Chapter 8 / 9
Adjust → Amplitude concept glossary
For each concept you know in Adjust: its Amplitude counterpart and the most important difference between them. Start typing to search; the search covers both columns and the notes.
| Adjust | Amplitude | Difference to watch |
|---|---|---|
| App token | Project and API key | In Amplitude it is common to have a separate project per environment; each project has its own key. |
| Sandbox / production environment | Separate test and production projects | Separated by a filter in Adjust, usually separate projects in Amplitude. |
| Event token | Event name (event type) | Not defined in advance in Amplitude; created on first send. |
| Callback parameter | Event property | In Amplitude every property is a filter and breakdown dimension. |
| Partner parameter | Event property | In Adjust it's for forwarding to networks; in Amplitude it's for analysis. |
| Session / global parameter | User property | Persistent info carried on every event; in Amplitude the value can change over time. |
| Install | New user | One is device-based, the other is based on the merged person. |
| Reattribution | User property update | Whether the first or latest source is kept depends on the integration setup. |
| Session | Session | Session definition and timeout may differ. |
| ADID | device_id / Amplitude ID | Amplitude ID represents the person merged across devices. |
| App-side user ID | user_id | The basis of identity merging in Amplitude; must be stable and unique. |
| Attribution (network, campaign, adgroup, creative) | User property (via the integration) | Amplitude doesn't produce attribution; it takes it from the MMP. |
| Organic | Channel property empty or organic | Unattributed paid users may also show up here. |
| SKAdNetwork data | No equivalent | Aggregated data, so it can't be tied to users. |
| Cohort report | Retention chart | In Amplitude you choose the start and return events. |
| Event report (Datascape) | Segmentation chart | Choose the counting unit (total, unique, average) explicitly. |
| Conversion rate (event / install) | Funnel | A funnel checks the same person did the steps in order within a time limit. |
| Audience | Cohort | Amplitude cohorts accept ordered and frequency-based behaviour conditions. |
| Raw data export | Export API, warehouse export | Similar purpose; the Amplitude side is closer to analytical use. |
| Callback (server notification) | Webhooks / sync destinations | Real-time event forwarding in Amplitude is more limited or a separate product. |
| S2S events API | HTTP API | Adjust needs device identifiers; Amplitude needs user_id/device_id. |
| Deduplication ID / purchase verification | insert_id | insert_id prevents resends; it does not verify purchases. |
| Revenue event | Revenue field or Revenue call | Define currency and amount format the same way in both tools. |
| Testing Console | Ingestion debugger / user lookup | To see instantly whether an event arrived. |
| Data residency (URL strategy) | Data region choice (e.g. EU project) | In Amplitude the region is chosen per project and the endpoint changes too. |
| Fraud prevention | No equivalent | Amplitude does not detect ad fraud. |
| Uninstall / reinstall | No direct equivalent | Amplitude sees loss as "dormant" in lifecycle, without knowing why. |
| Ad revenue | Revenue sent as an event | Needs a separate event or integration to reach Amplitude. |
| Dashboard (Datascape) | Dashboard / notebook | Amplitude dashboards are made of saved charts. |
| None | Journeys / Pathfinder | Shows the paths users actually take. |
| None | Stickiness / Lifecycle | Usage frequency and the mix of the active audience. |
| None | Group | Analysis at the level of the account users belong to. |
| None | Experiment | A/B tests and feature flags on the same event data. |
No term matches this search. Try a shorter word.
Verify
Product and screen names in the Amplitude column can change with Amplitude UI updates. The conceptual mapping stays the same.