Adjust migration guide
Moving to Adjust from another Mobile Measurement Partner is a straightforward process. Adjust offers support and guidance every step of the way, and a range of resources for you to refer to.
Follow the instructions in this guide to complete the following migration steps:
Before you can import your historic data, you need to set up your app in AppView. All historic data is imported against your Adjust app token.
- Follow the instructions in the app setup guide.
- Once you finish setting up your app, copy your app token.
SDK documentation is available in the Developer section of the help center. While you're configuring your app to work with the Adjust SDK, make sure you put the SDK in sandbox mode and turn the logging up to verbose to capture as much information as possible. If you have any questions about SDK integration, reach out to your Adjust representative or firstname.lastname@example.org.
Once you've set up your app in AppView, you need to create an import file containing your historic data. Export your information from your previous Mobile Measurement Partner or your Business Intelligence system and format your file as follows.
Your file must be a CSV (Comma Separated Values) file that is:
- UTF-8 encoded.
- Qualified with double quotes (
Your CSV file name must contain the following information in lower case:
- The app token you saved in step 1.
- The name of the target operating system (e.g.
- The type of device ID that is contained in the file.
You must provide a file for each device ID type.
The following device ID types are available:
For Android devices targeting the Google Play Store:
For Android devices targeting the Amazon app store:
This example demonstrates the file name you should use for data with the following properties:
- Relating to an app with an Adjust app token of
- For Android devices.
- Identified by the
gps_adiddevice ID type.
") in your CSV must be escaped. To do this, enclose quoted fields in another set of double quotes like this:
Your CSV file must contain the following fields, in this order:
|Field||Required or optional||Example value||Notes|
|Required||Dashes are optional. Accepted |
|Optional||Unix install timestamp as an integer, specified in seconds. If this field isn't populated in the import file, the value is automatically populated with the timestamp of the import.|
|Required||Imported data should be put in a separate network to avoid confusion with live Adjust datasets. See the network mapping table for more information about how to structure this information.|
|Optional||Ad Group 1|
If you don't have information for one or more of the optional fields, insert an empty field. Each row must contain the same number of fields as the header row.
Adjust tracks installs as soon as your app is opened for the first time. If an existing user opens your app after you integrate the Adjust SDK, this is counted as an install and the install date is recorded. This means that if you use the actual name of a network in your import file, you will see a spike of new installs associated with a network even if the install events are actually coming from existing users.
To avoid this, you should import your historical data under a placeholder network called "Imported devices". This keeps your historical data separate from your live Adjust data and gives you an accurate reflection of how each network is performing. To maintain granularity, you should map each network field as follows:
|Previous system value||Adjust import CSV value||Notes|
|—||Hardcode this value to "Imported devices".|
|Ad group name|
Using this structure enables you to drill down through your existing campaign data to three sublevels.
Here is a template with a header row and values:
device_id,created_at,network,campaign,adgroup,creative <device_id>,<created_at>,Imported Devices,<network>,<campaign>,<adgroup>
<adgroup> with values from your previous system. For example:
device_id,created_at,network,campaign,adgroup,creative B1CDA5FE-BEBA-48ED-AD0F-27AE62BF82D8,1586391845,Imported Devices,ironsource,ironsource_ios_us,Ad Group 1
Once you've exported your data and verified the files meet the above criteria, upload the files to a secure location and send it to your Adjust representative. Adjust's technical team imports your CSV files and checks the data over to make sure everything looks right. Your Adjust representative will contact you when your import is complete.
Once your developers confirm they've integrated the SDK and your Adjust representative confirms they've imported your data, you can submit a new version of your app to the store. Check your app statistics to verify that existing users and new installs are being recorded as you expect.
Follow the campaign setup guides to set up campaigns with network partners and self-attributing networks. If you need support setting up a campaign, provide a list of partners to your Adjust representative.
If your plan includes dedicated support, your Adjust representative will arrange a workshop to tak you through:
- The types of campaigns you can record
- The levels of information you can receive
- How to create a campaign link
- Adjust's attribution methodology
- How to set up an iOS 14+ campaign
After this workshop, you'll be ready to reach out to your network partners for campaign configuration.
Once you've configured your campaigns, send your Adjust campaign links to your network partners so they can test the new links and update their settings.
That's it! It's time to start using the new Adjust suite. Check out the help center for guides on:
- How to analyze your data in Datascape.
- How to set up your iOS campaigns with the Adjust Conversion Hub.
- How to pull reports with the Report Services API.
- How to receive raw data exports through server callbacks and cloud storage uploads.
If you need further advice or clarification, contact your account manager or reach out to email@example.com.