t1k:marketing:monetization:meta-audience-network

How to invoke

/t1k:marketing:monetization:meta-audience-network

Meta Audience Network as a mediation source, plus revenue reporting integration via the Graph API.

Integrating FAN as a bidding/mediation adapter (under MAX, LevelPlay, AdMob, etc.)
Placement setup, GDPR/ATT consent signalling
Pulling FAN revenue via the Audience Network Reporting API (Graph API)

Endpoint (async query): GET https://graph.facebook.com/v21.0/{property_id}/adnetworkanalytics — creates a query, returns an AdNetworkAnalyticsSyncQueryResult id; poll results via the adnetworkanalytics_results edge.
Auth: Meta access token with Audience-Network/Marketing-API permissions (Graph API v21 / Reporting API v2).
aggregation_period: DAY (metric refers to that date) or LIFETIME (cumulative to date).

Metrics (pick ≥1): fb_ad_network_revenue, fb_ad_network_request, fb_ad_network_filled_request, fb_ad_network_imp (impressions), fb_ad_network_show_rate, fb_ad_network_fill_rate, fb_ad_network_ecpm, fb_ad_network_click, fb_ad_network_ctr.
Breakdowns: country, platform, placement, deal, delivery_method, ad_server_campaign_id. With NO breakdown the report is account-level.
fb_ad_network_revenue is FAN’s own revenue (a single source within your mediation stack) — to compare against other networks, align it with each network’s per-source report.

Asynchronous: the GET creates a query; you must poll the result edge until ready (don’t expect inline rows).
Revenue is estimated and subject to Meta’s invalid-traffic adjustments.
API/SDK versions move fast (currently v21 / Reporting API v2) — confirm the version string against live docs before coding.

FAN ATT consent must be true on iOS to monetize at all — without ATT, FAN delivery on iOS drops to near zero.
FAN as a non-bidding network in MAX/LevelPlay underperforms — always enable FAN bidding in modern mediation.
Account-level vs placement-level reporting can disagree — Meta publishes settled revenue at the account level; placement-level is estimated.