ByteBrew data-sharing reference
Review the data-sharing configuration options in the ByteBrew dashboard.
Read time 2 minutesLast updated 4 months ago
Important
The following documentation discusses products or services (“Third-party Products”) not developed, owned, or operated by Unity.
This information might be outdated or incomplete and is provided for your convenience.
Your use of any Third-party Product is subject to its own terms.
Unity makes no warranties regarding these products and isn't liable for any damages or losses arising from their use, including issues related to content, advertising, or materials from Third-party providers.
Attribution lookback settings
Use lookback settings to choose what kinds of conversions you include in attribution. In the Install Settings tab of the ByteBrew integration setup, you can choose from the following lookback options:Lookback option | Description | Notes |
|---|---|---|
| Click-through attribution | Attribute installs that occur after a user clicks on your ad. The lookback setting for Click-through attribution is the maximum window of time after a user clicks on your ad before installing your app. | Click-through attribution is required for ByteBrew integration. |
| View-through attribution | Attribute installs that occur later, after a user watched your ad but didn't immediately select it. | View-through attribution isn't required for integration. However, including view-through attribution enables you to measure the impact of impressions that don't immediately result in a click. |
Attribution data sources
Attribution sources are the engagement data sources from which you want to pass data to Unity. In the Install Settings tab of the ByteBrew integration setup, you can choose from the following options:Attribution option | Description | Notes |
|---|---|---|
| Only this partner | Pass install data from only Unity-attributed installs. | |
| All Partners and Organics | Pass data from all installs, including unattributed and organic. | This option enables Unity's models to learn from your installs across all networks, which can help to improve campaign performance. |
| This Partner and Organics | Pass data from both Unity-attributed and organic installs. |
Post-install event data-sharing
Use data-sharing options to configure what post-install event data you want to pass to Unity in your postbacks. Post-install event data is required to access optimized campaign goals with Unity, such as Return on Ad Spend (ROAS) and Retention campaigns. In the Postback Settings tab of the ByteBrew integration setup, you can choose from the following post-install event data-sharing options:Data-sharing option | Description | Associated campaign goals | Notes |
|---|---|---|---|
| Ad Watched Event | Select this option to pass Ad revenue event data to Unity. | Ensure that you've implemented the newest ad revenue event in the ByteBrew SDK to track impressions based on revenue. | |
| User App Open Event | Select this option to pass Session event data to Unity. | ||
| In-App Purchase Event | Select this option to pass Purchase event data to Unity. |
Postback data sources
Like attribution sources, postback data sources are the sources from which you want to pass post-install event data to Unity. In the Postback Settings tab of the ByteBrew integration setup, you can choose from the following options:Postback option | Description | Notes |
|---|---|---|
| Send only this partner | Pass post-install event data from only Unity-attributed installs. | |
| Send from all Networks and Organics | Pass post-install event data from all installs, including data from unattributed and organic installs. | This option enables Unity's models to learn from your post-install events across all networks, which can help to improve campaign performance. |
| Send only from this Partner and Organics | Pass post-install event data from both Unity-attributed and organic installs. |