Connector Improvement: Include [campaign_breakdown report] in the existing Taboola Connector
AnsweredWe would like the Taboola connector to support a report that is currently available in Taboola but not exposed through Fivetran. Specifically, we need the [campaign_breakdown report] to be accessible via the connector to enable automated ingestion into our warehouse.
Here is a link that may be helpful to pinpoint what we're referring to:
https://developers.taboola.com/backstage-api/reference/dimensions-cheat-sheet
-
Official comment
Hi Amisha,
Thanks for the input. While this has been added to the backlog for next steps, can you help us understand how this data would help in your analysis - this would help us ensure we design and develop this right.
Regards,
Unni -
Thanks for the prompt response. This data would enable more accurate Yahoo performance reporting within our warehouse. We have been working directly with Yahoo on this issue, and they recommended requesting implementation of the campaign_breakdown dimension, as it most closely aligns with the metrics and structure shown in the Yahoo UI. While we are able to access campaign-level metrics through the existing Fivetran tables, Yahoo has identified a discrepancy , specifically with visible_impression, between the data returned by the current API reports and what is displayed in the UI.
As shared by the Yahoo Solutions Engineer: “I would suggest reaching out to Fivetran to see if they can implement the more general campaign_breakdown report, while I investigate internally why the other reports are not showing up-to-date data and follow up on timeline.”Implementing the campaign_breakdown dimension would allow us to reconcile these differences and ensure our reporting matches Yahoo’s source-of-truth UI metrics.
Could you also share whether this enhancement is feasible and, if so, the expected timeline for implementation?
-
Hello! I’m checking in to see if there’s an estimated timeline for when this might be completed. Thank you!
Please sign in to leave a comment.
Comments
3 comments