Skip to main content

Community

Please sign in to leave a comment.

Comments

4 comments

  • Official comment

    Hi Sharat,

    Thank you for reaching out to us with your feature request regarding Facebook's "Ad Activity" API. To better understand your needs, could you please provide further details? Specifically, we would appreciate it if you could specify your use case for this data.

    This information will help us assess how we can support your requirements effectively.

    Thank you for your engagement and for being part of our community.

    Best,  
    Luke

    Hi Lucas,

    We currently use Ad Activity to gather statistics about ad approval and disapproval and take action on disapproval to remedy issues. We also use it to gather information about manual changes made in ad accounts that may conflict with our automation and makes it easier to troubleshoot issues if we can see a history of changes in one one place instead of having our CS operatives click around in Facebook to find out what happened.

    Thank you, Sharat, that context is very helpful. 

    Do you know what data is stored in the field extra_data? It is described as "JSON encoded extra information" in Facebook's documentation. I'm curious whether it has a consistent structure and we should break this field out into a separate table to make it easier to work with, or if the structure changes for each row, and we should keep it as a JSON string in the schema.

    Thanks,
    Luke

    Hi,

    We would like to request this feature as well. Our use case is we need to pair ad performance with the creative that it was serving on the day. This enables us to understand why performance of certain ad may change over time.

    We thought we could use Fivetran ad_history table, but later was explained that the table only start syncing when we had Fivetran and thus it didn't contain any historical data.

    Ad Activity is one of the solves for this (even though it may not be the only solve)

    Let me know if you have any further question and I'd love to support this use case.