Set up Bidease
Bidease is an ad network integrated with Adjust. Our integration lets Bidease receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with Bidease for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Bidease.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Bidease 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 Bidease and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Bidease. 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 Bidease.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Bidease. To enable data sharing:
- Turn on Enabled
Once you enable data sharing with Bidease, Adjust automatically sends Bidease the following data, by default:
- install
- reattribution
- event
- rejectedInstall
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 Bidease by default.
- install
- reattribution
- event
- rejectedInstall
Send additional data
Choose the amount and type of data that you want to share with Bidease through callbacks. Bidease may use this information to optimize performance.
Ad spend
Ad spend sharing lets Bidease receive user ad spend data. This lets Bidease use ad spend data to optimize your campaigns.
Adjust sends Bidease the ad spend data received through callbacks only. This data comes from the following solutions that you’ve set up, as applicable for Bidease:
If Bidease wants complete ad spend data, then you can set up Ad spend third-party storage exports for Bidease.
This feature is available with Adjust’s SpendWorks package. To purchase our SpendWorks package, contact your sales representative.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets Bidease 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 Bidease can receive. Data for unmapped events is not shared with Bidease.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with Bidease. 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 Bidease.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with Bidease.
- Under Partner event, you need to select the Bidease 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 Bidease will receive in-app event data for each of your linked events.
Map all events
If Bidease supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now Bidease 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 Bidease
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 Bidease.
Once you’ve created your link, share it with Bidease for placement in campaigns.
List of all parameters forwarded to Bidease
Bidease requires Adjust to send the following parameters (data points) with your callbacks:
| Placeholder | Information |
{adid} | Adjust device ID (all platforms) |
{android_id_md5} | Lowercase Android ID hex MD5 hash |
{city} | Device city |
{click_attribution_window} | Attribution window settings for device matching (hours) |
{cost_amount} | Cost of the user engagement (available for ad spend tracking only) |
{cost_currency} | ISO 4217 currency code of the cost data (available for ad spend tracking only) |
{cost_type} | The campaign pricing model (available for ad spend tracking only) |
{country_subdivision} | Device subdivision of country, e.g., state |
{country} | Device two-character country code |
{device_name} | Device model number |
{device_type} | Device type |
{idfa||gps_adid} | IDFA, or GPS ADID if IDFA is empty |
{idfv} | Uppercase iOS ID for vendors |
{impression_attribution_window} | Attribution window settings for impression matching (hours) |
{ip_address} | Device IP address |
{is_reattributed} | 1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed |
{isp} | Device internet service provider |
{language} | Device two-character language code |
{mac_md5} | Uppercase MAC MD5 hash |
{match_type} | Attribution method |
{mcc} | Mobile country code: three-digit code identifying a device's country. Use with the mobile network code to identify a device's carrier. |
{mnc} | Mobile network code: two-digit code. Use with the mobile country code to identify a device's carrier. |
{os_name} | Device operating system |
{os_version} | Operating system version number |
{partner_parameters} | Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks |
{reattribution_attribution_window} | Attribution window settings for reattribution (hours) |
{region} | Device region code |
{reporting_cost} | Cost of the user engagement converted to your app's reporting currency and as reported in the Adjust Dashboard (available for ad spend tracking only) |
{reporting_currency} | Dashboard reporting ISO 4217 currency code |
{reporting_revenue} | Revenue, as reported in the Adjust Dashboard, in whole currency units |
{revenue_usd} | Revenue, in US dollars |
{session_count} | Number of sessions recorded by current Adjust SDK |
{time_spent} | Length of user's current session, in seconds |
{user_agent} | Incoming raw user agent |
{activity_kind} | Type of user activity |
{adgroup_name} | Adgroup name, as taken from the tracker |
{app_id} | Store App ID or Google Play Store |
{app_name} | Name of the app |
{campaign_name} | Campaign name, as taken from the tracker |
{connection_type} | Internet connection type |
{created_at} | Activity timestamp |
{creative_name} | Creative name, as taken from the tracker |
{engagement_time} | Engagement timestamp |
{impression_based} | 1 if impression-based engagement, 0 if not |
{installed_at} | Install (i.e., first app open) timestamp |
{is_organic} | 1 if organic traffic, 0 if non-organic |
{reattributed_at} | Reattribution timestamp |
{rejection_reason} | Reason for a rejected attribution |
{tracker_name} | Current tracker name |