Tune provides a platform that attributes app installs, in-app engagement, and purchases back to marketing sources.
Tune has limits around the number of unique event names and attributes their platform can process as noted here: http://developers.mobileapptracking.com/mobile-sdks-app-events-intro/
mParticle will only forward events to Tune if a package name is set or the Site ID configuration setting has been specified. If the package name is not set, you can you specify a package name in the Override Package Name configuration setting.
If the User ID setting is set to Customer ID and your app has not called setUserIdentity with the CustomerId identity type, data will still be forwarded to Tune without a User ID.
mParticle will forward Apple Search Ad Attribution values, if provided.
In order to enable mParticle’s integration with Tune, you will need an account with Tune in order to obtain your Advertiser Id. Your Advertiser Id is available on your Mobile Apps details page. Click here for information on finding your Advertiser ID and Conversion Key and here to find your Site ID.
You will also need your Private Key and Consumer Key to configure the Tune Integration. See Tune’s documentation for help finding your Private Key and Consumer Key. When you set up your key, be sure to leave the Whitelist IP Addresses field blank to leave access unrestricted.
The following general settings are forwarded to Tune:
|Parameter||mParticle details||Tune field|
|Advertiser ID||The value of setting
|Package Name||The value of setting
|Application Name||App Name||app_name|
|Application Version||App Version||app_version|
|Site ID||The value of setting
|User Agent||User Agent||user_agent|
The following user attributes are forwarded to Tune:
|User Attribute||mParticle details||Tune field|
|Gender||$Gender, 1 for female, 0 for male||gender|
|User Name||$FirstName + ’ ’ + $LastName||user_name|
The following user identities are forwarded to Tune:
|User Identity||mParticle Identity Type||Tune field|
|Facebook ID||Facebook ID||facebook_user_id|
|Google ID||Google ID||google_user_id|
|Twitter Handle||Twitter Handle||twitter_user_id|
|User ID||mParticle will forward User IDs to Tune based on the value of the User ID setting:
1. Hashed mParticle ID (default)
2. Customer ID
The following device properties are forwarded to Tune:
|Device Property||mParticle details||Tune field|
|Android Google Advertiser ID||Google Advertising ID||google_aid|
|Android Limit Ad Tracking||LimitAdTracking||google_ad_tracking_disabled|
|Apple OS IDFA||IDFA||ios_ifa|
|Apple OS IDFV||IDFV||ios_ifv|
|Apple Limit Ad Tracking||LimitAdTracking||ios_ad_tracking_disabled|
mParticle’s Tune integration supports custom mappings which allows you to map your events and attributes for Tune. mParticle provides mappings for the following Tune event types:
App Events are forwarded to Tune by using action=“conversion” and the event name is mapped to the “site_event_name” attribute. App Events containing the term “resume” will not be forwarded to Tune.
The following default mappings exist when forwarding events from mParticle to Tune:
Commerce Events are forwarded to Tune based on the incoming Product Action:
|mParticle Product Action||Tune action|
|Refund - This is mapped to the Tune action=purchase with a negative revenue amount||purchase|
The following event details are forwarded to Tune:
|mParticle event details||Tune field|
For each item in the event, the following additional fields are forwarded:
|mParticle Product details||Tune field|
|blank - used for product level tax||attribute_sub1|
|blank - used for shipping amount||attribute_sub2|
Screen Views are forwarded to Tune using action=“content_view” and the screen name is mapped to the “content_id” attribute. If you are using automatic screen tracking in our Android SDK, the automatically-generated screen view events will be forwarded to Tune using the name of the associated Activity class.
[MobileAppTracker measureAction:@"View SomeScreen"];
Session Start events are forwarded to Tune’s session measurement endpoint. Tune then determines whether each session start constitutes an ‘install,’ and ‘update’ or a ‘launch’ in Tune.
All calls to mParticle’s
logEvent SDK method with the event name “login” will be forwarded to Tune using action=“login”.
All calls to mParticle’s
logEvent SDK method with the event name “registration” will be forwarded to Tune using action=“registration”. See below for sample SDK calls and the equivalent call using mParticle’s SDK.
//MAT SDK call [MobileAppTracker measureAction:@"registration"]; //Equivalent mParticle SDK call [[MParticle sharedInstance] logEvent:@"registration"];
//MAT SDK call MobileAppTracker.getInstance().measureAction("registration"); //Equivalent mParticle SDK call mp.logEvent("registration");
The mParticle Android SDK provides a deep link API that you can use to query Tune and customize your app experience based on the parameters of deep links. Refer to the deep linking section of the Android and iOS SDKs to learn how to use these APIs. Rather than making direct API calls to the Tune SDK, this API let you write integration-agnostic apps that are easier to maintain.
|Setting Name||Data Type||Default Value||Description|
||Your Tune account’s Advertiser ID.|
||Your Tune application’s Conversion Key.|
||Your Tune application’s Site ID, found on the Mobile Apps list page under the ID column.|
||They key used to generate a request signature for all messages sent to Tune|
||The public key included with each request to Tune so the private key can be identified|
|Setting Name||Data Type||Default Value||Platform||Description|
||mParticleId||All||Select which user identity will be forwarded to Tune as your customer’s user ID|
|Override Package Name||
||All||Allows you to override your app’s package name that will be forwarded to Tune|
Was this page helpful?