Renta supports data export from Criteo to following destinations:
- Google BigQuery
- Clickhouse
- SQL Server
- Google Spreadsheets
Integration creating in data warehouse (DWH)
- Go to integrations catalog;
- Select Criteo;
- Add a Criteo account that has the necessary data;
- Choose the added Criteo account;
- Specify the destination you want to import the data into;
- Go to the settings screen and set necessary configuration:
Report type
Report type consists of the unique set of parameters and metrics available for uploading to DWH. Each Report Type has its own parameters and metrics collection.
| Name | Description |
|---|---|
| CampaignPerformance | Contains stats about Criteo Dynamic Remarketing. |
| TransactionID | Contains stats about all transactions. |
| FacebookDPA | Contains stats from Facebook Dynamic Ads. |
Parameters
Parameters contains the list of parameters and metrics available for export. Specify the parameters required for uploading.
As a result, Renta will create the table that will contain the selected parameters data. The order of the selected parameters in the Rentas interface will match to the order of the table columns.
Date range type
Choose the inserting period. You can specify any historical time interval.
To select the necessary time, enter the date from which you want to start uploading data in the “From” field, then enter the end date in the “To” field.
If you want the data in the table to be updated daily and supplemented with new days, then enter “Yesterday” in the “To” field.
Detailed instructions for working with a date range.
Integration name
There is an auto generated name for your integration and here you can edit it as much as you like.
Both Cyrillic and Latin are permitted, but not more than 100 symbols.
The integration name is displayed on the Integration List page.
Table name
There is an auto generated name for your table and here you can edit it as much as you like.
Only Latin is permitted, numbers and “_” symbol.
Update time
You can specify any update time that you need. Users choose early morning integration updates most often, for example 5 AM.
In that case your integration will update in period from 5 AM to 6 AM.
Integrations are updating according to the time zone selected in your profile settings.
Overwrite period
Data overwrite period is a retrospective update of data for the selected period.
For instance you choose the overwrite period “Last 7 days” – it means that all data for the last 7 days will be deleted and inserted once again with updated data.
Note: this tab appears only if parameters like Day/Date/Time Period etc have been chosen.
Integration creating in Google Spreadsheets
Take advantage of the free extension available in the Google Workspace Marketplace. In order to do it:
- Install the extension Renta Spreadsheets Add-on.
- Then go to Google Sheets and in the Tools tab select Renta
- Press the Run button.
After that a workspace with integration settings will open in the right sidebar. Detailed instructions for creating an integration are available at this link. Please note that all integrations created in Google Spreadsheets are also available for management in the web version of Renta.
Data Structure
| Name | Description | Type |
|---|---|---|
| Displays - test | Number of times your Criteo ad is displayed to a user on publishers’ websites. | INTEGER |
| Clicks | Number of times that your Criteo ads have been clicked. | INTEGER |
| AdvertiserCost | Total cost of your campaigns. | FLOAT |
| Currency | Currency. | STRING |
| SalesPc | The total number of purchases completed via the same device your Criteo ads were clicked. Sales are attributed within 30 days after a user clicks on your Criteo ad. | INTEGER |
| SameSalesPc | The total number of purchases completed via the same device your Criteo ads were clicked. Sales are attributed within 30 days after a user clicks on your Criteo ad. | INTEGER |
| SalesPcNd | Post-click sales that are non-deduplicated. | INTEGER |
| SalesPv | All sales that occurred on your website within 24 hours after a user sees a Criteo ad of your campaign. Post-view sales do not include sales from users who clicked an ad, which are counted as sales. | INTEGER |
| SalesPvNd | All non-deduplicated post-view sales that occurred on your website within 24 hours after a user sees a Criteo ad of your campaign. Post-view sales do not include sales from users who clicked an ad, which are counted as sales | INTEGER |
| SalesPcPv | The total amount of sales generated both post-click and post-view | INTEGER |
| SalesAllPc | The total number of purchases completed via the same device your Criteo ads were clicked, or a different one. Sales are attributed within 30 days after a user clicks on your Criteo ad. | INTEGER |
| RevenueGeneratedPc | Total revenue of your campaigns generated from post-click sales | FLOAT |
| RevenueGeneratedPv | Total revenue of your campaigns generated from post-view sales | FLOAT |
| RevenueGeneratedPcPv | Post-click + post-view revenue is the total revenue of your campaigns generated from post-click and post-view sales. This number is computed based on the prices provided by your conversion trackers | FLOAT |
| RevenueGeneratedPcNd | Total revenue of your campaigns generated from post-click sales non-deduplicated | FLOAT |
| RevenueGeneratedPvNd | Total revenue of your campaigns generated from post-view sales non-deduplicated | FLOAT |
| ExposedUsers | Number of distinct cookies that have seen at least one Criteo display | FLOAT |
| OverallCompetitionWin | Percentage of impressions/ad placements won, out of all impressions/ad placements that were bid on. For example, Criteo bid on 10 ad placements and won 2, so the Overall Competition Win is 20%. Higher CPC bids result in increased competition win. | FLOAT |
| Audience | Number of distinct cookies to which Criteo had the opportunity to make a display | FLOAT |
| Reach | Share of the audience exposed to at least one Criteo display ad (percentage) | FLOAT |
| AverageCart | Average revenue generated by a campaign’s sales. This number is calculated by dividing the total revenue by the total sales | FLOAT |
| ClickThroughRate | The number of times your Criteo ads are clicked, divided by the number of times your ad is displayed (impressions). Each campaign has its own CTR | FLOAT |
| ConversionRate | Number of sales generated by users who clicked on your campaign’s ad, divided by the campaign’s number of clicks | FLOAT |
| ConversionRatePv | Conversion rate post-view is the number of post-view sales generated by users who viewed on your campaign’s ad, divided by the campaign’s number of impressions | FLOAT |
| ECos | The ratio between the total cost of the campaign and the sales amount that the campaign generated. COS provides a good indication of your campaign’s ROI | FLOAT |
| ECosPv | The ratio between the total cost of the campaign and the post-view sales amount that the campaign generated. This number provides a good indication of your campaign’s ROI. | FLOAT |
| ECosPcPv | Cost of sale post-click + post-view is the ratio between the total cost of the campaign and the post-click and post-view sales amount that the campaign generated. This number provides a good indication of your campaign’s ROI | FLOAT |
| CostPerOrder | Cost per order is the amount of money (cost) spent to generate post-click sales | FLOAT |
| CostPerOrderPv | The amount of money (cost) spent to generate post-view sales | FLOAT |
| CostPerOrderPcPv | Cost per order post-click + post-view is the amount of money (cost) spent to generate post-click and post-view sales | FLOAT |
| ECpc | The price you pay each time a user clicks your Criteo ad. Depending on your campaign’s business model, you can change the CPC on the Campaigns tab for each campaign | FLOAT |
| ECpm | Cost per mille is the cost of your campaign for 1,000 impressions | FLOAT |
| ReturnOnAdvertisingSpending | Corresponds to the ratio between the sales amount the campaign generated and the total cost of the campaign (ROAS = 1/COS) | FLOAT |
| AdvertiserValue | The total value generated by the campaign. It is equal to the sum of revenues generated by each product multiplied by their corresponding Value coefficient as defined in the advertiser's feed. | FLOAT |
| CostOfAdvertiserValue | The ratio between the total cost of the campaign and the Advertiser Value of the campaign. | FLOAT |
| Day | Day. | DATE |
| Campaign Name | Campaign Name. | STRING |
| Transaction date | Transaction date. | DATE |
| CatalogName | Catalog Name. | STRING |
| ClickDate | The date of click. | DATE |
| TransactionId | Transaction id. | STRING |
| Amount | Amount. | FLOAT |
| IsAttributed | Attribution status. | BIT |
| MatchingType | Matching Type. | STRING |
| PartnerCurrency | Partner Currency. | STRING |
| Day | Day. | DATE |
| Displays | Number of times your ad is displayed. | INTEGER |
| Clicks | Number of times that your ads have been clicked. | INTEGER |
| FB cost | FB cost. | FLOAT |
| Advertiser Name | Advertiser Name. | STRING |
| ClickThroughRate | The number of times your ads are clicked, divided by the number of times your ad is displayed (impressions). Each campaign has its own CTR. | FLOAT |
| Total cost | Total cost. | FLOAT |
Quotes and limits
Important note: Renta doesn’t provide any restrictions like amount of accounts, connectors, integrations or inserting date range.
Limits for Criteo:
- Not more than 200 requests per minute, per client
Link to the official documentation
_______________________________________________
If you have any questions – please contact us!