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

Community

Add support for omnichannel promoted object on the Facebook Ads connector for the AD_SET_HISTORY table

Planned
Vid Stropnik User

Connector name: FACEBOOK_ADS

Table name: AD_SET_HISTORY

Column to add: PROMOTED_OBJECT_OMNICHANNEL_OBJECT (or similar)

API documentation link: https://developers.facebook.com/documentation/ads-commerce/marketing-api/ad-creative/omnichannel-ads

 

Additional details: 

Hi,

The promoted object JSON that is broken down does not accurately handle omnichannel promoted objects. Instead, no promoted object event type and URL is returned. We would like to request handling these cases in a sensible manner, as the promoted object event types & URLs are part of decisioning logic on downstream applications.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi Vid,

    Thanks for flagging this. The Meta Marketing API nests the pixel and offline data set IDs and their event types inside promoted_object.omnichannel_object, and the connector doesn't read that nested object.

    I've filed a task to sync the omnichannel pixel and offline data set IDs and their event types as queryable columns rather than raw JSON. It's on our mid-term roadmap, and I can't commit to a release date yet. I've also included the smart_pse_enabled field, which the API returns in promoted_object, but the connector doesn't sync it either.

    Cheers,
    Luke

  • Naren Bhandary Fivetranner

    Hey Vid,

    Thanks for reaching out and sharing additional details about your use-case. We are assessing this feature request to understand scope and alignment with our roadmap.

    We will share an update on this thread regarding our evaluation as soon as its available.

    Thanks,

    Naren 

  • Vid Stropnik User

    Hi Naren,

    Are there any updates available re: the alignment of the ticket above with your current roadmap? As it stands, these fields are not surface in any way on a pretty basic (i.e. high level) table in your ERD, which would leave us with the need to ingest it on our own.

     

    Thanks,

    Vid S