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

Community

Connector Improvement: pagepost / instagram media tables in the Facebook Ads connector

Answered
Vid Stropnik User
  • Edited

Hi,

We're inquiring about the feasibility to ingest the the following tables from the graph API:

- pagepost (referenced in creative history table as part of the `object_story_id` and `effective_object_story_id` fields) 

- shadowigmedia (referenced in creative history table as part of the `effective_instagram_media_id` field).

 

Ingesting these fields is relevant for us, as it is a means of referencing the creative assets used in certain facebook ads. As these ads aren't necessarily created by owned pages / IG accounts, fetching them via a Pages / Instagram Business connector isn't feasible. 

Thank you and kind regards,

Vid Stropnik

Please sign in to leave a comment.

Comments

4 comments

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi Vid,

    Thanks for submitting this feature request. As you pointed out, these fields are references to Facebook Pages and Instagram Pages objects. We don't include them in the Facebook Ads connector because those endpoints require an entirely separate set of permissions that we don't currently have on the Facebook Ads connector app.

    I think that even if we were to get those permissions assigned to this app, to hit those endpoints, you'll need approval (authorization) from a user with access to those Pages / IG accounts. So I believe if you can't access them via the Facebook Pages or Instagram Business connectors, you can't access them via the Facebook Ads connector with more permissions either. 

    Let me know if I'm misunderstanding something.

    Cheers,
    Luke

  • Vid Stropnik User

    Hi Luke,

    Thanks for getting back to me.

    From your response, I assume you're referring to the Page Public Content Access advanced access permission. If that's the case, this aligns with our current understanding of the query permission handling process: apps with this set are able to query nodes of type pagepost/shadowigmedia, while apps without it are not.

    However, my understanding is that authorization by a user with page/ IG account access would not be required to access the content of these nodes.


    For the Page Post example: While assignment to a page is necessary for configuring a Facebook Pages connector (which allows retrieval of all historic page posts, the IDs of which could then be matched to those found in the `Creative History` table on the Facebook Ads connector), no such permission should be required to query individual pagepost nodes (referenced via `object_story_id` on Creative nodes) when the Meta app has the `Page Public Content Access` advanced permission set. At least to our understanding, the same principle applies to shadowigmedia / IG Business connectors. Please correct me if this is not the case.

    This effectively allows a user with access only to the ad account (the main entity of the Facebook Ads connector) to retrieve elements of the creative-associated pagepost / shadowigmedia objects.

    This becomes particularly important when fetching creative assets (images and videos) associated with creatives, since these assets are only available through the pagepost / shadowigmedia nodes. If a user has access only to the ad account but not to the corresponding page / IG Account, these IDs cannot be matched with data ingested via a separate Facebook Pages / IG Business connector.

     

    I hope this provides enough context to support considering such a feature for the backlog or roadmap. Please let me know if I can provide any further context or if I'm missing a relevant limiting factor, preventing this feature.

    Best,

    Vid S

  • Vid Stropnik User

    Hi Luke, we've discussed this Feature request via a call a couple of weeks ago. I'm just checking in regarding the feasibility of this, so that we may direct our internal development in the most sensible way.

     

    Thanks

    Vid S

  • Lucas Alexander Fivetranner

    Hi Vid, 

    Sorry for the delay on this. I haven't heard back from our engineering team on this one yet because they've been busy with other tasks. I followed up to confirm the feasibility of this request.

    I understand the importance of this for your reporting, and I've marked it as a high priority internally.