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

Community

Connector Improvement: Expand Facebook Ads Connector's custom_conversion_history table to match what's available on the Graph API

Answered
Vid Stropnik User

Hi,

We're inquiring about the feasibility to ingest the extra fields from the Facebook's Insights API, in the custom_conversion_history table. Currently, the connector offers just the conversion ID and name, whereas the functionality in Meta is quite broader: https://developers.facebook.com/docs/marketing-api/reference/custom-conversion/

We're especially interested in ingesting the fields: 

- custom_event_type,

- data_sources,

- description,

- event_source_type,

- pixel,

- rule.

Ingesting these fields is imperative for us, as we're trying to move to a more general method of modeling ad performance, which is governed by the ad set's promoted object, to which these custom events are linked. In lieu of being able to ingest the general metrics directly (via the cost per result / result rate fields, about which we've asked previously), this is the closes approximation we can get to model these mappings manually.

 

Thank you and kind regards,

Vid Stropnik

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Official comment
    Shivaprasad Mogili Fivetranner

    Hi Vid,

    This is a valuable idea—expanding the custom_conversion_history table to include the additional fields available has been added to our feature improvements backlog for further review. A quick check looks like this is feasible and not already supported in our connector, we'll look deeper once our team gets a chance to pick this up.

    To better understand your needs, could you share more details about your use that requires these fields?

    Updates on any progress will be shared here in this thread.

    Thanks,
    Shiva

  • Vid Stropnik User

    Hi Shiva,

    I regretfully wasn't subscribed to this thread and I missed your response here. I see that this feature is already part of the ongoing development loop and will be supported in April. Thank you so much for looking into it!

     

    Let me highlight some usage on our part that requires those fields, even though it may be late:

    - Full matching of the primary metric (result) to an adset: For some adsets, the promoted object custom event is identified with the custom event rule. Even if the result field is now attainable via Fivetran, this requires the ad to be trafficked, which won't always be the case when just trying to analyze individual ad set setups and how the ads therein should be monitored / against which metrics they should be scored.

    - To prioritize our development correctly, we are interested in the amount of different pixels / other event sources used on adsets in individual ad accounts. This, again, can be done through the result rate, but a more complete snapshot of each custom event (rather than just an ID) is much more informative and we'd prefer to use data ingested via fivetran, versus fetching this through the graph api.

    Thank you for supporting our recent requests!

  • Lucas Alexander Fivetranner

    Hi Vid, 

    You may have seen the email we sent on March 4, 2026, about this feature. We’re adding Fivetran system columns that will make the custom_conversion_history table a History Mode table. With history mode, you can analyze data at a particular point in time or track how it has changed over time. To select the active version of a record in this table, you should include the following condition in your queries:

    WHERE _fivetran_active = true

    I think this addresses your request for "a more complete snapshot of each custom event (rather than just an ID)". But I'm not certain. It would be great to discuss your use case in more detail over a call.

    I'll send you an email with a link to book a meeting (if you're interested).

    Cheers,
    Luke

  • Vid Stropnik User

    Hey Luke, we're not seeing the column 

    _fivetran_active

    in any of our `_history` tables in the Facebook Ads connector. I understand that the `CUSTOM_CONVERSION_HISTORY` table has not been migrated to history mode as of yet, but we aren't seeing this column in other history-mode tables, such as ad, ad set, campaign or account history. Can you confirm that this is something that we should expect to see / look into why it isn't passing through to our account?

     

    Thanks.

  • Vid Stropnik User

    Hi Luke,

    Just following up on this. Any chance we'd get a clarification on the `

    _fivetran_active

    column?

    Thanks,

    Vid S