Bulletin: Consolidated Web+App reporting for Meta Ads and Google Ads

Last update:
SectionDetails
What's new
  • Any attribution to metaweb_int will now be reported as Facebook Ads.
  • Any attribution to googleads_int will now be reported as googleadwords_int.
  • The change only impacts new attributions. Existing attribution isn't changed retroactively.
  • This change applies across all reporting tools — including dashboards and raw data exports.
  • The translation to the “official” media source (e.g., Facebook Ads, Google Adwords_int) automatically occurs on the back end.
  • The complete web cost of Meta Web and Google Web is reported in the dashboard and Cost ETL under the main PID = facebook_int and googleadwords_int, respectively.
General Availability date November 02, 2025
Why should you care?The consolidation provides holistic reporting of ALL your campaigns from a specific network, such as Meta or Google, including full mobile and web cost reporting.
What you need to do 
  • No change to the campaign setting process. Continue using the original PIDs (metaweb_int and googleads_int). These ensure AppsFlyer routes postbacks correctly via the appropriate web integrations.
  • In raw data tools:  
    • the original_url field will still display the original PID used in the ad,
    • the attribution media source fields will reflect the updated naming.
  • To get the web cost include the campaign ID in the attribution link to get the web cost from Meta Web and Google Web,
Best practices
  • Include campaign type in campaign names to simplify classification.
  • To enable full cost reporting for web campaigns, connect your network account under the “Cost” tab of the respective main integration (Facebook Ads, googleadwords_int).
Future support
  • AppsFlyer plans to introduce a new dimension (engagement_platform_group) to indicate campaign type (App or Web).

  • Upcoming PIDs for CAPI integration will include:

    • snapweb_int → mapped to snapchat_int
    • tiktokweb_int → mapped to tiktokglobal_int
    • twitterweb_int → mapped to Twitter

     Note

    These mappings are already active — any attributions using the above PIDs are automatically translated to the main SRN PIDs, even prior to full integration support.