If you are a mobile business partner and you are integrating with Acoustic Exchange, you must send all user information from the mobile device to Acoustic Exchange, including user information for your app and the Acoustic Campaign SDK.

Verify that the Acoustic Campaign SDK is installed.

For information about iOS devices, see Detecting the SDK on your iOS app.

For information about Android devices, see Detecting the SDK on your Android app.

The Acoustic Exchange identity matching service maps identifiers in the user information to unique Acoustic Exchange x1Ids. The mapping allows Acoustic Exchange to exchange events between products. If you do not send the required user information, Acoustic Exchange cannot map user data, and user records become duplicated in the Acoustic Exchange database.

To send user information to Acoustic Exchange, build a JSON payload that includes the unique identifiers and attributes for your mobile app and the Acoustic Campaign SDK. Some mobile business partners use the mobile advertising ID (IDFA for iOS, GAID/AAID for Android) as a unique identifier. Acoustic Campaign uses Mobile User IDs (MUIDs), ChanneIds, and the appKeys as unique identifiers. When you build the JSON payload, ensure that the payload includes the identifiers for your mobile app, such as the mobile advertising ID, and the MUID, ChannelId, and appKey from the Acoustic Campaign SDK.

In some cases, you might not know the MUID, ChannelId, or appKey or whether the Acoustic Campaign SDK is installed. Before you build your payload, check the mobile device for the Acoustic Campaign SDK, and if the MCE SDK is installed, identify the identifiers for each platform.

1. Identify the MUID, ChannelId, and appKey on the mobile device. Check out Accessing registration details to learn how to get this information. 
2. Build the JSON payload.

[{
		"name": "userid",
		"value": "1473799578000-4774159"
	},
	{
		"name": "ios_advertising_id",
		"value": "0A40F5B8-F946-4FBF-BD0A-41628CF94063"
	},
	{
		"name": "android_advertising_id",
		"value": "0A40F5B8-F946-4FBF-BD0A-41628CF94063"
	},
	{
		"name": "mobileuserid",
		"value": "RlqVsLpzJ2rdZe5y"
	}
],

"events": [{
	"code": "appInstalled",
	"timestamp": "2016-09-13T11:55:06.279Z",
	"attributes": [{
			"name": "eventName",
			"value": "AppInstall",
			"type": "string"
		},
		{
			"name": "description",
			"value": "Installevent",
			"type": "string"
		},
		{
			"name": "mediaSource",
			"value": "organic",
			"type": "string"
		},
		{
			"name": "appKey",
			"value": "id554782625",
			"type": "string"
		},
		{
			"name": "channelId",
			"value": "q25QwSE8",
			"type": "string"
		},
		{
			"name": "campaignName",
			"value": null,
			"type": "string"
		},
		{
			"name": "platform",
			"value": "ios",
			"type": "string"
		}
	]
}]

When you build the JSON payload, ensure that the payload includes identifiers for your mobile app and the Acoustic Campaign SDK. The following tables describe the required identifiers and event attributes.

Use the v1/event API to send the payload to Acoustic Exchange. For more information about the Exchange v1/event API, see Exchange Event API.