Set up Miniclip Ad Network

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

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

Before you begin

Requirements

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

Select Miniclip Ad Network and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > Miniclip Ad Network. 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 Miniclip Ad Network.
  4. Select Next.

Enable data sharing

Enable data sharing to activate the integration with Miniclip Ad Network. To enable data sharing:

  1. Turn on Enabled

Once you enable data sharing with Miniclip Ad Network, Adjust automatically sends Miniclip Ad Network 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:

  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 Miniclip Ad Network 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 Miniclip Ad Network through callbacks. Miniclip Ad Network may use this information to optimize performance.

Ad revenue (from ad views)

Ad revenue sharing lets Miniclip Ad Network receive user ad revenue data. This lets Miniclip Ad Network 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 Miniclip Ad Network, 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 Miniclip Ad Network will receive your app’s session activity.

In-app revenue (from in-app purchases)

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

Map individual events

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

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Miniclip Ad Network.
  3. Under Partner event, you need to select the Miniclip Ad Network 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 Miniclip Ad Network will receive in-app event data for each of your linked events.

Map all events

If Miniclip Ad Network supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.

Now Miniclip Ad Network will receive in-app event data for all your linked events.

Map parameters

You usually need to map parameters to share custom data with Miniclip Ad Network.

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Miniclip Ad Network. This lets Miniclip Ad Network 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 Miniclip Ad Network, 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 Miniclip Ad Network

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 Miniclip Ad Network.

Once you’ve created your link, share it with Miniclip Ad Network for placement in campaigns.

List of all parameters forwarded to Miniclip Ad Network

Miniclip Ad Network 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_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}Event token
{fire_adid}Fire OS advertising identifier
{gps_adid_md5}Lowercase hex MD5 hash of Google Play Store advertising ID
{gps_adid}Google Play Store advertising ID
{idfa_md5_hex}IDFA hex MD5 hash
{idfa_md5}IDFA base64 MD5 hash
{idfa_upper}Uppercase IDFA
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{impression_attribution_window}Attribution window settings for impression matching (hours)
{inactive_user_definition}Inactivity period required for reattribution (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
{label}Value of the Adjust "label" parameter sent on click
{language}Device two-character language code
{lifetime_session_count}Number of sessions recorded across entire user lifetime
{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.
{nonce}Random lowercase alphanumeric string (unique per callback)
{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
{random_user_id}Random user ID (per device)
{random}Random number (unique per callback)
{reattribution_attribution_window}Attribution window settings for reattribution (hours)
{reftag}Random device reference tag
{region}Device region code
{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
{sdk_version}Adjust SDK version (per app)
{session_count}Number of sessions recorded by current Adjust SDK
{timezone}Device time zone
{tracking_enabled}1 if tracking is enabled, 0 if not
{tracking_limited}1 if tracking is limited, 0 if not
{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
{app_version_raw}App version number (Android), build-version-number for the bundle (iOS)
{app_version_short}App version number (Android), release-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_hour}Attributed click timestamp, rounded to the nearest hour
{click_time}Attributed click timestamp
{connection_type}Internet connection type
{conversion_duration}Time between click and install or reattribution in seconds
{cpu_type}CPU type
{created_at_hour}Activity timestamp, rounded down to the nearest hour
{created_at_milli}Activity timestamp with millisecond placeholders
{created_at}Activity timestamp
{creative_name}Creative name, as taken from the tracker
{device_manufacturer}Device manufacturer name
{engagement_time_hour}Engagement timestamp rounded to the nearest hour
{engagement_time}Engagement timestamp
{first_tracker_name}Name of a user's first attribution source
{hardware_name}Hardware name
{impression_based}1 if impression-based engagement, 0 if not
{impression_time_hour}Attributed impression timestamp, rounded to the nearest hour
{impression_time}Attributed impression timestamp
{install_finish_time}App download completion timestamp
{installed_at_hour}Install (i.e., first app open) timestamp rounded to the nearest hour
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{network_name}Network name, as taken from the tracker
{reattributed_at}Reattribution timestamp
{referral_time}User landed on app Play Store page timestamp (Android and Google Play Store only)
{reinstalled_at}Reinstall timestamp
{rejection_reason}Reason for a rejected attribution
{store}Target store of click
{tracker_name}Current tracker name
{ad_impressions_count}Number of mobile ads served to end users
{ad_revenue_network}Ad network that displayed the ad
{ad_revenue_unit}Ad unit that generated the revenue
{ad_revenue_placement}User placement, as defined on the platform
{oaid_md5}OAID MD5 hash
{oaid}OAID device ID
{is_s2s_engagement_based}1 if attributed to a server to server engagement, 0 if not
{proxy_ip_address}IP address of user's proxy
{ad_mediation_platform}Mediation platform name
{third_party_tracking_disabled}1 if third party sharing is disabled, 0 if not