Criteo
How to connect Criteo to Roivenue, what the default setup downloads, and how the figures are put together.
Criteo retargeting. The Roivenue connector downloads daily displays, clicks and cost down to ad level, plus the sales Criteo attributes to them.
Setting up the connector
Add a Criteo connector in Roivenue and choose Connect to Criteo. Roivenue sends you to Criteo to sign in and approve access. There are no keys to copy.
Setup options
In which currency does the site operate?
none
Criteo reports in the currency you pick here. Options are USD, EUR and PLN.
Conversion type name
purchase
What Criteo sales are called inside Roivenue.
AdCampaign REGEX filter
everything
Limits the connector to campaigns matching a pattern.
What the default setup downloads
Three jobs. One brings displays, clicks and cost per ad and day, a second brings sales and revenue, and a third downloads the transaction feed behind synthetic impressions.
Where the values land
Campaign
adCampaign
Adset
adGroup
Ad
adName
Displays
impressions
Clicks
clicks
AdvertiserCost
cost
SalesAllPc30dPv24h
conversions
RevenueGeneratedAllPc30dPv24h
conversionValue
Impressions are Criteo displays.
Reports are requested in GMT rather than the account timezone, so a day boundary may fall differently from your other connectors.
The jobs reprocess the last three days on every run.
Available columns
The table above is what the recommended template downloads. Every column this connector can bring back is listed on Criteo - Supported Columns.
Adding one means editing the connector in the Advanced Editor, which stops that connector receiving template updates.
Synthetic impressions
Alongside the daily figures, this connector downloads a conversion feed that Roivenue uses to build synthetic impressions.
Ad platforms report conversions that Roivenue never saw as a web session, because of ad blockers, cross-device journeys or conversions uploaded from a CRM. Left alone those orders look like they came from nowhere, and paid media gets undercounted. The synthetic impression stands in for the missing visit so path analysis and attribution see a complete journey.
There is nothing to configure. It comes with the connector, and it is why the setup creates more than one job.
How far back the data goes
The connector will request up to three years of history. How much arrives depends on what the platform holds for the account.
Troubleshooting
Was this helpful?