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

Community

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi Adam and Ahmed, 

    Thanks for the details.

    In March 2026, we released custom reports for our Criteo connector: https://fivetran.com/docs/connectors/applications/criteo/changelog#march2026. This feature was designed to give you more flexibility with the reporting table schemas.

    You should be able to add a new custom report to your Criteo connections that uses the statistics_report type, with a day granularity and includes the adset_id or campaign_id as a dimension. Both are supported dimensions: https://fivetran.com/docs/connectors/applications/criteo/custom-reports#customreports.

    Let me know if that feature doesn't solve this gap.

    Cheers,
    Luke

  • Ahmed Zaman User

    • We have all the metrics needed from Fivetran in the “ad_statistics_daily_report” table; this table is at the “ad” level. But it does not have any adset_id or campaign_id, which we need to fetch by joining other tables.

    • We can get the adset_id from the “ad” dataset, but this “ad” table does not have some of the ads that we are getting through the SDK or that are in the "ad_statistics_daily_report". (I think this was what we ran into earlier). I have screenshots attached for reference.

    • It's the ad_id = “-1” and ad_name = “Unknown” that are missing from the ad table.

    ad_statistics_daily_report - this table only has ad_id as "-1" or ad_name as "Unknown".

    ad - this table does not have that "-1" in it.

     

    If I reverse-engineer this based on the data that we are pulling from Criteo using the Connector SDK, here are the detailed screenshots.

    Our Internal Criteo SDK Table - If you see here, we have ad, adset, and campaign level data all in one table. Good news is that the metrics are matching in the "ad_statistics_daily_report" from the std fivetran connector.

    Now let's use this campaign_id can go in reverse order to adset and then to ad.

    Campaign Table - Fivetran Std Connector: we have campaign_id = 871999

    Adset Table - Fivetran Std Connector: we have campaign_id = 871999 & corresponding adset_id = 695806

     Until this point, both campaign and adset details are aligned and correctly joined.

    Ad Table - Fivetran Std Connector: Now, if you see here, I searched using the ad_set_id = 695806. The ids (ad_id) that I get in return are "3007172" and "3007173", which I don't find in the "ad_statistics_daily_report" where we have all the metrics.

    ad_statistics_daily_report (filtered to above ad_ids)

     

    P.S: The ask is if we can get the adset_id and campaign_id in the "ad_statistics_daily_report" table; that would be super helpful and help us transition back to the std Criteo connector rather than the SDK.