711121 - [EC1] Firefox Aurora Campaign Tracking

Status: RESOLVED WONTFIX

(www.mozilla.org :: General, defect)

Description

[Grace Jimenez :grace]

Hi Steven, 

We will be running display banner ads tentatively scheduled for 12/19.
In order to track the campaign we need to copy the mozilla.org/firefox/aurora page to another URL and implement ROI tags in the new unique Firefox Aurora URL just for this campaign (in addition to the webtrends tags)

* Tag one is to be placed in the "download" button on the Aurora US page. 
* Tag two should be placed in the first screen that spawns post downloading the browser. 

Laura, since this is a separate page to the current aurora page, can we make sure that webtrends tracking is implemented and set up? 

I know this is a very last minute request, do you think it would be possible to have it up to test by tomorrow? thanks!

thanks

Comment 1

[Grace Jimenez :grace]

Here is what EC1 provided: 


Below Here are your tags:
 
To put it the Download ROI tag on the download button, they can write their own java script to have the tag fire on click.  If they need an example of some code that will work, below is an example:
 
function doaction(f) { 
var mpck = "http://altfarm.mediaplex.com/ad/bk/17112-142712-3840-0?Download=1&mpuid=
&mpre="; 
parent.location=mpck; 
return false; 
} 

Which is called from the FORM action: 

<FORM action="_____" onSubmit="return doaction(this);">
 
The MPRE field is our redirect so they can put whatever the next page’s URL is there. 
 
 
 
________________________
 
ROI Tag Implementation Instructions for Mozilla/Firefox by Engine Company 1
 
 
Overview:
 
Mediaplex's MOJO Adserver Reports are specifically designed to provide Advertisers with the information needed to track and analyze the results of their specific campaign. Mediaplex provides the capability for Advertisers to collect the information that is most relevant to their campaign goals. Return on Investment (ROI) provides a key element in this process by tracking specifically desired data.
 
Mediaplex distinguishes between successful conversions that come from Mediaplex-served banners and those coming from other sources by correlating the backend requests (ROI tags) with the banner and click thru requests, using the Cookie ID, which is placed on the consumer's computer upon viewing a banner. The banner request is a 49-byte 1-pixel transparent gif file.
 
Mozilla/Firefox has identified an interest in tracking order and registration information. Specifically, Mozilla/Firefox is interested in the following information:
 
 
Basic Tracking Information:
 
1. The number of banners served ("Impressions") 2. The number of times that a potential customer clicks through the banner ("Clicks")
 
Custom ROI Tracking Information:
 
3. The number of ROI tag hits correlated with the above metrics ("Conversions")
 
 
Reporting:
 
Mediaplex will provide online reports in a delimited format that look similar to the following:
 
Impressions | Clicks | Click Rate (%) | Cost | CPC | Download, Welcome
 
This will provide Mozilla/Firefox and Engine Company 1 the information needed for analysis and fine-tuning the campaign towards the target audiences.
 
 
Required Tags to be Implemented:
 
Following is an example and explanation of an ROI tag that needs to be implemented on Mozilla/Firefox's site.  The specific ROI tags that should be implemented on the site are provided at the end of these instructions.  Please note that "https://" is used for secure pages:
 
 
<img src="http://adfarm.mediaplex.com/ad/bk/[Placement ID]?[ROI Name]=1&amp;mpuid=XXXXX" height="1" width="1" alt="Mediaplex_tag" />
 
 
Variables:
 
"mpuid":
XXXXX after "mpuid" is a unique alphanumeric value which can be dynamically inserted into the ROI tag for every ROI conversion.
 
The following are good examples of "mpuid" values:
 
1. Order ID for an order thankyou page
2. Anonymous Internal User ID for a registration thankyou page 3. Session ID for milestone pages such as shopping cart, registration fill-out form pages
 
Personally identifiable information, such as email address, should NOT be used as an "mpuid" value.
 
The illegal characters for "mpuid" are the = sign, the & sign, the ?, and either type of quotation marks (single or double). The semicolon is a good choice for a field delimiter if including multiple parameters. Mediaplex encourages the use of all parameters that might help the client later analyze the transaction.
 
Alternatively, if an appropriate mpuid value is not available, this value can be left blank and Mediaplex will automatically use a unique value contained in the browser cookie to identify the ROI event. Please note that, in this case, only one conversion per web browser will be counted within a particular duplicate checking period for a given ROI name and value. The duplicate checking period (or "de-dup period") is a window of time in which prior ROI events are scanned to see if the new event is a duplicate. The default duplicate checking period is 30 minutes, although it can be reconfigured, upon request, for a period of time up to 30 days. Please contact your account manager if this option is of interest.
 
Finally, you could pass any of the following values below for the "mpuid":
 
***Please note that this is not the recommended method for configuring an ROI tag as using the following values would result in possible multiple counting of the same ROI conversion when the users are able to reload the page and when a new value is generated. If a recommended value for "mpuid" is not available, Mediaplex recommends leaving the value blank, as described above.
 
1. random number
2. time stamp including the millisecond
3. combination of the above
 
The "mpuid" value needs be unique per ROI conversion and NOT per page load. If it is unique per page load, i.e., when the consumer refreshes the screen or clicks on the back and forward buttons, then MULTIPLE counts could be reported for the same conversion.
 
If possible, please make the entire ROI tag disappear when the user refreshes the page to completely avoid any possibility of multiple counting.
 
The "mpuid" value can be also used for post processing and statistical analysis. For example, Mediaplex could send you a list of Order IDs that came from a banner. Please inquire with the Mediaplex Account Manager for more details on MOJO Data Feed.
 
 
ROI Tag Name-Value Pair:
 
When constructing the ROI Name-Value pair part of the tag, you have two options:
 
Option 1:
[ROI Name]=1 Client needs to generate this ROI tag for every valid ROI conversion. The 1, which should not change (a hard -coded value), will be incremented in Mediaplex DB for every ROI conversion that results from a view through or click through on a particular site / banner combination.
 
Option 2:
[ROI Name]=[variable] Client needs to generate this ROI tag for every valid ROI conversion. The numeric [variable], which you will need to dynamically pass for every valid ROI conversion, will be incremented in Mediaplex DB for every ROI conversion that results from a view through or click through on a particular site / banner combination. The numeric variable may include decimal places, so it can represent dollar values. For example, "dollars=54.01", might represent a total sales amount on an order page.
 
[ROI Name] represents the ROI Names configured in the MOJO interface for each associated ROI Page.
 
 
Placement ID:
 
[Placement ID] is the Mediaplex placement id specific to EACH ROI tag.
 
 
Notes:
* Impressions- No customization needs to be performed on Mozilla/Firefox's website.
 
** Put the ROI tags AT THE HIGHEST POSSIBLE LOCATION on the page; ideally, immediately after the "BODY" tag.
 
 
------------------------------------
ROI Tags: Please use these URLs
------------------------------------
 
The following statements must be generated at the TOP of the ROI pages on Mozilla/Firefox's website:
 
************************************************************
ROI tag for Download
************************************************************
 
The following statement must be generated at the TOP of Mozilla/Firefox's Donwload page (http://www.mozilla.org/en-US/firefox/aurora/); ideally immediately after the "BODY" tag:
 
 
<img src="http://altfarm.mediaplex.com/ad/bk/17112-142712-3840-0?Download=1&amp;mpuid=" height="1" width="1" alt="Mediaplex_tag" />
 
 
Click on the following link to activate the ROI tag once it has been generated at the top of the Donwload page:
 
http://app.mediaplex.com/adserver/bl_roi.activate?client_id_in=17112&roi_log_id_in=44350&roi_page_id_in=50254
 
 
 
************************************************************
ROI tag for Welcome
************************************************************
 
The following statement must be generated at the TOP of Mozilla/Firefox's Welcome page (http://www.mozilla.org/); ideally immediately after the "BODY" tag:
 
 
<iframe src="http://img-cdn.mediaplex.com/0/17112/universal.html?page_name=welcome&Welcome=1&mpuid=" HEIGHT=1 WIDTH=1 FRAMEBORDER=0></iframe>
 
 
Click on the following link to activate the ROI tag once it has been generated at the top of the Welcome page:
 
http://app.mediaplex.com/adserver/bl_roi.activate?client_id_in=17112&roi_log_id_in=44350&roi_page_id_in=50255

Comment 2

[Grace Jimenez :grace]

hi steven, 

no need to implement the ROI tag from valueclick. 

We still need to create the page and implement webtrends tags. 
but both will have to be unique URL and reporting specific to this campaign.

Laura, can you help us set up a special reporting for this campaign?

Thanks!