Meta Resurrects AMM: What Changes for Your Reporting Now

Meta resurrects AMM this week, updating the terms of a measurement framework it had effectively shelved before Apple's App Tracking Transparency reshaped mobile attribution in 2021. According to Mobile Dev Memo's reporting on the terms update, published Tuesday, AMM, Meta's Advanced Mobile Measurement service, allows user-level conversion attribution to pass from third-party measurement tools into Meta's ad reporting for app advertising. Read that sentence twice. User-level conversion attribution passed from third-party tools is a materially different proposition from the aggregated, privacy-preserving reporting most buyers have assumed was the permanent state of the platform since 2021, so anyone running a measurement stack built entirely around ATT-era constraints has reason to look up from the dashboard this week.

What is actually confirmed now that Meta resurrects AMM

Be precise about what this update does and does not establish. Meta updated AMM's terms. That much is a real, dated event, and it is the only part of the story a buyer can bank on today. What the public reporting leaves open is the practical scope: which advertisers gain access, what data an MMP may actually pass under the revised terms, and whether any of it changes the week-to-week reality for a typical mobile game buyer running standard app campaigns rather than a narrower set of accounts with existing AMM relationships. So treat AMM's return as a confirmed policy change with an unconfirmed footprint. Frameworks like this have historically rolled out in phases, often gated to particular verticals or account tiers long before wider availability, which is reason enough to resist assuming this immediately restores pre-ATT reporting fidelity for every advertiser on the platform.

Why AMM's history matters for reading this correctly

AMM is not a new invention. Before ATT it gave advertisers a way to route user-level conversion data through approved third-party measurement partners rather than relying solely on Meta's own pixel and SDK-based tracking. Apple's 2021 privacy changes made that kind of user-level pass-through untenable at scale on iOS, which is presumably why the framework went dormant instead of disappearing outright. Its resurrection this week suggests Meta now sees a compliant path back to at least part of that mechanism, whether by limiting the scope to Android, by confining it to users who have opted in, or by narrowing what counts as user-level under current privacy rules. None of that detail is public yet. Which is exactly why a measurement team should treat the news as a lead to chase with its own MMP account manager rather than a change to build reporting logic around today.

What to actually do with this news this week

The practical response for a measurement lead is a short list, not a stack overhaul:

• Ask the studio's MMP directly whether it participates in the updated AMM framework, and if so, what it may now pass to Meta that it was not passing last month.
• Confirm whether any change applies platform-wide or only to specific markets, account tiers or campaign types, because a reactivation announced at a terms level usually rolls out unevenly in practice.
• Watch the gap between Meta's own dashboard and the MMP's independent numbers over the following weeks for signs that the underlying data flow has actually changed, rather than assuming a terms update produces a visible shift on its own.
• Leave blended ROAS models and attribution weighting for Meta campaigns alone until the practical scope is clear, because acting on a terms change before you understand its data footprint adds a new source of reporting error instead of removing one.

The Android question sitting underneath this

One plausible reading of AMM's return, unconfirmed in the current reporting, is that it lands differently by platform. Whatever legal and privacy pressure made user-level pass-through untenable on iOS after ATT does not carry over in the same form to Android, where Meta has historically retained more device-level signal through its own SDK regardless of platform-level identifier restrictions. If the revived scope turns out to be Android-specific, or simply weighted toward Android given that platform's comparatively looser attribution environment, then it changes which advertisers benefit and how far any of this moves iOS reporting. And iOS is where four years of post-ATT measurement pain has concentrated. Ask which platform the reactivated mechanism actually touches; assuming it applies evenly across a studio's entire user base is the easiest mistake to make while reading early coverage.

Why this fits a pattern worth naming

This is not an isolated update. It follows closely on Apple's own WWDC-era AdAttributionKit refinements, which this desk covered in AdAttributionKit Re-Engagement Gets Sharper After WWDC, and it belongs to a wider pattern running through the industry this year: every major platform quietly expanding or clarifying its measurement mechanics in ways that change what a buyer can actually see, usually without a headline announcement to match the significance of the change. Individually, each one looks like a minor terms revision. Taken together they describe a measurement settlement that the platforms keep renegotiating with advertisers while regulators move the boundaries, four years into what many buyers had started treating as a fixed post-ATT status quo. So the job this year is less about picking one stable stack and defending it, and more about keeping enough discipline to notice when a platform quietly reopens a door it shut years ago, then verifying what actually walks through it before trusting the number on the other side.

A note for the next quarterly measurement review

Whatever AMM's confirmed scope turns out to be, it belongs as a standing line item in the next quarterly measurement stack review rather than a one-off news item to note and forget. The specific mechanics of this reactivation matter less than the habit it should reinforce. Platform measurement terms are living documents. Reread them on a schedule; they are not settled infrastructure a team configures once and then revisits only when something visibly breaks.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• Updating the playable ad spec for re-engagement campaigns
• Tripledot's AppLovin Apps Portfolio: A Buyer's Guide