Hi Gokul,

Thanks for the detailed write-up and for including the curl example.

I dug into Taboola's Campaign Summary Report API and the Taboola Ads connector's existing behavior. The connector calls this report endpoint and syncs the campaign_site_day_breakdown dimension into the campaign_site_day_report table, but it enumerates campaigns from Taboola's GET /campaigns/ endpoint and requests the report one campaign at a time. Per Taboola's docs, a terminated campaign no longer appears in that campaigns list, so it's never included when the connector builds its per-campaign report requests. That's the root cause of the gap you're describing.

Per the Campaign Summary Report reference, campaign is documented as an optional filter (only start_date/end_date are required), and Taboola's exclude_empty_campaigns changelog states that campaign-breakdown dimensions return all campaigns by default. That suggests an account-level request without a per-campaign filter should include terminated campaigns' delivery data, since the report reflects delivery facts rather than the active campaign list.

I've filed an internal ticket to explore this change. I can't provide a specific timeline for when this will be delivered, but I'll keep you updated. Additional upvotes for this request from other Fivetran users will help increase the prioritiy relative to the rest of our backlog.

Cheers,
Luke