Adjust Events API Connector Setup Guide

Connector Actions

Action name	Visitor profile	Event data
Send Event	✗	✓
Send Session	✗	✓

Configuration

Go to the connector marketplace and add a new connector. For more information, see About connectors.

After adding the connector, configure the following settings:

Authentication Token
- With Adjust’s S2S Security feature, you can guarantee the security of your S2S events and protect against spoofed requests.
- After you set up S2S authentication, each incoming request must carry a token generated in your Adjust dashboard.
- See Server-to-server (S2S) Security for more details.
- Leave the field empty if you haven’t set up S2S authentication.

Action Settings - Parameters and Options

Click Continue to configure the connector actions. Enter a name for the action and select the action type from the list.

Action - Send Event

Parameters

Parameter	Description
Event Token	Adjust event token from the dashboard.
App Token	Adjust app token from the dashboard.
Android ID	Android ID. Sent to Adjust as `android_id`. See Device identifiers.
Hashed Android ID (Lowercase, MD5)	MD5 hash of the lowercase Android ID. Sent to Adjust as `android_id_lower_md5`. The connector passes the value through as supplied and does not hash it.
Hashed Android ID (Lowercase, SHA1)	SHA1 hash of the lowercase Android ID. Sent to Adjust as `android_id_lower_sha1`. The connector passes the value through as supplied and does not hash it.
Hashed Android ID (Uppercase, MD5)	MD5 hash of the uppercase Android ID. Sent to Adjust as `android_id_upper_md5`. The connector passes the value through as supplied and does not hash it.
Hashed Android ID (Uppercase, SHA1)	SHA1 hash of the uppercase Android ID. Sent to Adjust as `android_id_upper_sha1`. The connector passes the value through as supplied and does not hash it.
Open Advertising ID	Platform-dependent Open Advertising ID. Sent to Adjust as `oaid`. See Device identifiers.
Raw Amazon Fire Advertising ID	Platform-dependent Raw Amazon Fire Advertising ID. Sent to Adjust as `fire_adid`. See Device identifiers.
Raw IDFA	iOS only. Raw IDFA Identifier. Sent to Adjust as `idfa`. See Device identifiers.
Raw IDFV	Raw IDFV Identifier. Sent to Adjust as `idfv`. See Device identifiers.
Raw Google Advertising ID	Raw Google Advertising ID Identifier. Sent to Adjust as `gps_adid`. See Device identifiers.
Roku Advertising ID	Roku device advertising ID. Sent to Adjust as `rida`. See Device identifiers.
Vizio Advertising ID	Vizio device advertising ID. Sent to Adjust as `vida`. See Device identifiers.
Tizen Advertising ID	Samsung Tizen device advertising ID. Sent to Adjust as `tifa`. See Device identifiers.
Adjust Device ID	Identifying LAT users on iOS without idfa information.
Created At Timestamp (Formatted)	Telling the exact moment an event occurred. The connector encodes the value. Example:__ `2017-01-02T15:04:05.000+0000` becomes `2017-01-02T15%3A04%3A05.000%2B0000`
Created At Timestamp (Unix)	Telling the exact moment an event occurred. Can be specified using either seconds or milliseconds.
IP Address	Event linking to third-parties, such as Google and including location-related information, such as `city` and `postal_code`) in your callbacks. The `ip_address` parameter only accepts IPv4. IPv6 is not yet supported.
Currency	Revenue event See currency code.
Environment	Environment to post the data t. Example: `environment=sandbox` or `environment=production` If this parameter is not included, the event will be pushed to the production environment.
Revenue	Revenue event value in full currency units (149.99 = $149.99). Adjust accepts a minimum value of 0.001 for this parameter.
Template Variables	Provide template variables as data input. For more information, see Connector template variables. Reference nested template variables with 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. For more information, see About connector templates.=. Templates are injected by name with double curly braces into supported fields. For example, `{{SomeTemplateName}}`.

Send Session

Use the Send Session action to establish a session with Adjust before sending events. Adjust drops events from devices it has not recorded a session for. Use this action when the source cannot start a session through the Adjust SDK, such as server-side deployments on Roku, Vizio, and Tizen devices.

Behavior:

Adjust ignores a session sent within 30 minutes of the previous one for the same device. Trigger this action on a session-start event, not on every event.
Adjust must enable server-to-server (S2S) sessions for your app before you can use this action. Contact your Adjust account manager to activate the feature.

Parameters

Parameter	Description
App Token	Adjust app token from the dashboard.
Device Identifier	Platform-dependent device or advertising ID. Map a value for each supported identifier. The connector sends the first non-empty identifier. See Device identifiers.
Recommended Additional Parameters	For accurate session attribution, Adjust recommends including the following parameters with your sessions: Adjust Device ID: Identifying LAT users on iOS without idfa information. Created At Timestamp (Formatted): Telling the exact moment a session occurred. The connector encodes the value. For example, `2017-01-02T15:04:05.000+0000` becomes `2017-01-02T15%3A04%3A05.000%2B0000`. Created At Timestamp (Unix): Telling the exact moment a session occurred. Can be specified using either seconds or milliseconds. IP Address: Session linking to third-parties and including location-related information in your callbacks. The `ip_address` parameter only accepts IPv4. IPv6 is not yet supported.
Session Parameters	App Version: App version. App Version Short: Short app version. OS Name: Operating system name. OS Version: Operating system version. Device Type: Device type. Device Name: Device name. Country: Country code. Language: Language code. Environment: Environment to post the data to (`sandbox` or `production`). If this parameter is not included, the session is pushed to the production environment. EEA, Ad Personalization, Ad User Data, NPA: Digital Markets Act (DMA) consent parameters. Custom keys (not in the dropdown) are passed through verbatim.