Languages 

Set up Bidease

Bidease is a network and Adjust module partner. Our integration lets Bidease receive attribution and in-app event data through automated callbacks.

Use our basic setup instructions to turn on Adjust’s integration and send callbacks to Bidease. Then, use our advanced setup instructions to customize what information Bidease receives.

Basic setup

To turn on Adjust’s integration with Bidease, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select the add (+) icon next to Bidease
  4. Turn on Enabled
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. Now you can create an Adjust tracker URL and submit it to Bidease to launch your campaign.

Bidease will receive callbacks for these activities:

  • install
  • reattribution
  • event
  • rejectedInstall

Advanced setup

Choose which data Bidease receives from Adjust by customizing your setup.

Forward in-app revenue

In-app revenue forwarding lets Bidease receive revenue amounts along with your revenue event data.

To forward in-app revenue to Bidease, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Bidease
  3. Turn on In-App Revenue Forwarding

Now Bidease will receive the revenue amount for every tracked transaction.

Note: Link at least one [revenue event] to Bidease before turning on In-App Revenue Forwarding.

Forward in-app events

Event linking lets Bidease receive in-app event data. You can link every in-app event in Adjust to a preset Bidease name or a custom event name.

To forward in-app events to Bidease, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Bidease > Event Linking
  3. Find the event you want to link and update the field with a Bidease event or your own custom name
  4. When you finish linking events, select OK
  5. Select Save

Now Bidease will receive in-app event data for each of your linked events.

List of all parameters forwarded to Bidease

Bidease requires Adjust to send the following parameters (data points) with your callbacks:

PlaceholderInformation
{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
{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
{match_type}Attribution method
{os_name}Device operating system
{os_version}Operating system version number
{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
{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