Set up Vybs
Vybs is an ad network integrated with Adjust. Our integration lets Vybs receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with Vybs for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Vybs.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Vybs parameters. Follow the guides linked below to use this feature.
iOS | Android | Windows | Unity | React Native | Flutter | Adobe Air | Cordova | Marmalade | Xamarin | Cocos2d-x | Titanium | Corona
Select Vybs and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Vybs. Select Next to move to the next screen.
- In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Vybs.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Vybs. To enable data sharing:
- Turn on Enabled
Once you enable data sharing with Vybs, Adjust automatically sends Vybs the following data, by default:
- install
- session
- reattribution
- event
- rejectedInstall
- rejectedReattribution
- ad revenue
Set your data sharing options
If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:
- Separate data sharing options at the platform-level by selecting Use platform-specific settings.
- Set the same data sharing settings for multiple platforms by selecting Use global settings.
Now, under What will be shared by default?, review the activities that Adjust shares with Vybs by default.
- install
- session
- reattribution
- event
- rejectedInstall
- rejectedReattribution
- ad revenue
Send additional data
Choose the amount and type of data that you want to share with Vybs through callbacks. Vybs may use this information to optimize performance.
- Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Vybs:
- Data from all attribution sources
- Only data attributed to Vybs
Ad revenue (from ad views)
Ad revenue sharing lets Vybs receive user ad revenue data. This lets Vybs use ad revenue data to optimize your user targeting and campaigns.
This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.
To share ad revenue to Vybs, select one or more Ad Revenue Sources.
- If you leave this field empty, we send ad revenue data from all integrated mediation sources.
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means Vybs will receive your app’s session activity.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets Vybs receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Map events
Map events that you want to share to the values that Vybs can receive. Data for unmapped events is not shared with Vybs.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with Vybs. This lets you:
- Set individual events to manage campaign strategies for each platform.
- Customize data sharing per platform.
Under Map events, follow these steps to choose the in-app events you want to directly send to Vybs.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with Vybs.
- Under Partner event, you need to select the Vybs event that corresponds to the Adjust event.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
- Select Use global mapping to map the same events for all platforms.
- In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Apply.
Now Vybs will receive in-app event data for each of your linked events.
Map all events
If Vybs supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now Vybs will receive in-app event data for all your linked events.
Configure your link and settings
You have the option to set your:
Create your link and share it with Vybs
In the Setup review screen, you can review your choices. You can also go back and make changes to:
- Your selected app
- Data sharing options
- Link structure parameters
- User destinations
- Attribution settings
Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with Vybs.
Once you’ve created your link, share it with Vybs for placement in campaigns.
List of all parameters forwarded to Vybs
Vybs requires Adjust to send the following parameters (data points) with your callbacks:
Placeholder | Information |
{country} | Device two-character country code |
{gps_adid} | Google Play Store advertising ID |
{lifetime_session_count} | Number of sessions recorded across entire user lifetime |
{revenue_usd} | Revenue, in US dollars |
{session_count} | Number of sessions recorded by current Adjust SDK |
{app_name} | Name of the app |
{campaign_name} | Campaign name, as taken from the tracker |
{created_at} | Activity timestamp |
{creative_name} | Creative name, as taken from the tracker |
{installed_at} | Install (i.e., first app open) timestamp |
{last_session_time} | Last session timestamp |
{reattributed_at_hour} | Reattribution timestamp, rounded to the nearest hour |
{reattributed_at} | Reattribution timestamp |
{rejection_reason} | Reason for a rejected attribution |