Categories attribute indicate the category of the product being submitted, according to the Google product taxonomy. If your product can be linked to multiple categories, Criteo wants the one that is the most relevant.
The Categories pipeline can be used to request and retrieve categories for your portfolio. If a category is requested but is missing from current user’s portfolio, it will not be included in the list. If neither campaign ids nor advertisers ids are provided, then the user’s portfolio will be used.
Read more about this here
Configuring the Credentials
Select the account credentials which has access to relevant Criteo data from the dropdown menu & Click Next
Data Pipelines Details
- Data Pipeline
Select Categories from the dropdown
Select one or more advertisers from the drop-down. If the advertiser ids requested are not part of the user’s portfolio, they will be skipped.
|All advertisers which your credentials have access to should be available here. If they are not, please check the credentials selected / configured by you. While you can add multiple advertisers, the table size may become too large and so it is advisable to add one account per pipeline and use Union queries in the data warehouse to join the data for consumption|
Select one or more metrics you would like to fetch from the Criteo platform. Each of the selected metric will create one or more columns in the database table in the destination warehouse. You can click on View Schema anytime to see the schema of the table being created.
Select to specify if you want only enabled categories or not in each run. If selected YES, it returns only categories you can bid on.
Default Value: False
Delete or Append
This refers to the manner in which data will get updated in the data warehouse, with 'Delete' selected, the data will be upserted (only new records or records with changes) and with 'Append' selected, all data fetched will be inserted. Recommended to use "Delete" option unless there is a specific requirement.
Default Value: Delete
Scheduling specifies the frequency with which data will get updated in the data warehouse. You can choose between Manual Run, Normal Scheduling or Advance Scheduling.
- Manual Run
If scheduling is not required, you can use the toggle to run the pipeline manually.
- Normal Scheduling
Use the dropdown to select an interval-based hourly, monthly, weekly, or daily frequency.
- Advance Scheduling
Set schedules fine-grained at the level of Months, Days, Hours, and Minutes.
Detailed explanation on scheduling of pipelines can be found here
Dataset & Name
- Dataset Name
Key in the Dataset Name(also serves as the table name in your data destination).Keep in mind, that the name should be unique across the account and the data source. Special characters (except underscore _) and blank spaces are not allowed. It is best to follow a consistent naming scheme for future search to locate the tables.
- Dataset Description
Enter a short description (optional) describing the dataset being fetched by this particular pipeline.
Choose the events for which you’d like to be notified: whether "ERROR ONLY" or "ERROR AND SUCCESS".
Once you have finished click on Finish to save it. Read more about naming and saving your pipelines including the option to save them as templates here
Still have Questions?
We’ll be happy to help you with any questions you might have! Send us an email at email@example.com.
Subscribe to our Newsletter for latest updates at DataChannel.