This article describes how to set up the Amplitude connector.

In this article:

API Information

This connector uses the following vendor API:

Batch Limits

This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met:

  • Max number of requests: 2000
  • Max time since oldest request: 10 minutes
  • Max size of requests: 1 MB

Connector Actions

Action Name AudienceStream EventStream
Send Event

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send Event

Parameters

Parameter Description
Event Type (Required)
Android ID  
App Version  
Carrier  
City  
Country  
Designated Market Area  
Device Brand  
Device ID  
Device IP Address  
Device Manufacturer  
Device Model  
Event ID  
Google Play Services Advertising ID  
iOS Identifier for Advertiser  
iOS Identifier for Vendor  
Insert ID  
Language  
Location Latitude  
Location Longitude  
OS Name  
OS Version  
Platform  
Price  
Product ID  
Quantity  
Region  
Revenue  
Revenue Type  
Session ID  
Time  
User ID  
Event Properties A dictionary of key-value pairs that represent additional data to be sent along with the event.
Empty values are skipped and not included.
User Properties A dictionary of key-value pairs that represent additional data tied to the user. Each distinct value will show up as a user segment on the Amplitude dashboard.
Empty values are skipped and not included.
Groups Enterprise only.
A dictionary of key-value pairs that represent groups of users. See this excerpt in our Javascript SDK for more information on groups.
Empty values are skipped and not included.
Template Variables Provide template variables as data input (see: Template Variables Guide).
Name nested template variables with the dot notation (Example: items.name).
Nested template variables are typically built from data layer list attributes.
Templates Provide templates to be referenced in Body Data (see: Templates Guide).
Templates are injected by name with double curly braces into supported fields (Example: {{SomeTemplateName}}).
Public