Connect Teads to Azure SQL

Start with a connected Teads source and an existing Azure SQL database. Create a datastream between them, then configure the accounts, fields, schedule, and "accounts" table.

Select concrete Teads fields such as Billable Events, Budget Delivered Total Ad Cost - Cost per Result, Budget Delivered Total Ad Cost - CPC, 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.

Set an initial fetch period for Teads, then choose the frequency and lookback window for the job writing to "accounts". Catchr rewrites that selected period on each run.

The partition field tells Catchr which Teads rows in "accounts" belong to the period being refreshed. If you omit it, every run appends records rather than updating them.

With Teads data, an Azure SQL query can summarize spend, impressions, clicks, and click-through rate by campaign. A query built around Billable Events and Budget Delivered Total Ad Cost - Cost per Result can support trend reviews, account comparisons, and operational reporting.

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.