概要

We’ve also created a short video to help you familiarize yourself with SKAdNetwork Reporting in Tenjin. In the video we cover what SKAdNetwork is and how Tenjin is thinking about it, what SKAdNetwork metrics you can access through Tenjin and where you can see them, and what networks or channels Tenjin supports for SKAdNetwork.

Watch the full video:

コンバージョン value is a numeric value between 0 and 63 which you can assign to a specific インストール. It’s a “signal” that will help you understand how valuable a specific user is without giving you a way to identify them. アドネットワーク can use this information to understand how valuable each インストール is for your business. This signal can help アドネットワーク identify better audiences to serve your ads and improve your campaign performances.

Below are some important characteristics you need to remember for コンバージョン values:

• You can only update the コンバージョン value with a value higher than your previous call (1-> 2 but not 3->2).
• 0 ～ 63の制限された値。
• You can measure コンバージョン values for any time frame within the user’s life time, but the longer you wait, the later the ad-networks will get the postback from Apple. In Tenjin, we recommend using 24 hours time window for this reason.
• N-Day All pLTV コンバージョン value only appears if there are enough installs from the publisher according to Apple’s privacy thresholds.

In Tenjin, we give developers full flexibility to choose whatever コンバージョン values you 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. Below are a couple of basic recommendations for apps that are mainly monetized through in-app ads.

1. Map ad revenue to コンバージョン values

• Figure out the コンバージョン value buckets for each accumulated ad revenue calculated on the device for 24 hours since the インストール using historical data.
• Implement the コンバージョン value buckets in the SDK: map accumulated ad revenue to コンバージョン values.
• Send the corresponding コンバージョン value to Tenjin (and Apple) using updatePostbackConversionValue(_:) method in the Tenjin SDK when the ad impression happens every time until 24 hours of インストール.

注: The mapping of ad revenue to コンバージョン values may change over time and require an updates in the app. You also need to integrate Impression Level Revenue Data(ILRD) in the mediation SDK.

2. Map ad impressions to コンバージョン values

• Figure out the コンバージョン value buckets for each accumulated ad impressions calculated on the device for 24 hours since the インストール using historical data.
• Implement the コンバージョン value buckets in the SDK: map accumulated ad impressions to コンバージョン values.
• 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 インストール.

注: The mapping of ad impressions to コンバージョン values may change over time and require updates in the app.

3. Sessions

• Count the sessions as they are accumulated over a 24 hour period since the インストール.
• 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 インストール.

Here is an example of コンバージョン value implementation shared by other customers:

Examples for IAP based games

In the postback sent from Apple to ad-network, there are two different types of timers:

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

- updatePostbackConversionValue()のメソッドをコールすると、24時間タイマーが起動します。その後、 updatePostbackConversionValue(_:) again, the 24 hours timer is reset to zero and starts again. Every time you fire 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)

Feel free to email to support@tenjin.com if you have any questions.

Here is the current list of the networks that support SKAdNetwork.

*: Does the network pass us SKAdNetwork conversions via postback or reporting API?

**: Conversions from dual opt-in users and Google’s modeling conversions (https://support.google.com/google-ads/answer/10081327)

\***: Conversions from dual opt-in users and Snap’s proprietary アトリビューション method, Advanced Conversions

We created a short video to help you familiarize yourself with the SKAdNetwork Report in Tenjin. In the video, we cover what SKAdNetwork is, and how Tenjin is thinking about it, what SKAdNetwork metrics you can access through Tenjin and where you can see them, and what Networks Tenjin supports for SKAdNetwork.

Watch the full video here. https://www.youtube.com/watch?v=k4mMY2WK_RE&t=1s

SKAdNetwork data is available in データエクスポーター tab. Go to ANALYZE -> Data Exporter on the dashboard, and select “SK Ad Network” as RERORT TYPE. You can apply app and channel filters for your data.

You can choose multiple group-by options from this list:

• Required dimensions
• App
• Tenjin dimensions
• チャンネル
• キャンペーン
• SK Adnetwork dimensions
• コンバージョン 価値
• Fidelity Type
• SK Channel
• SK Campaign
• SK Source app

You can also select multiple metrics from this list:

• コンバージョン Value Count (Default)
• コンバージョン Value Average (Default)
• コンバージョン Value Total
• First Download Count
• First Download コンバージョン Value Average
• First Download コンバージョン Value Total
• Redownload Count
• Redownload コンバージョン Value Average
• Redownload コンバージョン Value Total
• Assists
• Redownload Assists
• First Download Assists

You can see the definition of those metrics こちら.