MMP measurement URLs for app advertising

This document defines the requirements for HAQM-managed app advertisers to provide HAQM with proper measurement URLs.

Third party Mobile Measurement Platforms

HAQM Ads has integrated with several mobile measurement platforms (MMPs). This means app advertisers who have also integrated their app with one of these MMPs can surface install and in-app events from their managed Fire Tablet or Fire TV campaigns to HAQM. This event data can help HAQM account managers identify quality installs and apply optimization strategies that drive toward goals based on advertising cost-per-action (CPA) or return-on-investment (ROI).

HAQM has reserved some of the MMP data parameters to pass identifying information for devices, impressions, and ad campaigns. Advertisers need to follow the parameter specs below so that these identifiers can be transmitted to HAQM systems. The following table is a list of all currently certified MMPs and the supported locales by device type. Note that both event types install and in-app are supported only in the US locale; UK and DE locales only support install (not in-app) events.

What are the data pathways?

Impressions
As ads are served, HAQM embeds click measurement information in the creative and sends the impression notification to the MMP. View-through attribution (if desired) is managed directly by the advertiser in the MMP portal.

Clicks
When the user clicks on the ad, HAQM records the click and forwards the data to the MMP using the measurement URL.

Installs
When the user loads the app, the MMP SDK in the advertised app notifies the MMP. When the MMP determines an install is credited to HAQM, it can notify HAQM via postback (callback). HAQM requires advertisers to enable notifications to HAQM for HAQM-attributed installs and non-attributed installs to help optimize ad campaigns (portal settings vary per MMP).

In-app Events
If available and configured properly, when the user completes a desired action in an app, the MMP SDK in the app can report that to the MMP. The MMP can surface in-app events to HAQM via the MMP portal (features and settings vary per MMP). HAQM strongly encourages all notifications to help in ad optimization.

Policy and Instructions

Advertising clients working with HAQM Ads for Apps managed services can send event data to HAQM by enabling postbacks (callbacks) in the MMP portal. Of course this first requires proper integration of the MMP SDK in the advertised app. Failing to comply with the policy and instructions may disrupt data flowing to the MMP and/or to HAQM and may cause delays in campaign launch.
1. Create campaign, enable events
In the MMP campaign screen, create the campaign and enable event “postbacks” or “callbacks” to be sent to HAQM. HAQM requires advertisers to enable install postbacks which are required for install reporting to work. Enabling In-app event postbacks is optional; if enabled, in-app events flow through the MMP portal only (they do not flow through HAQM's internal campaign management system).

2. Get measurement URLs (trackers)
The MMP portal will generate measurement URLs with HAQM data macros embedded. Advertiser will need to ensure the MMP URLs are attributing on Fire Ad ID versus Android ID. Advertisers should provide these trackers to HAQM that comply with these parameter specs. Only one impression tracker and one click tracker is supported per title and platform. Advertisers can insert HAQM macros in any of the parameters available to them (i.e. parameters not reserved for HAQM use). An impression tracker can be used for view-through conversion measurement, but it is optional. Longer view-through attribution settings are recommended given that HAQM is the only vendor selling Fire TV and Fire Tablet inventory.
- Appsflyer and Branch offer a 7 day maximum window
- Kochava offers a 24 hour maximum window
- Adjust offers a configuarable view-through window

3. Resolve any parameter conflicts
HAQM uses some of the MMP parameters to pipe certain identifiers (details below). If there is an unavoidable parameter conflict, communicate that to the HAQM account contact. Using HAQM- reserved parameters will disrupt the data that HAQM campaign managers use to optimize performance.

4. Additional parameters
Advertisers can add optional MMP-expanded parameters (as well as their own parameters) to dynamically pull in certain campaign identifiers used for optimizing. Other than HAQM macros and MMP macro/placeholder expansion, there is no capability to support different measurement URLs per creative, ad line, or group of ad lines.

5. URL modification
HAQM will encode the advertiser-provided measurement URL when the ad is trafficked to preserve it as embedded payload within the ad creative. HAQM may also add data macros or modify other aspects of the URL to comply with the policy and instructions.

MMP Measurement URLs (trackers)

HAQM ad creatives support measurement URLs or “trackers.” On every advertising campaign, the advertiser provides HAQM with impression and click trackers: one of each per platform (Fire Tablet/Fire TV), although the impression tracker is optional. These trackers are generated in the MMP portal by the advertiser. There are cases where the advertiser wishes for more granular reporting (by creative or special segments, for example). Since a campaign can only support one impression and click tracker, advertisers can leverage HAQM's optional “macros” that dynamically pull in the appropriate campaign name, ad line, or creative size when the ad is rendered. HAQM supports the below macros for all MMPs. These macros are either automatically included in the MMP's URL template or can be added manually after the URL has been generated (optional). The optional macros vary by MMP and are outlined in the next section.

Advertisers should use HAQM's Tracker Builder tool to generate and validate new MMP trackers. This ensures the URL is setup to pass through HAQM's internal systems properly and will help prevent post-launch campaign issues. See http://s3.amazonaws.com/ksomedia/mmp-tracker/index.html.

Adjust Parameters

HAQM uses custom parameters with Adjust, so advertisers may use any of these params below. (See http://docs.adjust.com/en/tracker-generation/ and http://docs.adjust.com/en/special-partners/amazon/)

Adjust Example Measurement URLs

Impression: Fire

Click: Fire

AppsFlyer Parameters

HAQM reserves several AppsFlyer parameters. (See http://support.appsflyer.com/hc/en-us/articles/207447163-AppsFlyer-Tracking-Link-Structure-and-Parameters)

AppsFlyer Example Measurement URLs

Impression: Fire

Click: Fire

Kochava Parameters

The following Kochava parameters are reserved for HAQM use. (See http://support.kochava.com/reference-information/integrate-with-kochava-as-a-networkpublisher/)

Kochava Example Measurement URLs

Impression: Fire

Click: Fire

Singular Parameters

The following Singular parameters are reserved for HAQM use.

Singular Example Tracking URLs

Impression: Fire

Click: Fire

Tune Parameters

Tune provides a way to add customer parameters to the measurement URL in the “My Parameters” section. HAQM reserves the following “Partner Parameters”. (See http://help.tune.com/hasoffers/parameters-macros-in-hasoffers/).

Tune Example Tracking URLs

Impression: Fire

Click: Fire

Branch Parameters

The following Branch parameters are reserved for HAQM use. (See http://docs.branch.io/deep-linked-ads/amazon-mobile-tracking/).

Branch Example Measurement URLs

FIRE TV

Impression: Fire

Click: Fire

FIRE TABLET

Impression: Fire

Click: Fire

Note: For click url, the subdomain is dependent on the app. Hence it changes for every app. In the above case it’s branchsteramazon