Connect Xandr to Azure SQL

Create the Xandr source, then register Azure SQL with its server host, database name, username, and password. Link both through a datastream and target the "ad groups" table in the job.

Select concrete Xandr fields such as Attributed Pc Revenue, Attributed Pv Revenue, Attributed Revenue, and Day of the month. You can rename the chosen columns, preview the result, and write them to Azure SQL tables such as accounts, advertisers, and campaigns.

Configure the initial Xandr period separately from the recurring schedule for "ad groups". The source API determines how much history is available.

Choose an eligible date field as the partition for Xandr. Catchr can then replace the matching period in "ad groups"; without it, later runs append rows and may create duplicates.

With Xandr data, an Azure SQL query can summarize spend, impressions, clicks, and click-through rate by campaign. Use Attributed Pc Revenue and Attributed Pv Revenue in an Azure SQL view to create a reusable reporting layer for client analysis.

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.