Meta

Guide · 22 Oct 2026

Meta app onboarding: define activation before choosing events

AppsFlyer, Adjust, and Amplitude documentation helps app buyers connect onboarding milestones with funnel analysis and Meta event mapping.

G2P Media · · 4 min read

Meta app onboarding: define activation before choosing eventsMeta

At a glance

FieldDetail
WhatChoose an onboarding milestone to measure, then assess its suitability for Meta campaign optimization.
Who it matters toApp buyers and product teams investigating what users do after installation.
WhereMeta integrations documented by AppsFlyer and Adjust; product funnel analysis documented by Amplitude.
When it appliesWhen acquisition reporting needs a defined registration, tutorial, or product activation outcome.
ActionReview the milestone definition, funnel settings, and partner mapping before changing the campaign goal.

Meta app onboarding needs an explicit definition of success before an advertiser chooses an optimization event. AppsFlyer documents post-install events such as registration and tutorial completion, while Amplitude recommends measuring the stages of activation. Our suggested approach is to define the useful behavior, inspect the onboarding journey, and then check how that event reaches Meta. AppsFlyer event overview, Amplitude activation guide.

Define the milestone before choosing its name

AppsFlyer distinguishes an event name from the parameters that describe it. It supports predefined names and custom events for app-specific scenarios, and recommends predefined names where possible to simplify partner mapping. That provides a measurement vocabulary; the team still needs to decide which behavior represents successful onboarding.

As a suggested check, write down the exact action that completes registration, the action that completes a tutorial, and the product behavior that demonstrates useful progress. Review whether those are separate milestones in your app. Avoid combining them into an activation label unless its definition makes the required behavior clear.

Amplitude’s activation guide recommends tracking the event that represents each onboarding stage, investigating drop-off paths, and comparing retention among behavioral groups. Our interpretation is to examine whether the proposed activation milestone is associated with later use before treating it as the acquisition outcome. An observed association can support a test hypothesis; it does not establish that encouraging the action will cause better retention. Amplitude activation guide.

Separate funnel diagnosis from campaign event selection

The following approaches answer different questions. The capability descriptions come from the linked vendor documentation; the suggested checks are our analysis.

ApproachSource-backed capabilityLimitationSuggested check
Product onboarding funnelAmplitude measures progress through selected events and identifies drop-off.Event order and the included user segment affect what counts as conversion.Define the starting population and required sequence.
Predefined Meta event mappingAppsFlyer and Adjust document mapping to standard events, including completed registration and tutorial completion.A familiar event name does not define your app’s trigger.Compare the implemented action with the intended milestone.
Custom activation eventAppsFlyer forwards custom event names and values; Adjust documents a custom-event optimization route.Adjust describes availability for most App Install campaigns, without establishing universal eligibility.Confirm the event is supported in the intended campaign.
Funnel timing and countingAmplitude supports unique-user or event-total counting and a rolling conversion window.These settings describe different measurement bases.Fix the counting method and completion window before comparing results.

The capabilities above are documented in Amplitude funnel setup, Amplitude funnel FAQ, AppsFlyer Meta mapping, and Adjust Meta setup.

Make the onboarding readout reproducible

Amplitude distinguishes an ordered funnel that permits intervening actions from an exact-order funnel that excludes other steps. Its segmentation setting applies to the starting event. Our suggested check is to record those choices alongside the onboarding result, especially when users can explore the app between milestones. Otherwise, a changed chart definition could be mistaken for changed onboarding behavior. Amplitude funnel setup.

Amplitude also distinguishes unique users from event totals. Its conversion window runs from entry through completion of the entire funnel. For this review, decide whether you are evaluating people reaching activation or repeated journeys through onboarding. Document the completion window and keep it consistent across the variants being compared. Amplitude funnel FAQ.

Check the event route and its eligibility

AppsFlyer documents that custom events retain their original SDK event names when forwarded to Meta, and that event names are case-sensitive. Review the exact event name used in the app, the partner mapping, and the name received by Meta. AppsFlyer Meta mapping.

For an Adjust integration, its setup documentation says to select Adjust as the data source in Meta Events Manager so Meta can receive app events and optimize toward them. It separately describes standard mapping and custom-event optimization. A universal eligibility rule or minimum event volume for a proposed custom onboarding milestone is not specified in the cited documentation. Confirm availability for the actual app and campaign before planning around it. Adjust Meta setup.

What to review

  • Define the user action that completes each onboarding milestone and keep its meaning consistent across teams.
  • Compare later retention among users who reach the proposed activation event and those who do not; treat differences as hypotheses to investigate.
  • Record funnel entry, event order, counting method, and completion window before comparing onboarding variants.
  • Check the exact partner event mapping and confirm campaign eligibility for the chosen milestone.
  • Review the event data path to connect the app trigger, measurement record, and partner event definition.

Discuss your app.

Discuss your app