Conversion Tracking Guide

From Mojiva
Jump to: navigation, search

Contents

Brief Description

This document details multiple approaches to tracking user conversions. Mojiva can track application downloads or track conversion from a mobile website.

A conversion occurs when a publisher site visitor performs a desired reaction (i.e. an app download or a user signup for a product).

Application Download — Tracking

Mojiva has partnered with AD-X, an independent tracking partner; to perform conversion tracking on apps downloads without the need for any unique device information. Advertisers will have to incorporate the AD-X SDK (a one–time installation) into their App. The campaigns can run on other apps and/or mobile web and AD-X will be able to track downloads.

Using AD-X, these application downloads can be successfully recorded and counted, providing a very effective campaign performance metric.

Table 1: Parameters
Parameter Required? Description
%SID% Yes Show ID used to tie the impression to the conversion.
%DID% Yes Domain (site) ID where the ad impression occurred.

AD-X Click URL format:

   https://ad-x.co.uk/API/click/CAYMEN2011BEASLEY/4f2004711067c/NET/%SID%/Mojiva?subid=%DID%

AD-X does not require %CPID% because the %SID% impressions ID that Mojiva passes to AD-X is a unique ID generated for each campaign display. Mojiva receives a conversion from AD-X with the unique impression ID and then translates it back to a specific Campaign ID.

For more information on Ad-X please contact your Mojiva Sales Rep.

http://adxtracking.com/


The Mojiva 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.mojiva.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]. Using UDID for iOS is at the advertisers discretion.

For Android, use Android’s Device ID - getDeviceId()

udid=1bef50453858d317a8471087aaf1614a
advertiser_id yes Advertiser user id (provided by Mojiva 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

Example of request:

http://www.mojiva.com/appconversion.php?udid=1bef50453858d317a8471087aaf1614a&advertiser_id=1234&group_code=APP1

Successful XML Response format:

<?xml version="1.0" encoding="UTF-8"?>
<mojiva>
  <result>OK</result>
</mojiva>


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

 <?xml version="1.0" encoding="UTF-8"?>
 <mojiva>
   <result>ERROR</result>
 <errorcode>1</errorcode>
 </mojiva>

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

Mobile Web – Simple Option

When a site visitor clicks on an ad and goes to the Advertiser’s landing page or site, the ad server 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 Mojiva 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 Mobile Web Advanced Option 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.

Getting Conversion Code


<img src="http://www.mojiva.com/conversion.php" />


Mobile Web - Advanced Option

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 Unique ID of the ad. (This is not required for AD-X)
%DID% no Domain (site) ID where the ad impression occurred.


Using the Mojiva Solution

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

  • Mojiva Click URL format:

http://www.example.com/?sid=%SID%&cid=%CPID%

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:

<img src="http://www.mojiva.com/conversion.php?sid=%SID%&cid=%CPID%&did=%DID%"/>

Sample of the conversion code:

<img src="http://www.mojiva.com/conversion.php?sid=87bd3f60-9eff-11df-953d-0019b9f99000&cid=2266&did=5842" />

Mojiva 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:

<img src="http://www.mojiva.com/conversion.php?sid=%SID%&cid=%CPID%&did=%DID%&group_code=REGISTER" />

OR a HTTP request:

http://www.mojiva.com/conversion.php?sid=%SID%&cid=%CPID%&did=%DID%&group_code=REGISTER

Reporting

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

  • Date: the specific date/time of conversion;
  • Campaign ID: the creative/ad ID from the Mojiva 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;
  • IP: user device IP Address;
  • Country: user country (which the request has been received from).
  • Impression ID: unique identifier of the corresponding impression;

To access your conversion reports, follow these steps:

Step #1: Login to your Advertiser account/account.
Step #2: Go to ’Reports’, then select ’Conversions’.
Step #3: Specify the report type (hourly/daily/monthly) and the date range.
620px

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

620px

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

Personal tools
Namespaces

Variants
Actions
Navigation
Tools