Set up Opera Ads

Opera Ads is an ad network integrated with Adjust. Our integration lets Opera Ads receive attribution and in-app event data through automated callbacks.

In this article, learn how to set up measurement with Opera Ads for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Opera Ads.

Before you begin

Requirements

iOS | Android | Windows | Unity | React Native | Flutter | Adobe Air | Cordova | Marmalade | Xamarin | Cocos2d-x | Titanium | Corona

Select Opera Ads and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > Opera Ads. Select Next to move to the next screen.
  3. In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Opera Ads.
  4. Select Next.

Enable data sharing

Enable data sharing to activate the integration with Opera Ads. To enable data sharing:

  1. Turn on Enabled

Once you enable data sharing with Opera Ads, Adjust automatically sends Opera Ads the following data, by default:

  • install
  • session
  • uninstall
  • reinstall
  • 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:

  1. Separate data sharing options at the platform-level by selecting Use platform-specific settings.
  2. 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 Opera Ads by default.

  • install
  • session
  • uninstall
  • reinstall
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution
  • ad revenue

Send additional data

Choose the amount and type of data that you want to share with Opera Ads through callbacks. Opera Ads may use this information to optimize performance.

  1. Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Opera Ads:
  • Data from all attribution sources
  • Only data attributed to Opera Ads

Ad revenue (from ad views)

Ad revenue sharing lets Opera Ads receive user ad revenue data. This lets Opera Ads use ad revenue data to optimize your user targeting and campaigns.

Growth solution:

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 Opera Ads, 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 Opera Ads will receive your app’s session activity.

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets Opera Ads receive your app’s uninstall and/or reinstall data measured by Adjust.

Note:

For iOS apps, you might expect a low record of uninstalls and/or reinstalls. For more information, visit Uninstall and reinstall measurement.

In-app revenue (from in-app purchases)

Sharing in-app revenue lets Opera Ads 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 Opera Ads can receive. Data for unmapped events is not shared with Opera Ads.

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with Opera Ads. 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 Opera Ads.

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Opera Ads.
  3. Under Partner event, you need to select the Opera Ads event that corresponds to the Adjust event.
    1. 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.
    2. In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
  4. Select Apply.

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

Map all events

If Opera Ads supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.

Now Opera Ads will receive in-app event data for all your linked events.

Map subscription events

Map subscription events that you want to share to the values that your network can receive. Data for unmapped events is not shared with your network.

If you have a multi-platform app, you can choose to share different events per platform with your network. This lets you:

  • Set individual events to manage campaign strategies for each platform.
  • Customize data sharing per platform.

Under Map subscription events, follow these steps to choose the subscription events you want to directly send to your network.

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with your network.
  3. Under Partner event, you need to select the partner event that corresponds to the Adjust event.
    1. 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.
    2. In the Partner event list, choose or enter a custom event name that you want to map the Adjust event to.
  4. Select Apply.

Now your network will receive subscription event data for each of your linked events.

Subscription events - No revenue

Subscription events - Positive revenue

Map parameters

You usually need to map parameters to share custom data with Opera Ads.

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Opera Ads. This lets Opera Ads receive custom event details for each of your linked events.

Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.

To share partner parameters to Opera Ads, follow these steps.

  1. Set up partner parameters within the Adjust SDK.
  2. Under Set your data sharing options, select Parameters.
  3. Under Map parameters, you can specify how you want to send partner parameters defined in the SDK to the network:
    1. Select Map parameter.
    2. In the SDK parameter field, enter the name of the SDK parameter you want to share with the network.
    3. In the Partner parameter field, enter the network parameter that corresponds to the SDK parameter.
Note:

If you set up partner parameters within the Adjust SDK without setting up parameter sharing in the dashboard, Adjust forwards the parameters as named in the Adjust SDK.

Configure your link and settings

You have the option to set your:

Create your link and share it with Opera Ads

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 Opera Ads.

Once you’ve created your link, share it with Opera Ads for placement in campaigns.

List of all parameters forwarded to Opera Ads

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

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{android_id_md5}Lowercase Android ID hex MD5 hash
{android_id}Android ID (Android only)
{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_id_md5}An MD5 hash of the cost ID provided by a network using our ad spend API (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
{deeplink}Deeplink URL appended to click URL
{device_name}Device model number
{device_type}Device type
{environment}Current Adjust SDK environment setting
{event_name}Event name, as set in the Dashboard
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{impression_attribution_window}Attribution window settings for impression matching (hours)
{ip_address}Device IP address
{isp}Device internet service provider
{language}Device two-character language code
{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
{postal_code}Device postal code of IP address
{revenue_usd_cents}Revenue, in US cents
{revenue_usd}Revenue, in US dollars
{timezone}Device time zone
{user_agent}Incoming raw user agent
{activity_kind}Type of user activity
{app_id}Store App ID or Google Play Store
{app_name}Name of the app
{app_version_raw}App version number (Android), build-version-number for the bundle (iOS)
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{campaign_name}Campaign name, as taken from the tracker
{click_time}Attributed click timestamp
{conversion_duration}Time between click and install or reattribution in seconds
{created_at}Activity timestamp
{device_manufacturer}Device manufacturer name
{engagement_time}Engagement timestamp
{impression_based}1 if impression-based engagement, 0 if not
{impression_time}Attributed impression timestamp
{install_begin_time}App download began timestamp (Android and Google Play Store only)
{install_finish_time}App download completion timestamp
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{rejection_reason}Reason for a rejected attribution
{oaid}OAID device ID
{is_s2s}1 if server to server engagement, 0 if not
{proxy_ip_address}IP address of user's proxy
{att_status}App Tracking Transparency Status. Possible values are 0 (Not determined), 1 (Restricted), 2 (Denied), 3 (Authorized), unknown
{device_model}Device model number
{engaged_ad_based}1 if attributed to an engaged ad
{is_google_play_store_downloaded}Indicating if an app downloaded from Google Play Store or not
{platform}Indicates if the activity happened on mobile or web
{system_boot_time}System boot time for iOS devices