Connect Outbrain DSP to Azure SQL

Add Outbrain DSP in Sources and connect the existing Azure SQL database in Storage. A datastream defines the route, while the job loads the chosen fields into "ad groups".

Select concrete Outbrain DSP fields such as Account Status, Ad Group Status, Avg. Cost per Minute, 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.

Define the first Outbrain DSP fetch, run frequency, and lookback window in the "ad groups" job. Each scheduled run replaces data inside the configured period.

Use a supported date field to partition "ad groups". Recurring Outbrain DSP runs can then update the selected window instead of adding another copy of the same period.

With Outbrain DSP data, an Azure SQL query can summarize spend, impressions, clicks, and click-through rate by campaign. Model Account Status and Ad Group Status in SQL, then expose the result to dashboards, internal tools, or recurring client reports.

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.