Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Taboola Connector Enhancement: Campaign Group Ingestion

Answered
Amisha Papneja User
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_group
  • GET /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.
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, and account_id
We currently retrieve this data via a custom Taboola API pull and would prefer to centralize ingestion through Fivetran for consistency and maintainability
Thanks!

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi Amisha,

    Thanks for submitting this request and for including all the details.

    I don't see a reference to this endpoint in Taboola's API documentation, though. This is the API documentation that we rely on for the connector: https://developers.taboola.com/backstage-api/reference/campaigns-overview. If you find any details related to campaign groups that I missed there, please let me know.

    I also found this documentation from Taboola on their hierarchy: https://www.taboola.com/help/en/articles/3878008-realize-account-organization. It doesn't reference any campaign group either.

    All of the fields that you mentioned are included on the campaign object: https://developers.taboola.com/backstage-api/reference/get-a-campaign. We sync that endpoint to the campaign table in the connector. Does that table address your use case?

    Thanks,
    Luke

  • Amisha Papneja User

    Hello! Checking in to see if there is an estimated timeline on when these can be completed by. Thank you! 

  • Amisha Papneja User
    • Edited
         

    Hey Lucas, 

    Thanks for following up. I wanted to provide additional clarification regarding campaign groups in Taboola and how they differ from the fields currently synced in the Fivetran campaign table. While the standard Taboola hierarchy documentation does not explicitly reference campaign groups, in practice we see campaign group data exposed via the Taboola API that functions as a distinct layer above campaigns and is not available in the campaign object currently synced by Fivetran.

    More specifically, when querying the campaign_groups Taboola API endpoint directly, we receive:

    • campaign_group_id
    • group_name

    (Example below is pulled from the campaign_groups endpoint showing campaign_group_id and group_name)

    https://docs.google.com/spreadsheets/d/1bbb329KYeNNjwj9EQLBtW23JHZDigJgkdmQ-WtGRgig/edit?usp=sharing

    Whereas in the Fivetran-synced campaign table:

    • campaign_group_id is not present
    • group_name is not present

    There is no field that allows a campaign record to be associated with its campaign group

    (Example below pulling from Fivetran campaign table showing the absence of  campaign_group_id and group_name).

    https://docs.google.com/spreadsheets/d/1O-a246YIEs9NajlxQGzxjtimHwnQyD3BZ5pFuqbZd8A/edit?usp=sharing

    These examples illustrate the gap between what exists in the Taboola API and what is currently synced via the connector. 

    Thanks for your help, 
    Amisha