6 Bits mode

Focus your campaign on up to 6 key events performed in the first 24 hours - 2 days after install. 6 Bit mode lets you easily define which events are most useful to you and assign them to conversion value bits.

Create a new mapping

To create a new 6 Bits mapping:

1. Under AppView, select All apps.
2. Select your app from the list or use the search bar to find it.
3. Select SKAN Conversion Hub.
4. Select Map conversion values.
5. Select Advanced setup in the Map conversion values modal that appears.

1. Set your measurement windows

1. (Optional) SKAN 3 CV window: For users where the SKAN 3 framework is still applicable we recommend the default 24 hours; however, you can change it to any hour less than 24. The CV window determines the period of time after an install in which conversion values can be updated. This window applies only to the first postback.
2. (Optional) lockWindow: We don’t recommend changing the default postback schedule or using a lockWindow for any of the three postbacks during the early testing phases. If you do change your lockWindows be sure to share this information with your partners.
3. Select Next to continue the mapping for your app. Select Save draft to save a draft of your mapping to return to later. Select Close at the top right to close the editor without saving any changes.

Optional: Add lockWindows

While we generally advise against the use of lockWindows, if you do choose to work with the feature then set it in the first measurement window. This lets you assess how well the campaign is converting. You can then use the subsequent second and third postbacks to get as much detailed data as possible.

From the default postback schedule, you can select Edit to add lockWindows.

Set a static window: If the majority of your users perform a key event at a specific time after install, you can lock the window at this point to shorten the time you need to wait for the postback.

When you do this, you'll see a measurement gap shown on your schedule overview. This is the time between applying the SKAN lock and the end of the original measurement window. During this period, no measurement is recorded.

2. Configure the first postback

Configure your first postback to provide as much crucial information about the campaign performance as possible. This lets you decide whether to continue running it, pause, or make adjustments.

1. Set your Setup mode to 6 Bits.
2. Choose your events from the Select event dropdown menu next to each bit for the fine conversion values.
3. Map your coarse conversion values. Here are some tips for coarse mappings
4. Select Next to continue the mapping for your app. Select Save draft to save a draft of your mapping to return to later. Select Close at the top right to close the editor without saving any changes.

3. Configure the second postback

The second postback shares information from the measurement window of days 3-7. At this point, you may be interested to see if users were converted from a trial or have hit specific milestones, such as completing a purchase. As a result, these events should be given a higher value than, for example, completing a tutorial.

If you use early in-app event behavior for predictive analysis of users' life-time value, use this window to confirm whether the analysis was correct.

1. (Optional but recommended) Map your coarse conversion values.
2. Select Next to continue the mapping for your app. Select Save draft to save a draft of your mapping to return to later. Select Close at the top right to close the editor without saving any changes.

Tips for coarse value mapping

We recommend you use the coarse values to divide users into three groups:

• High-value users: When you see a large number of high-value users, it's an indication to continue and even scale-up the campaign.

• Medium-value users: With a reasonable number of mid-value users you can continue running your campaign at the current level.

• Low-value users: If you see a lot of low-value users, you should pause the campaign to avoid misspent budget.

To follow this approach, you need to identify which events from day 0 to 2 in the user journey are most important. The events you choose will be highly dependent on both your app vertical and monetization model.

4. Configure the third postback

The third postback shares information from the measurement window of days 8-35. You should have a clear profile of the user: they may have uninstalled the app or be inactive, or they may be consistently active and performing certain events.

As a result, you should build you mapping logic based on behavior at this stage in the app journey. For example, coarse values in this window should be mapped to key events that happen after day 8. This might include a certain revenue amount earned, or users retained.

You can also continue to use the data from the third postback to validate and predictions made during the first days after install. Keep in mind the tips for coarse mappings.

1. (Optional but recommended) Map your coarse conversion values.
2. Select Next to continue the mapping for your app. Select Save draft to save a draft of your mapping to return to later. Select Close at the top right to close the editor without saving any changes.

5. Review and save mapping

Once you have finished configuration of all postbacks and measurement windows, you can review your settings, edit if necessary and save the mapping.

1. Select Save and apply to apply the mapping for you app. Select Save draft to save a draft of your mapping for your app to return to later. Select Close at the top right to close the editor without saving any changes.

Update your mapping

You can change a smart setup mapping at any time after you save it. To do this:

1. Under AppView, select All apps.
2. Select your app from the list or use the search bar to find it.
3. Select SKAN Conversion Hub. Your current mapping is shown.
4. Select the edit icon () to edit your current mapping.
5. Update any of the following for your postbacks:
   1. Your measurement windows
   2. The Setup mode
   3. Your mapped values: Fine conversion values and/or Coarse conversion values

1. Select Save and apply to apply the mapping for you app. Select Save draft to save a draft of your mapping for your app to return to later. Select Close at the top right to close the editor without saving any changes.

Delete your mapping

You can delete your mappings if you no longer need them. To do this:

1. Under AppView, select All apps.
2. Select your app from the list or use the search bar to find it.
3. Select SKAN Conversion Hub. Your current mapping is shown.
4. Select the delete icon ().
5. A confirmation modal appears. Select Delete mapping to confirm you want to delete the mapping or Cancel to keep the mapping.

Analyze your data

You can analyze your SKAN data in Datascape using Adjust's dedicated SKAN dashboard. You can also set up data exports to analyze your raw data using cloud storage uploads or server callbacks. This lets you perform your own analysis and further optimize your iOS campaigns.