At a glance
| Field | Detail |
|---|---|
| What | Decide whether a Meta app campaign reporting gap needs a measurement investigation before a budget change. |
| Who it matters to | App buyers comparing Meta campaign results with a mobile measurement partner. |
| Where | Meta app campaign reporting and the AppsFlyer, Adjust, or Branch integrations discussed below. |
| When it applies | When install, event, cost, or export totals differ; this is an evergreen review process. |
| Action | Identify the report basis, event route, refresh timing, and data-access conditions before interpreting the gap. |
Meta app ads reporting should inform a budget decision only after the compared reports answer the same question. Our suggested approach is to separate attribution differences, event-delivery problems, and export restrictions, then investigate the relevant layer. The documentation below describes different integrations; use the checks for the measurement partner your app actually uses.
Choose the comparison before judging performance
Adjust explains that Meta Events Manager can contain events sent from organic traffic and other acquisition sources, whereas a campaign comparison should use events attributed to Meta in both systems. It also recommends checking attributed install differences before investigating event-level differences. Adjust's integration details distinguish these reporting populations.
Our suggested first step is to write down the exact event and report being compared. An event-delivery check asks whether information arrived. A campaign-performance check asks which advertising activity received credit. Treating those as separate questions gives the investigation a clearer owner and avoids interpreting an event receipt total as a campaign result.
AppsFlyer's discrepancy documentation identifies additional differences, including attribution windows, cross-device attribution, time zones, and activity-based versus lifetime-based event reporting. AppsFlyer's explanation supports checking report definitions before expecting matching totals. Record the selected windows and reporting basis rather than assuming a universal default.
Match the symptom to the evidence
The following table is a suggested investigation order, not a network requirement. Each row concerns a different reporting layer.
| Decision or approach | Source-backed capability | Limitation | Suggested check |
|---|---|---|---|
| Compare attributed campaign events | Adjust distinguishes attributed events from total events received by Meta. | The populations can differ. | Select campaign-attributed events on both sides. |
| Compare event reporting periods | AppsFlyer distinguishes activity-based and lifetime-based dashboards. | The same event name can appear under different reporting bases. | Match the report basis and time zone. |
| Investigate missing spend or clicks | AppsFlyer's FAQ says aggregated cost, clicks, and impressions arrive periodically. | Those metrics have a different refresh pattern from installs and events. | Check synchronization before interpreting a fresh gap. |
| Investigate missing export detail | AppsFlyer's integration guide makes full device-level attribution visibility conditional on AMM acceptance. | Earlier conversions retain restrictions. | Check acceptance status against the affected conversions. |
| Use row-level Meta attribution in internal analysis | Branch documents non-aggregated last-touch data for advertisers accepting AMM terms. | Branch describes a measurement-access change. | Keep access changes separate from campaign-performance conclusions. |
The factual bases are Adjust's integration details, AppsFlyer's discrepancies guide, AppsFlyer's FAQ, AppsFlyer's integration setup, and Branch's AMM documentation.
Trace delivery and synchronization separately
AppsFlyer lists unmapped events, unsent revenue, and incorrectly structured event values as possible causes of differences. It also warns that reporting in-app events through both its integration and the Facebook software development kit can create duplicates. Review the route for the specific event before changing settings; a reporting discrepancy alone does not identify its cause.
For spend comparisons, AppsFlyer's FAQ explains that cost comes from Meta while AppsFlyer calculates installs using its own attribution rules. Reported cost per install can therefore differ even when spend matches. The same FAQ identifies campaign-access permissions as a possible reason for missing cost data. These are separate checks: whether spend was imported completely, and whether the install populations are comparable.
Our suggested decision log should record the symptom, affected app and campaign, report names, and unresolved explanation. The measurement data path provides a place to continue defining the event and reporting basis.
Check eligibility before expecting export detail
Advanced Mobile Measurement, or AMM, concerns access to attribution detail. AppsFlyer's setup guide says an app administrator must accept the terms, and full device-level visibility applies to new attributed devices after acceptance. Events associated with earlier conversions remain restricted. A later export should therefore not be assumed to reconstruct unrestricted historical attribution.
Branch likewise requires acceptance of Meta's AMM terms for non-aggregated last-touch information and an app Administrator role to accept them. Branch explicitly says the change does not alter the data it receives from Meta and that it does not expect campaign performance to change. Our interpretation is to treat newly available detail as an analysis capability, not evidence of better acquisition results.
AppsFlyer's FAQ also says agencies cannot receive Meta raw data; advertiser access should not be treated as agency access. A universal market or account eligibility list is not specified in the cited documentation. Check the applicable app, integration, and permissions before promising a particular export.
What to review
- Check that both reports use campaign-attributed events when evaluating campaign performance.
- Compare attribution windows, time zones, and activity or lifetime reporting bases.
- Review event mapping, revenue transmission, and overlapping reporting routes for the affected event.
- Check cost synchronization and campaign-access permissions before judging missing spend.
- Review AMM acceptance and conversion timing before interpreting restricted export fields.
- Record unresolved differences and the evidence needed before using the comparison to change budget.



