Skip to content
AppDues
Log in
Contact salesSign up

Meta Ads In-App Purchase Attribution

Connect subscription activity to Meta advertising so campaign decisions can reflect what happens after install, including trials, paid starts, renewals, and cancellations.

What you can track

Use the connection to follow revenue generated over time rather than judging a campaign only by its initial purchase. Trial starts, trial conversions, and renewals can be sent directly to Meta Ads Manager. Campaign-level review can also include trials, churn, and monthly recurring revenue, helping distinguish a campaign that attracts trial users from one that produces durable subscribers.

Choosing standard event names

Choose a standard Meta event name for each subscription moment. Standard events are recommended by Meta for optimizing advertising campaigns and audiences, so they are the preferred starting point when configuring the integration.

Event mapping checklist

Trial Started — map to StartTrial. This separates early interest from a paid commitment. Trial Converted — map to Subscribe. This marks the point at which a trial becomes a paid subscription. Initial Purchase — map to Subscribe. This captures the first paid subscription event. Renewal — map to Subscribe. This captures continuing subscription revenue after the initial purchase. Non-Renewing Purchase — map to Purchase. This distinguishes a one-time purchase from recurring subscription activity. Practical check: before launching, confirm each lifecycle moment produces exactly the intended event, and review whether trial, initial-purchase, and renewal activity should remain separate in campaign reporting.

Related integrations

No-code integrations can connect real-time events and revenue data to other tools. Related attribution and measurement options include Adjust, Apple Search Ads, Singular, Branch, SplitMetrics Acquire, Tenjin, and AppsFlyer. Compare them according to the platforms, event types, and reporting workflows your team already uses.

ConfigureTargetTest