Migrating to Adapty requires more than switching the SDK. Your third-party analytics and attribution integrations — tools like Amplitude and Adjust — also need a coordinated switch. Done carefully, the transition produces few duplicate or missing events and does not disrupt your campaigns.

Map your events

Event names are customizable in most Adapty integrations. You can configure them to match the names already in use in your dashboards and campaigns. Your analytics and campaign reporting will continue to work with the same event names after the switch. To see the full list of events available in Adapty, see Events.

For Adjust, the integration uses event IDs instead of custom event names. Transfer your existing event IDs from the Adjust dashboard to the Adapty integration configuration. See the Adjust integration guide for details.

How Adapty creates integration events

To send an event to an integration, Adapty must have a user profile. A profile is created in one of two ways:

• Historical import: The profile is created when you import historical transaction data before the SDK goes live.
• SDK interaction: The profile is created automatically when the user opens the app with the Adapty SDK for the first time.

Adapty learns about purchases made in the legacy system in real time. But it can only send an integration event once the buyer’s profile exists. A profile is created when the user opens the app with the Adapty SDK. Users who do not update to the new version will not generate integration events.

Prepare before migration day

Exclude historical events

Enable Exclude Historical Events in your integration settings. This prevents events that predate the user’s first Adapty SDK session from being sent to the integration.

This setting is especially important during historical import, when Adapty processes a large volume of past transactions at once. Without it, those transactions will generate a large volume of events in your analytics tool.

Set up the integration in advance

Adapty lets you configure and test an integration while keeping it disabled. You can set up credentials, event mapping, and filters without activating the integration until you are ready. The setup is preserved when you enable it, so nothing is lost by keeping it off until migration day.

To find your integration, see Attribution integrations, Analytics integrations, Messaging service integrations, or Webhook and ETL integrations.

Switch on migration day

Disable the integration in your legacy solution and enable it in Adapty at the same time. Running both simultaneously will produce duplicate events.

Pause large acquisition campaigns on migration day. This reduces the risk of campaign optimization errors caused by events in the overlap window.

What to expect

Some missing or duplicate integration events during the migration are unavoidable. When the switch is done correctly, the number of affected events is negligible.

The main source of gaps is the timing described above: Adapty can only send integration events for a purchase after the user’s profile exists. Purchases made in the legacy system do not generate Adapty integration events until the buyer opens the app with the Adapty SDK.

Integrations vs. server-to-server notifications

Adapty recommends using integrations rather than forwarding raw server-to-server store notifications to your analytics or attribution tools directly.

With integrations:

• Unified format: Events from all stores — App Store, Google Play, Stripe — use the same event format.
• Enriched data: Events include data Adapty collects, such as subscription state and user attributes. Raw notifications do not include this.