Как сопоставить доходы от рекламы с показателями конверсии

CV Mapping Recommendations #

1. How to map ad revenue to Конверсия values #

1. Determine the Конверсия value categories for every aggregated ad revenue computed on the device within the 24 hours following installation, based on historical data.
2. Implement the Конверсия value buckets in the SDK: map accumulated ad revenue to Конверсия values.
3. Send the corresponding Конверсия value to Tenjin (and Apple) using the updatePostbackConversionValue(_:) method in the Tenjin SDK when the ad impression happens every time until 24 hours of Установите.

Note: The mapping of ad revenue to Конверсия values may change over time and require updates in the app. You also need to integrate Impression Level Revenue Data(ILRD) in the mediation SDK.

2. How to map ad impressions to Конверсия values #

1. Figure out the Конверсия value buckets for each accumulated ad impression calculated on the device for 24 hours since the Установите using historical data.
2. Implement the Конверсия value buckets in the SDK: map accumulated ad impressions to Конверсия values.
3. Send the Конверсия value (impression counts) to Tenjin (and Apple) using updatePostbackConversionValue(_:) method in the Tenjin SDK every time the impression happens until the first 24 hours of Установите.

Note: The mapping of ad impressions to Конверсия values may change over time and require updates in the app.

3. How to map sessions to Конверсия values #

1. Count the sessions as they are accumulated over a 24 hour period since the Установите.
2. Send the CV (accumulated Сессия count) to Tenjin (and Apple) using updatePostbackConversionValue(_:) method in Tenjin SDK every time the Сессия occurs until the first 24 hours of Установите.

Examples #

• IAP and In-App event mapping
• Ad Impressions and IAP mapping (Hybrid Games)
• Custom events mapping

Understanding Postback Timer (For SKAN 3.0 or lower) #

In the postback sent from Apple to the рекламная сеть, there are two different types of timers:

1. A 24 hours timer: This can be reset multiple times and has a defined duration of 24 hours
2. A Random timer: Once it starts, it can’t reset. The duration is random, between 0-24hours

• When you fire updatePostbackConversionValue(), the 24 hours timer starts. If you decide to fire updatePostbackConversionValue(_:) again, the 24 hours timer is reset to zero and starts again.
• Каждый раз, когда вы стреляете updatePostbackConversionValue(_:), the 24 hours timer will reset.
• Suppose you don’t fire updatePostbackConversionValue(_:) before the 24 hours timer expires, a random timer will start. Once the random timer starts, you can’t update the Конверсия value anymore.
• At the end of the random timer, the postback is sent to the ad network. This postback may or may not include a Конверсия value (it will be the latest value you set for this specific user)

In Tenjin, we give developers full flexibility to choose whatever Конверсия values they want to map to a specific user event. Tenjin’s Customer Success team is happy to work with you to figure out the best implementation for your app. Please contact support@tenjin.com for more custom solutions.

(SKAN 4.0 postback timers) SKAN 4.0 allows you set more complex timer systems. You can read about it здесь