Connector Improvement: Connector Improvement: Taboola Connector Enhancement: Campaign Group Ingestion
Answered
Hi Fivetran Team,We’re using the Taboola connector and noticed that Campaign Groups are not currently being ingested, even though they are a supported resource in the Taboola API.Taboola exposes Campaign Groups via the following endpoints:
GET /backstage/api/1.0/{account-id}/campaigns_groupGET /backstage/api/1.0/{account-id}/campaigns_group/{campaign-group-id}
These endpoints return fields such as campaign_group_id and group_name, which we use as campaign-level metadata in our reporting. And we would like to request the raw ingestion of this resource.Specifically, we’re asking for:Ingestion of the Campaign Group resource as a standalone table
- Inclusion of fields such as
id,name,status,start_date,end_date,spending_limit, andaccount_id
We currently retrieve this data via a custom Taboola API pull and would prefer to centralize ingestion through Fivetran for consistency and maintainabilityThanks!
-
Official comment
Hi Amisha,
This request appears to be a duplicate of a previously submitted feature. You can find our response and current status regarding Taboola Campaign Group ingestion at this link.
Please refer to the thread above for updates and to add any further details or feedback.
Thanks,
Shiva
Please sign in to leave a comment.
Comments
1 comment