Migrate Historical Data

       Please read this page before you migrate historical user data into SolarEngine to avoid being charged twice due to re-attribution and prevent data gap issues.

A brief description:

       When migrating from other MMPs to SolarEngine, you need to complete the following:

• Create product and app on SolarEngine
• Integrate SolarEngine SDK with appkey
• Pause advertising on existing channels
• Device ID migration [important]
• Migrate ad campaigns
• View attribution data

Step 1: SDK Integration

• Integrate SE SDK in your app

       When integrating the SE SDK, you can decide whether to immediately remove other MMP SDKs from your app and switch directly to SolarEngine, or keep the other MMP SDKs for a few weeks and use both SDKs simultaneously during the transition period.

       It is recommended to remove other MMP SDKs because this method allows quick transition and avoids duplicate attribution. To keep other MMP SDKs, you can compare data attributed by SolarEngine and other MMPs.

Step 2: Pause advertising on existing channels

       If you decide to remove the other MMP SDKs, please log in to your advertising account and pause user acquisition.

       If you decide to keep the other MMP SDKs, please log in your advertising account and pause advertising first, and then disable the data postback for existing channels on other MMPs.

Note:

       If you have previously authorized your other MMP account in SolarEngine before you start to use our attribution services, please remove the association between SE and other MMPs, in case SE receives the attribution results from both SE and other MMPs.

Step 3: Device ID Migration

       For a completely new product, you can ignore this step and proceed with the subsequent procedures, as there are no historical users to import.

       For existing products, if there is a large number of historical users, we strongly recommend importing their device IDs into our system to avoid duplicate attribution and duplicate payments for UA.

       If you decide to migrate device IDs, please provide the historical data offline following these steps after app debugging in SE. We will update with you once we complete data processing. Please wait for our response before proceeding to the next step.

Data format requirements:

• CSV format with UTF-8 encoding
• CSV filename requirement: appkey_os, lowercase. Supported operating systems (os) include Android and iOS.    

   e.g. 475ba3ff398ba823_ios.csv, 22e0b37db504f0c7_android.csv

• Device IDs allowed for importing:
• Android: GAID, OAID, IMEI1, IMEI2, Android ID (please provide original values)
• iOS: IDFA, IDFV (please provide original values)

Data content requirements:

       Please strictly adhere to the required header format below and do not adjust field positions or miss any fields.

Step 4: Publish App on Marketplaces

       Publish your app on marketplaces.

Note:

       We recommend that you fill in the attribution results from other MMPs into their respective fields to facilitate data viewing after switching to our platform.

       Please place the different device ID values of the same device on the same row for our recording convenience.

       The imported attribution results will be consolidated under the "import_device" channel in Attribution Report.

       The recommended import method and data format are as follows:

Here is an email template for requesting historical data migration:

Email title: SE Advertiser Company Name-Data Migration Application

Recipient: operation@solar-engine.com

Content:

SE advertiser company name: xxx

SE operations personnel in contact: xxx

Data to be migrated includes the following:

PS: The above application information has been finally confirmed.