Conversion Tracking Guide

From Mocean Mobile Wiki

Contents 1 Brief Description 2 Tracking Approach #1: Mocean Default Conversion Code 2.1 Limitations 2.2 Getting a Conversion Code 2.3 Using the AD-X Solution 3 Tracking Approach #2: User Defined Conversion Code 3.1 Customizing Conversions 4 Multiple-Trigger Conversion Tracking 5 Application Download — Tracking 6 Reporting

Brief Description

This document details several approaches to tracking user conversion using the Mocean Mobile platform, from how to properly install the default conversion code, to application download tracking and counting.

A conversion occurs when a publisher site visitor performs a desired reaction (i.e. a registration, a product purchase, or a viewing of specific information). Using the below methods, these actions can be recorded and counted, providing a very effective campaign performance metric.

Tracking Approach #1: Mocean Default Conversion Code

When a site visitor clicks on an ad and goes to the Advertiser’s landing page or site, the Mocean Mobile system logs a click and creates a cookie in order to track the conversion (campaign and click IDs are saved in cookies).

A pair of UA/IP and the last click parameters are saved in the hash where the UA/IP is a key and the last click is a value. On reaching the page with the conversion code installed, it sends the request to the Mocean server for a pixel image. The script on the server side processes the request comparing the UA/IP from the header of the conversion request with that stored in the hash and, if they are the same, registers the conversion, saving information about the conversion (campaign ID and click ID from cookies) to the database; it then returns a pixel image 1×1.

Limitations

In view of the fact that only the last click is stored in the hash, there is no opportunity to track conversion by several clicks. This means that a visitor can perform several transactions invoking the conversion tracking code each time, but only one conversion (the last) will be registered.

Moreover, there is also a time limit allowed from registering the click and visiting a page with the conversion tracking code installed. At the moment, this time limit is set to 10 minutes.

For multiple trigger conversion tracking, please refer to Tracking Approach #2 below.

Getting a Conversion Code

Copy the conversion code displayed at the bottom of the campaign ’Summary page’, and place it on the confirmation page on your landing site.

There are two ways to track conversion; through the Mocean interface or using the AD-X solution.

Using the AD-X Solution

Step #1: Add conversion parameters to your click URL.

AD-X Click URL format:

Append: /NET/%SID%/Mocean?subid=%DID% to all click URLs.

For example:

AD-X does not require %CID% because the %SID% impression ID that Mocean passes to AD-X is a unique ID generated for each campaign display. Mocean receives a conversion notification from AD-X with this unique impression ID and Mocean translates it back to the appropriate Campaign ID in your network.

Step #2: After click URLs are correctly setup [with Mocean’s macros and path], Advertisers will need to install the AD-X SDK.

Step #3: Configure Ad-X dashboard to enable Postbacks to Mocean. This way all the conversions will automatically show up within your Mocean network portal itself!

In the AD-X interface, go to start -> Campaign Setup -> Network Setup (see image below) then dragging the Network Icon back onto the app.

Tracking Approach #2: User Defined Conversion Code

Another way to track conversions is to include click and campaign IDs in a campaign’s Click URL. In this case, you must pass these parameters via click URL when a user requests your page and store them within the user’s session.

This approach enables multi-trigger conversion tracking (i.e. registering a conversion each time it occurs as opposed to just registering by last click).

The list of useable parameters for tracking conversions is given below:

Table 1: Parameters

Parameter	Required?	Description
%SID%	yes	Show ID used to tie the impression to the conversion.
%CPID%	yes	Campaign ID corresponding to the ad shown
%DID%	no	ID of a web page where the conversion registered

Customizing Conversions

Step #1: Add conversion parameters to your click URL.

Click URL format:

Step #2: Save parameters within a session. You can omit site ID (%DID%) if desired, but make sure that impression ID (%SID%) and campaign ID (%CPID%) are stored.

Step #3: Format your conversion code according to the following example. BE SURE TO exclude symbols ’'%'’ setting off parameters from the request (see sample below).

Conversion code format:

Sample of the conversion code:

Multiple-Trigger Conversion Tracking

Mocean Mobile conversion tracking allows for the tracking of multiple conversions. As an example, you may track users that have registered for an account on the site (as a qualified lead/conversion) AND also track the number of users that paid for a product (as a 2nd conversion).

For this purpose, an additional GET parameter called group_code can be passed in with the conversion code.

Table 2: Conversion Parameters. Continuation

Parameter	Required?	Description	Example
group_code	no	[1-20] letters/digits (all letters will be converted to upper case).	group_code = REGISTER group_code = SALE

Conversion code format:

OR a HTTP request:

Application Download — Tracking

The Mocean Mobile platform allows advertisers to track the number of application downloads on a per campaign basis, providing for an effective campaign performance metric.

After an application is downloaded and launched, a ping URL is sent to the URL http://www.moceanmobile.com/appconversion.php .

Parameter	Required?	Description	Example
udid	yes*	FOR APPS ONLY! MD5 HASHED UDID (Unique Device ID) is required regardless of method used to integrate advertising into the apps. For iOS - it is the device ID (apple’s UDID) – use [[UIDevice currentDevice] uniqueIdentifier]. For Android, use Android’s Device ID - getDeviceId(). If you use our SDKs, this is already done. You must send the properly hashed UDID for conversion tracking to work.	udid=1bef50453858d317a8471087aaf1614a
advertiser_id	yes	Advertiser user id (provided by Mocean Mobile team).	advertiser_id=1234
group_code	no	[1-20] letters/digits (all letter will be converted to upper case). Can be used to pass in any identification info (like application name, version).	group_code=APP1

* You must send the properly hashed UDID for conversion tracking to work.

Example of request:

Successful XML Response format:

If any error occurred during the conversion input, XML response will be as follows:

The above XML node ’errorcode’ can be any number between 1 through 99.

Reporting

Conversion reports are available in your network. Reports are aggregated daily (every 24 hours). The following are captured within the reports:

• Date: the specific date/time of UDID (hashed) download transaction;
• Campaign ID: the creative/ad ID from the Mocean Mobile system;
• Campaign Name: the name of the ad;
• Zone ID: the ID of the zone that delivered the conversion;
• Click ID: unique identifier of the click;
• Impression ID: unique identifier of the corresponding impression;
• IP: user device IP Address;
• Country: user country (which the request has been received from).

To access your conversion reports, follow these steps:

Step #1: Login to your network/account.

Step #2: Go to ’Reports’, then select ’Conversions’.

Step #3: Specify the report type (hourly/daily/monthly) and the date range.

You can also download this report in CSV format by clicking on the ’Export to CSV’ link.

In the case of CSV output, you can get the complete information that also includes some additional parameters like country region, group code, phone brand, phone model and Advertiser ID