Follow these steps to integrate Adjust attribution data in to your Unity game.

1. Integrate our deltaDNAUnity SDK into your game as normal, as described at deltaDNA Unity SDK

2. Add the adjustAttribution event to your game on from the event management tool. If you view or edit the adjust Attribution event you will be able to see the attribution parameter mapping.

3. Integrate the latest Adjust Unity SDK: https://github.com/adjust/unity_sdk

4. Follow section 7 of the docs in that page to implement and link in a responseDelegate, then use the received data to populate and send an adjustAttribution event using the deltaDNA SDK

add-adjust-event

NB :

  • You should always populate all adjust attribution fields and send empty strings for any missing values to ensure that the LAST value of any attribution fields is always correctly set in your user metrics.
  • acquisitionChannel : It is up to you what you populate the acquisition channel parameter, there is no common definition of this parameter across attribution providers and games. This is your highest level attribution parameter. It is used as a Dimension in Slice & Dice and is available as a filter across all your deltaDNA charts. It  is also visible on all events in Data Mining and Direct Access. It should therefore be populated with the most important, highest level, of attribution that you want to track (ask yourself, where do I spend my marketing bucks as this will generally be the level of granularity you want for the acquisition channel).Because the acquisition channel is defined as a dimension you shouldn’t populate it with too many distinct values. An acquisition channel list of 12 entries is great to work with but you’ll give yourself headaches if you try and define hundreds of different acquisition channels.Many games will concatenate a few attribution parameters together to form their acquisition channel. E.G <Network>::<Campaign> might return TapJoy :: Halloween Campaign 2014 etc..
  • The acquisition channel parameter is limited to 72 characters long.
  • Not all attribution data is available immediately from the Adjust SDK. It is suggested that you read from the Adjust SDK when the activityKind parameter = SESSION and the network is not ORGANIC as this will prevent issues where Twitter and Facebook attribution data are falsely reported as ORGANIC in the adjust SDK prior to the real attribution coming through. We understand this is due to fixed in Adjust SDK v4 SDK.
  • Data sharing with deltaDNA will need to take into account any agreements you have entered into as appropriate – see Adjust’s notes in https://github.com/adjust/sdks/blob/master/doc/attribution-data.md and Facebook https://www.facebook.com/ads/manage/advanced_mobile_measurement/tos