Connect AdsWizz to Power BI

Connect AdsWizz in Catchr using an API key with reporting access and select the advertiser. In Catchr’s Power BI query builder, select Audio Impressions and campaign delivery for a completed period 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 audio delivery versus companion-display activity clear in the model.

The Catchr catalog includes Audio Impressions, Total Impressions, Total Reach - Unique Users, LTR/VTR, audio quartiles and clicks. It also includes companion-banner, Second Screen, ShakeMe and conversion fields where those features and measurements apply. Keep audio delivery separate from companion display activity so a combined impression total does not look like a count of audio listens.

Listen-through rate describes how much ad playback reached completion. Listen-through conversions describe downstream actions attributed to an audio exposure. A completed listen is not automatically a purchase or lead. Show LTR/VTR alongside the relevant conversion field, and use the Audio Pixel Action dimension when you need to identify the type of tracked outcome.

Catchr's AdsWizz fields include Total Conversions, Click-Through Conversions, Listen-Through Conversions, View-Through Conversions, Conversion Value, CPA and Return on Ad Spend. Results depend on the attribution and measurement configured in AdsWizz, such as AudioPixel tracking. Connecting the reporting source does not create conversion tracking or recover untracked purchases. Confirm the action and monetary units before comparing these results with store revenue.

AdsWizz reports limit the number of breakdowns in one request. Catchr already includes Advertiser, and adds a daily time breakdown when the query includes Date. Start with Date, a metric and one useful breakdown such as Campaign or Publisher. Split country, device and other analyses into separate charts if adding them together exceeds the reporting limit.

Match the advertiser, metrics, filters and reporting period first. Catchr requests daily date windows in UTC, so an export using local dates can differ at the edges of the period. Compare the returned rows as well as the total. If rows are still missing with matching settings, send Catchr support the advertiser, dates and field selection so the report can be checked before you use it for billing or client reconciliation.

No. The same person may appear in several days, campaigns or publisher groups, so adding unique-user counts can double-count listeners. Request reach for the full period without a daily breakdown and verify it against the matching AdsWizz report. For cross-channel dashboards with Spotify Ads, keep each platform's reach separate unless you have a measurement method that deduplicates listeners across platforms.