63 Conversion Values mode

Create a tailored conversion value mapping for your app using all 63 conversion values. Use the Conversion Hub's simple yet powerful editor to set up your conversion values to measure exactly what you need to.

Create a new mapping

To create a new 63 Conversion Values 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.

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 or Save Draft if you would like to return later.

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.

Start your Fine value mapping

Now you can start mapping your fine conversion values for postback 1.

(Optional) Filter ad revenue sources: You can select the specific ad revenue sources you would like considering for your revenue conversion values.

Conditions

63 Conversion Values mode gives you access to several conditions you can use to measure user interaction in your app.

• Session – the user's in-app session.
• Session count – the number of times a user initiates a session.
• Event – an event token you want to track.
• Event count – the number of times a user triggers an event in your app.
• Event revenue – the amount of revenue generated by a specific event.
• Ad revenue – the amount generated by a user's engagement with ads.
• In-app purchases (IAP)– the amount generated by users spending money in your app.
• Total revenue – the total amount generated by events, purchases, and ad revenue.

Revenue ranges

Map ranges of revenue to conversion values to measure how much revenue your users are generating. You can map each conversion value yourself to customize the values you want to measure, or let the Conversion Hub fill your range automatically.

To create a new revenue mapping:

1. Add a new conversion value mapping with one of the following revenue types:
   1. Event revenue
   2. Ad revenue
   3. In-app purchases
   4. Total revenue
   You can choose one revenue type. This is because event revenue is a subset of in-app purchases, and in-app purchases and ad revenue are a subset of total revenue. So, In-app revenue is the sum of all event revenue, and total revenue is the sum of in-app purchases plus ad revenue.
2. Your revenue range should start at 0, so leave your first Min field empty or enter 0.

You don’t have to start your revenue range at 0 unless you are running a Meta VO campaign, but it is best practice. This is because of currency conversion. For example, if your first revenue range is $0.01-$0.99 for the first conversion value (CV=1), but then a revenue of $0.0009 is measured after currency conversion, your conversion value won’t update to 1 because it’s outside the defined revenue range.

1. Enter your Max value.

When a user generates revenue between these two values, their conversion value updates. Add more mappings to create a revenue range. Here’s how it works:

When there is an overlap between conversion value ranges, Adjust prioritizes the highest conversion value that matches. For example, let’s say you map the following revenue ranges:

• 1.5.-2.5 = CV2
• 2.5-5 = CV3

If Adjust measures a revenue value of 2.5, the conversion value updates to CV=3 as it's the higher conversion value that matches the measured revenue.

If your revenue range starts with 0, such as a revenue range of 0-1.5 mapped to CV=1, the conversion value updates only when a revenue value greater than 0 is measured. If no revenue is measured, the conversion value stays at CV=0.

You can map multiple conversion values at once by using the checkboxes next to each value. The Conversion Hub can then create a revenue range for these values using one of the following distribution types:

1. Linear – the revenue range is distributed evenly between all selected conversion values.
2. Exponential – the revenue range is distributed between the conversion values with exponentially bigger amounts.

Event and session counts

In this section, we’ll describe what your possibilities for event and session counts are.

• You can use exactly the same Max count as the Min count. For example:
  • Session count Min=3, session count Max=3.
  This means that exactly three sessions should be triggered for this condition to be met.
  • Event count Min=10, event count Max=10.
  This means that this event should be triggered exactly 10 times for this condition to be met.
• You can use ranges in the session and event count conditions. For example:
  • Session count Min=3, session count Max=6.
  This means that at least three sessions and up to and including 6 sessions should be triggered for this condition to be met.
  • Event count Min=10, event count Max=20.
  This means that this event should be triggered at least 10 times, and up to and including 20 times for this condition to be met.
• You can set count Min=1 and count Max=1. That is exactly the same as setting a condition for:
  • Session
  • Event
• You can't use 0 in a session, event, or session count. As that's the same as saying that a session or an event should not occur.

Bulk mapping and CSV upload

You can use the the bulk mapping or the CSV upload feature to map multiple conversion values.

Bulk mapping

Select the checkbox ☐ next to each conversion value you want to include.

Select Bulk mapping.

Choose your Condition.

Enter your Minimum and Maximum revenues.

Choose your Distribution.

Select Assign.

The Conversion Hub assigns your revenue range to the selected conversion values.

1/7

(1/7)

(2/7)

(3/7)

(4/7)

(5/7)

(6/7)

(7/7)

1. Select the checkbox (☐) next to each conversion value you want to include in the mapping.
2. Select Bulk mapping in the banner that appears at the bottom of the screen.
3. Choose the Condition you want to measure.
4. Enter your Minimum and Maximum revenues.
5. Choose your Distribution.
6. Select Assign.

The Conversion Hub assigns your revenue range to the selected conversion values.

Upload a CSV file

To upload your mapped conversion values as a CSV file, follow these steps:

1. Click Download to download the template. This is optional, but use the template for best results.
2. Drag and drop your file or Browse to upload your configuration.
3. Refer to the preview configuration to check that your values are mapped correctly.
4. Click Upload CSV.

Your conversion values are now mapped in the Conversion Hub.

Multiple condition mappings

You can map multiple conditions to each conversion value. Adjust updates a user's conversion value only once every condition in a mapping is met. This means that you can create a detailed picture of your user's journey in your app.

To add multiple conditions to a conversion value:

1. Add a new mapping.
2. Select the add icon () to add a new condition.
3. Select your new condition and fill out all the required fields.
4. Repeat this action to add more conditions to the conversion value. You can delete a condition by selecting the delete icon () next to it.

Time intervals

The Conversion Hub allows you to record the time interval in which a condition is met. You can assign a time interval to each mapped conversion value to more precisely measure how users are interacting with your app.

To assign a time interval to a conversion value:

1. Select the time interval icon () next to your conversion value.
2. Enter the interval start and interval end values to define the time range you want to measure.
3. Select Apply to save the time interval.

The user's conversion value only updates if all conditions are met within the specified time interval.

Add Coarse conversion values

1. Map your coarse conversion values.

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.

1. 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.

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.

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.

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.