Skip to content

Attribution API

The Attribution API is for sending attribution campaign events (identified by idfaidfv, or adid) that contain attribution information.

Get interactive examples for this API

The Amplitude Developers Postman profile has a collection of the example requests included in this documentation, including detailed responses for each call. You don't need a Postman account to browse.

If you already use Postman, you can fork and run the collection in Postman.


This API doesn't use authorization, but uses your API key. Pass your API key in the URL of the request like{{api-key}}.

See Find your Amplitude Project API Credentials for help locating your credentials.


Region Endpoint
Standard Server
EU Residency Server


  • When Amplitude can't match attribution events to an existing user, they're held for up to 72 hours for potential user matching. If an event isn't logged for a matching user within 72 hours of receiving the attribution data, then Amplitude drops the attribution data.
  • For most of Amplitude's partners, attribution is matched to Amplitude users and events via the Advertising ID (IDFA, IDFV, or ADID). Therefore, you must send the Advertising ID for attribution requests and you must set the idfa, idfv, and adid fields in Amplitude as the Advertising ID.
  • If you are using the iOS SDK or Android SDK, you can enable tracking of the Advertising ID by following the instructions here. If you are using a JavaScript SDK or React Native, these don't have the functionality to collect Advertising ID automatically due to Google's and Apple's privacy rules around advertising ID and web tracking. You have to send the Advertising ID through the HTTP API endpoint so that Amplitude can match attribution data/events. See keys in the HTTP API V2 doc.

Differences between HTTP API and Attribution API

The HTTP API is for sending event data to Amplitude. These events must have a user ID or a device ID, and are ingested immediately. The Attribution API is for sending attribution campaign events (identified by IDFA, IDFV, or ADID) that contain attribution information. The big difference between the APIs is that if Amplitude can't match the user when it receives an attribution event, the event is held for up to 72 hours. If Amplitude receives regular events with user information that matches the attribution events, the attribution events are ingested into Amplitude. Otherwise, they're discarded. This allows you to send attribution information without worrying about polluting Amplitude with events from people who never actually use the app.

Send an attribution event

Send a POST request to with two arguments: api_key and event.

Required arguments

Name Description Example
api_key Required. The project's API key. {{api_key}}
event Required. A request parameter representing the event, in JSON format. {"event_type":"[YOUR COMPANY] Install", "idfa": "AEBE52E7-03EE-455A-B3C4-E57283966239", "user_properties": {"[YOUR COMPANY] media source": "facebook", "[YOUR COMPANY] campaign": "refer-a-friend"}, "platform": "ios"}

Event argument keys

These keys are available for the Event argument.

Description Example
event_type Required. String. The event info. Prefix with brackets [YOUR COMPANY]. [YOUR COMPANY] Install
platform Required. String. Either ios or android. ios
idfa or idfv Required for iOS. String. The Identifier for Advertiser or the Identifier for Vendor. You must include at least one for iOS devices. AEBE52E7-03EE-455A-B3C4-E57283966239
adid Required for Android. String. The Google ADID, or Amazon Advertising ID for Amazon devices. AEBE52E7-03EE-455A-B3C4-E57283966239
android_id Optional. String. (Android) The Android ID AEBE52E7-03EE-455A-B3C4-E57283966239
user_properties Optional. Dictionary. A dictionary of attribution properties prefixed with brackets [YOUR COMPANY]. {"[YOUR COMPANY] media source": "Facebook"}
time Optional. Long. Timestamp of the event in milliseconds since epoch. 1396381378123. It's set to the upload time by default

Example request

iOS Attribution (click to expand)

This is an example attribution for iOS.

curl --location --request POST '' \
--data-urlencode 'api_key=123456789' \
--data-urlencode 'event={"event_type":"[YOUR COMPANY] Install", "idfa": "AEBE52E7-03EE-455A-B3C4-E57283966239", "user_properties": {"[YOUR COMPANY] media source": "facebook", "[YOUR COMPANY] campaign": "refer-a-friend"}, "platform": "ios"}'
POST /attribution HTTP/1.1
Content-Length: 365

Android Attribution (click to expand)

This is an example attribution for Android.

curl --location -g --request POST '{"event_type":"[YOUR COMPANY] Install","adid": "AEBE52E7-03EE-455A-B3C4-E57283966239", "user_properties": {"[YOUR COMPANY] media source": "facebook", "[YOUR COMPANY] campaign": "refer-a-friend"}, "platform": "android"}'
POST /attribution?api_key={{api_key}}&event={"event_type":"[YOUR COMPANY] Install","adid": "AEBE52E7-03EE-455A-B3C4-E57283966239", "user_properties": {"[YOUR COMPANY] media source": "facebook", "[YOUR COMPANY] campaign": "refer-a-friend"}, "platform": "android"} HTTP/1.1


Code Message
200 Success
400 The expected JSON is formatted incorrectly.

Was this page helpful?