Managing the Conversion Value

The app determines the actions that need to be measured, and calls the updateConversionValue method to update the conversion value. The method transmits integers from 0 to 63 to advertisers and advertising networks, so it is impossible to track the actions of a particular user.

Since it is impossible to associate the conversion value with a specific user, it is measured in comparison with other data channels by efficiency.

Within 24 hours after it starts working, the app sends the first conversion values. They are updated every 24 hours, but are taken into account only when the conversion value increases.

The conversion value will be updated until it reaches the maximum or 24 hours have passed since the last increase. As soon as the conversion value is fixed, its postback is sent to the advertising network within a day.

AppMetrica offers several methods for measuring the conversion value. Choose the one that suits you best:

• Conversions evaluates the conversion rate of any 6 target events.
• Number of events calculates how many target events users have completed on average and in total.
• Revenue calculates the total amount of purchases, ARPU, the number and share of paying users (based on Revenue or E-commerce events).

Configure the desired option directly in the interface, and the AppMetrica SDK will automatically measure and send the conversion value to SKAdNetwork.

Advantages:

• You don't need to spend time on development and testing (SDK version 4.0.0 is enough).
• If the conversion measurement method changes, you don't need to update the app. The new method is applied on all versions simultaneously and automatically.

An app should have uniform rules for measuring the conversion value. The “another conversion scheme is linked” warning means that your app also uses another APIKey, that has another measurement configured.

For one APIKey in several apps, you can apply the same conversion value measurement scheme.

The chosen type sets which actions in the app affect the conversion value.

The advertising network won't receive a postback as long as the conversion value continues to increase more often than once a day. When measuring constantly growing metrics, such as the number of events or revenue, it may be useful to limit the period during which AppMetrica sends the conversion value.

Example

Your users view dozens, and sometimes hundreds of posts per day, so you use a step size of 10, the maximum is, respectively, 621 post views. For users who consistently view 10-15 posts a day, the conversion value will be measured for almost 2 months, and all this time you won't even know about them.

The period restriction makes sense if you plan to change the measurement object. Since the SKAdNetwork postback does not contain data about this, the value calculated according to the previous model, but received at the time of the new one, may distort the results.

Example

You measure the number of event A. On Monday, a user installs your app and the conversion value increases every day. On Wednesday, the model changes to revenue. The user continues to use the app until Friday inclusive, and stops at the weekend. At the end of the week, a postback comes with a conversion value of 10, which is taken as $10 of revenue from this user, although in reality there was no revenue. If you limit the period to 2 days, this won't happen.