Connect Outbrain DSP to Power BI

Connect Outbrain DSP in Catchr with its DSP API Client ID and Client Secret, then select an accessible account. In Catchr’s Power BI query builder, select Date, campaign, Impressions, Clicks and Total Spend and preview a short extraction. Import the generated URL through Get data > Web in Power BI Desktop. Check the returned rows before building measures, keeping report level and cost basis, without inventing unsupported conversion measures clear in the model.

This Catchr source connects to the Zemanta API used by Outbrain DSP, whose current documentation is branded Teads DSP. It is separate from the Outbrain connector and the Teads Ad Manager connector. Match the source to the platform where your account and reporting credentials were issued; similar brand names do not make their connections interchangeable.

Catchr includes impressions, clicks, media spend, total spend, data cost, license fee, video starts, video completions and viewability fields. Reports can use account, campaign, ad group or content ad levels, with available breakdowns such as publisher, device and country. Start at the reporting level you need and add breakdowns gradually, checking totals against the DSP report with the same selections.

The current Catchr field catalog for this source does not expose conversion counts, CPA or ROAS. Use it for delivery, cost, video and available engagement reporting. To measure business outcomes, add a separately connected analytics source such as GA4 and define how its campaign data matches DSP spend. Those analytics results follow their own attribution rules and do not recreate the DSP's conversion report.

Choose the cost field that matches the figure you use in the DSP interface. Catchr exposes Media Spend, Data Cost, License Fee, Total Spend and Margin separately, so they should not be treated as interchangeable amounts or added together indiscriminately. Use one consistent cost basis when calculating CPC or CPM, and verify currency before combining accounts or other advertising platforms.

The connector excludes visit and site-engagement fields from hourly requests, including Visits, Unique Users, Pageviews, Bounce Rate and Time on Site. Use hourly charts for supported delivery metrics such as impressions, clicks and spend, and assess engagement in a separate report at a supported time level. A blank or zero for an unsupported field should not be interpreted as proof that no visits occurred.

Catchr retrieves generated DSP reports rather than the separate real-time statistics feed. The imported Power BI model changes when it refreshes successfully, and report generation can take time. Configure and test scheduled refresh in the service, then compare completed periods using the same account and cost basis. Recent traffic and post-click engagement can finish processing at different times.