Connect Criteo to Azure SQL

Register Criteo, save the Azure SQL connection details, and pair both systems in a datastream. The associated job previews and writes the selected columns to "accounts".

Select concrete Criteo fields such as Advertiser All Value, Advertiser Value, App Installs, and Channel Name. You can rename the chosen columns, preview the result, and write them to Azure SQL tables such as accounts, advertisers, and campaigns.

The "accounts" job can begin with a historical Criteo fetch and continue on a recurring schedule. Available history and frequency depend on the source API and your plan.

Select a valid date field when configuring the Criteo job for "accounts". Catchr deletes and rewrites the scheduled window, limiting duplicate rows across overlapping runs.

With Criteo data, an Azure SQL query can summarize spend, impressions, clicks, and click-through rate by campaign. Turn Advertiser All Value and Advertiser Value into a stable Azure SQL view that analysts and reporting tools can query repeatedly.

Yes. Connect an existing Azure SQL  database first. The Catchr job creates and populates the destination table you configure inside that database.

Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.