Amplitude

​

Overview

​

How it works

​

Events and properties

​

Event properties

​

Attribution user properties

​

How users are matched

​

Setup

1. In Amplitude, copy the API key of the project that should receive Appstack data (Organization settings → API Keys).
2. In the Appstack console, open the Integrations page of your project and select Amplitude.
3. In the Credentials section, select the region of your Amplitude project (United States or European Union) and paste your API key. The key can only contain letters and numbers.
4. Connect the integration.
5. In the Events to forward section, choose which events to send, as described below, and save.
6. Optional but recommended: pass your own user ID as customerUserId when you configure the Appstack SDK, so events match your existing Amplitude users.

​

Choose which events to send

• Event selector. Pick the events you want in Amplitude from the events Appstack has received for your app: SDK events, server-to-server events and subscription events from connected providers such as RevenueCat. The install event is always sent and cannot be removed. A new connection sends only the install event until you save a selection.
• Only send attributed events. A switch, off by default. Off sends all events, including those of organic installs. On excludes events from organic installs.

​

Sample payloads

​

Purchase event (Batch API)

{
  "api_key": "<your_amplitude_api_key>",
  "events": [
    {
      "event_type": "appstack_purchase",
      "time": 1789491346000,
      "insert_id": "77e84ab86aa92a8406a07ec051123c34",
      "user_id": "<your_user_id>",
      "adid": "<advertising_id>",
      "platform": "android",
      "country": "US",
      "revenue": 4.99,
      "event_properties": {
        "event_id": "357431a2-b306-4531-8d23-56904bf8c45b",
        "matching_type": "<matching_type>",
        "click_to_first_open_hours": 3,
        "confidence_score": "high",
        "revenue_usd": 5.39,
        "currency": "EUR",
        "appstack_media_source": "meta",
        "appstack_campaign": "<campaign_name>",
        "appstack_adset": "<adset_name>",
        "appstack_ad": "<ad_name>",
        "appstack_install_type": "none",
        "appstack_app_id": "com.example.app",
        "appstack_app_name": "Example App"
      },
      "user_properties": {
        "$set": {
          "appstack_media_source": "meta",
          "appstack_campaign": "<campaign_name>",
          "appstack_adset": "<adset_name>",
          "appstack_ad": "<ad_name>",
          "appstack_install_type": "none",
          "appstack_app_id": "com.example.app",
          "appstack_app_name": "Example App"
        }
      }
    }
  ]
}

​

Install event (Attribution API)

api_key=<your_amplitude_api_key>
event={
  "event_type": "appstack_install",
  "time": 1789492189000,
  "platform": "android",
  "adid": "<advertising_id>",
  "user_properties": {
    "appstack_media_source": "meta",
    "appstack_campaign": "<campaign_name>",
    "appstack_adset": "<adset_name>",
    "appstack_ad": "<ad_name>",
    "appstack_install_type": "none",
    "appstack_app_id": "com.example.app",
    "appstack_app_name": "Example App"
  }
}

​

Limitations and troubleshooting

• Install counts can differ. Installs in Amplitude can differ slightly from Appstack or from your own install events, because matching depends on device identifiers.
• Installs show up as new users with one event. The device identifier did not match an existing Amplitude user. Possible causes are a user who opted out of ad tracking, or an Amplitude SDK that uses a device ID Amplitude cannot match on, such as the Android App Set ID. Passing customerUserId does not help installs, because the Attribution API only matches on device identifiers.
• Some campaigns appear as IDs. When no ad network integration has resolved a name, appstack_campaign, appstack_adset and appstack_ad hold the ID instead. Apple Search Ads is one case: Apple does not share campaign names, so appstack_campaign holds the campaign ID and appstack_media_source is apple.
• Events from before you connect are not sent. The first sync only sets the starting point. Appstack sends events that arrive after it.
• Very high event volumes can delay the sync. Appstack uploads batches of up to 1,000 events, about 35 seconds apart. Select only the events you need.
• Sync is not real time. Appstack syncs about once an hour, so new events can take over an hour to appear in Amplitude.