Skip to main content

Community

Connector Improvement: Impact Brand Connector Granularity Improvement

Answered

Please sign in to leave a comment.

Comments

2 comments

  • Official comment

    Hi Adam,

    Thank you for reaching out with your feature request to improve the connector for granular data on clicks and impressions. We've added this request to our backlog and will prioritize it based on demand and feasibility. I will keep you updated on any progress or developments regarding this feature. Please feel free to reach out if you have further questions or insights.

    Best regards,  
    Sanjeevv Maniram

    Please see my questions for Impact and their repsonses below regarding their API endpoints.

     

     

    1. Does the Impact Brand API expose ad-level performance data, including ad_id?
      Yes, you would need to run the report export endpoint to export this report, which contains this data. This can be done through our brand API documentation or directly through the report on a brand account:

    2. Are click and impression events available as discrete records via any API endpoint?
      Yes, click records are available via the Clicks Endpoint. Impressions, on the other hand, are not available via a specific endpoint; however, they can be retrieved through reports that have this dimension available, i.e., the Performance by Ad report.

    3. Is the UI “Performance by Ad” report powered by an internal reporting layer that is not accessible via the public Brand API?
      ​No. What you see in the report is what you can access through the API.

    4. Is there an alternative reporting API (e.g., advanced reporting or custom reporting endpoints) that provides ad-level grain?
      Yes, I would advise the Ad Listing report, which can also be accessed through the reportExport endpoint:


    5. Are there additional permissions or scopes required to access this level of detail?
      No. Account Administrators and Implementation Specialist members of a brand account can configure access scopes for the tokens. You can read more here.