t1k:marketing:monetization:meta-audience-network
| Field | Value |
|---|---|
| Module | monetization |
| Version | 1.49.21 |
| Effort | high |
| Tools | — |
How to invoke
Section titled “How to invoke”/t1k:marketing:monetization:meta-audience-networkMeta Audience Network (FAN)
Section titled “Meta Audience Network (FAN)”Meta Audience Network as a mediation source, plus revenue reporting integration via the Graph API.
Facebook Instant Games (FBInstant placements, App Dashboard setup) →
t1k:marketing:monetization:fb-instant-ads.
When to Use
Section titled “When to Use”- 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)
Reporting API — endpoint & auth
Section titled “Reporting API — endpoint & auth”- Synchronous GET (pulls):
GET https://graph.facebook.com/v27.0/{business_id}/adnetworkanalytics?metrics=[...]&breakdowns=[...]&since=YYYY-MM-DD&until=YYYY-MM-DDreturns rows in the response, withpaging.cursors(before/after) andpaging.nextfor further pages. Version and path per the vendor guide: https://developers.facebook.com/documentation/audience-network/optimization/report-api/guide-v2 [retrieved 2026-11-16]. - Asynchronous POST:
POSTto the same business edge creates an async query and returnsquery_idandasync_result_link; read the result throughasync_result_link. Sample GET responses also carry aquery_id, so do not treat its presence as the async signal. - Auth: Meta access token with Audience-Network/Marketing-API permissions (Graph API / Reporting API v2).
aggregation_period:day(default),hourortotalon the GET (guide v2); the POST reference enum isDAY/TOTAL.hourneeds a range of at least 2 days. There is noLIFETIMEvalue; usetotalfor a cumulative figure.
Metrics & breakdowns
Section titled “Metrics & breakdowns”- 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_cpm(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_revenueis 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.
Quirks
Section titled “Quirks”- Synchronous GET limits (guide v2): at most 2,000 rows per request (
limit), and a window of up to 8 days. Page withpaging.cursors/paging.next. - Revenue is estimated and subject to Meta’s invalid-traffic adjustments.
- API versions move; the guide v2 examples show v27.0. Re-check the version string against the guide before coding (checked 2026-11-16).
References
Section titled “References”- Audience Network Reporting API v2 guide: https://developers.facebook.com/documentation/audience-network/optimization/report-api/guide-v2 [retrieved 2026-11-16]
- Graph API Adnetworkanalytics reference: https://developers.facebook.com/docs/marketing-api/reference/business/adnetworkanalytics
Hard rules
Section titled “Hard rules”- 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.