Nielsen Hybrid TAM Implementation Guide

hushedsnailInternet and Web Development

Nov 12, 2013 (3 years and 5 months ago)

79 views





Nielsen
Hybrid
TAM
Implementation Guide


Release
0.1




Version
0
.
2







CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
2

of
31

May 2010

Revision History


Date

Version

Description

Author

April 28
th
, 2010

0.1

Creation

Mauro
Clerici

June 11, 2010

1

Draft Release

Mauro Clerici







Distribution List


Position

Name

Department

Sr TAM, USA

Mauro Clerici

Product leadership

VP Census Operations

Colin Brown

Product leadership

TAM, USA

Adam Mansfield

Product leadership

TAM,
USA

Josh Pineda

Product leadership

VP media Solutions

Shiven Ramji

Product leadership

Hybrid PM

John Brauer

Product leadership

EMEA PM

Manuel Montanari

Sales

APAC PM

Harley Hochstetler

Operations

Emerging Markets PM

Diego Semprun

Sales



Sponsor
Approval


Name

Position

Department











CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
3

of
31

May 2010

Table of Contents


Contents

Hybrid implementation workflow

................................
................................
................................
.........................

4

Tagging Implementation Overview

................................
................................
................................
......................

5

1.1

Basic Overview

................................
................................
................................
................................
..........

5

1.2

Nielse
n Tagging Implementation Package

................................
................................
................................

5

1.3

Pre
-
existing SC/MI Clients

................................
................................
................................
.........................

6

1.4

New Clients

................................
................................
................................
................................
...............

6

1.5

Code Versions (Hybrid
-
centric & New Clients)

................................
................................
..........................

7

1.5.1

JavaScript (Compact) Version
................................
................................
................................
............

7

1.5.2

JavaScript
-
less (Image Only) Version

................................
................................
................................

8

1.6

NetView Dictionary

................................
................................
................................
................................
....

8

1.7

Hybrid client ID Generation Process

................................
................................
................................
.........

8

1.8

SC Account Creation

................................
................................
................................
...............................

14

1.9

Hybrid Client Online Database

................................
................................
................................
................

15

DATA QA & Audit Process

................................
................................
................................
................................
..

16

QA client
internal

number with Nielsen overview

................................
................................
...............................

17

Observe Point

................................
................................
................................
................................
.....................

17

1.1 Tagging Au
dit

................................
................................
................................
................................
...............

17

Editing an Audit

................................
................................
................................
................................
..................

18

Starting an Audit

................................
................................
................................
................................
.................

19

4. Schedule

................................
................................
................................
................................
.........................

20

A NOTE ON AUDIT
RUNNING TIMES

................................
................................
................................
..............

22

Reading the Audit Results

................................
................................
................................
................................
..

23

1.2

Firefox browser’s plug
-
in

................................
................................
................................
.........................

24

1.3

URL Monitoring

................................
................................
................................
................................
........

25

1.3.1

Setting up an alert

................................
................................
................................
............................

25

1.
3.2

Recording a path beyond password
-
protected pages

................................
................................
.....

29

1.4

ABCi auditing process [optional]
................................
................................
................................
..............

29

TAM Tagging FAQ [please do NOT distribute to client
-

contains confidential details]

..............................

30

Appendix1


TAM responsibilities

................................
................................
................................
.....................

30

Appendix 2
-

Recommendations for
update to existing VCID tag generator (in progress)

.........................

30

Appendix 3


Regional Notes

................................
................................
................................
.............................

31

Appendix 3


Tagging Audit expected running times

................................
................................
......................

31




CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
4

of
31

May 2010



Hybrid
implementation workflow





Notes

The procedure below might change a bit in coming weeks/months, due to the release of some custom built hybrid tools such as:




Hybrid ID Generator (via VCID Tool);

Values generated will unique and independent from the VCI
D values and will be ending with the letter ‘h’, identifying an Hybrid ID.
Example: us
-
123456h
. For now the process of adding the ‘h’ is manual.

Approx arrival date: end of summer



Hybrid QA tool

This will eliminate the need to create a SC to monitor
client’s traffic

Approx arrival date: TBA


Below find a general Hybrid implementation walk
-
through. For each step listed, you will wind a respective section
describing more in
-
depth details.





CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
5

of
31

May 2010

Netview/SC Addendum is signed and delivered to Sales/TAM

Sales

Nielsen Digital Rating Tagging pre
-
Screener is filled out and delivered to Sales/TAM

Client/Sales

[recommended
]

Technical kick
-
off call with client to gather implementation
-
critical details

TAM

Client ID is created [new clients], proper code is
generated



new record is created at
http://www.nielsenonlinesupport.com/hybrid

TAM

Nielsen Tagging Implementation Package is delivered to client

TAM

Client implements code on pages

Client

Sample code is performed to assure that critical issues are
present (ie wrong ID) and code
fires up correctly

TAM

After a few days

of collecting data, d
ata
reconciliation
is performed against client internal
numbers

TAM

[optional] IF

further action is required, an audit may be ran by using Observe Point
(currentl
y
available in US only)

TAM

Once Data QA is completed, account is handed over to Sales/Account manager


A
notification to Product Manager John Brauer should be sent out,
at least until Hybrid is
running in Beta mode

TAM

Update client details at Hybrid
page http://www.nielsenonlinesupport.com/hybrid

TAM

[optional] IF

client is listed in your country TIER 1, set up a maintenance/monitoring plan as
described in referring section

TAM






Tagging Implementation

Overview


1.1

Basic Overview




NetView/SC
Addendum

-

In order to start the implementation process, the Addendum must be returned
to Nielsen signed by the client. Without this document, the TAM cannot start the implementation
process. If you are stuck, please contact
John Brauer

before starting the implementation process.
Template is found here:
SiteCensus
-
NetView Addendum
;




Nielsen Tagging Questionnaire



this questionnaire contains very important information such as
expected page view traffic. This is important for us to be able to monitor the infrastructure capacity.

If
you can’t get this information from the client, you can contact
Colin Brown

before starting the
implementation to check on capacity availability.
Templa
te found here:
Nielsen Digital Ratings Tagging
Pre
-
Screener v2
;







1.2

Nielsen Tagging Implementation
Package

Once you collect the Basic Requirements from your S
ales team, you are ready to send

the Nielsen Tagging
Implementation Tagging. This is very simple and for
new users

it

generally
includes

the following
:


1.

Txt attachment containing the Nielsen taggin
g code (please refrain from sending in the body of the
email);

2.

The
Nielsen Digital Ratings Tagging Guide v2




CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
6

of
31

May 2010

3.

A

brief description of where to place the code ALONG with the client ID to use for each of the domains to
track (see sections on how to create a new Hybrid id with the VCID Tool);





















Sample





Nielsen Tagging Implementation Package




1.3

Pre
-
existing
SC/MI
Clients


For pre
-
existing SC/MI clients who already have the Nielsen tag in place, you have 2 options

1.

Use their existing CI

OR


2.

a) Verify if they already are present in the NetView dictionary (see section ... )

b)
Create a new ID using the VCID tool
described below and have them retagging all pages


Note: currently, Hybrid completely
disregards

the VCID or the CI values present in our tag. Instead, it matches
URLs against the NetView dictionary. Although in the future might change and would be good to

keep all Hybrid
clients aligned, this should be a very light decision

to be taken as of today’s update [ June 11, 2010].


Once you
executed one of the two options above
:

1.

Add the client ID to the ww.nielsenonlinesupport.com/hybrid database

If you don’t
have a login, you can register by using your Nielsen email address

2.







1.4

New Clients

For new clients who do NOT have the Nielsen tag implemented on their pages yet, you must go through the
following process:

Dear Client,

I’m excited to be working with all of you to get hybrid roll
ed out on your sites.

The tags I have attached are for the respective websites foxnews.com and foxbusiness.com

This new code should be placed at the bottom of each page on the site, ideally right before the </body>
tag for maximum accuracy. The document “N
ielsen Digital Ratings Tagging Guide v2” contains further
technical details.


Once the new code is deployed, our servers will start collecting the page events immediately.


I also put together a test URL for you to see how the tag works live and the recor
d you would see through your
favorite network sniffer.

The page below uses our Compact version in an external include file.


http://nielsenonlinesupport.com/support/hybrid/js/



As soon as
you confirm all pages have been tagged up, we will start a QA period to make sure we are
aligned for publishing phase
.


Let me know if you have any further questions.






CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
7

of
31

May 2010

1.

Verify if they already are present in the
NetView dictionary (see section ... )

2.

Create a new Hybrid ID through the VCID Tool

(section ...)

3.

Open a SC account with ONLY the Core module enabled.
Disable everything including geo location and
other content modes such as Mobile and Streaming. See below
for more detailed Walk
-
trhough.

The suggested naming convention for Hybrid SC accounts is the following:

FoxNews (us
-
801796h) Hybrid



The “Hybrid” word will help TAMs search for all Hybrid accounts on the interface




The ID will help identify the Hybrid ID

at a glance without drilling into the account info

4.

Add the client ID to the http://ww.nielsenonlinesupport.com/hybrid database

If you don’t have a login, you can register by using your Nielsen email address




1.5

Code Versions (Hybrid
-
centric & New Clients)

For all new Hybrid clients that do NOT sign up for SC service (other than Core module), t
he recommended
and official Nielsen hybrid tag version for standard roll
-
out is the Compact version.

You can generate this
and other
version
s (
Image Only
, described b
elow)

by using the Nielsen SiteCensus
Intranet V6.0 Code generator found here:

http://reports.redsheriff.com/v60_docs/v60
-
codegen/v60cg.html


[Intranet Access login may be used t
o access this page]





1.5.1

JavaScript (Compact) Version

Most of big network clients will implement our code along o
ther tag vendors such as Omniture

and Goggle
Analytics. They will do so by embedding all the codes in one external JavaScript file hosted on their servers.

Once called within the client external file, o
ur standard SC tag would normally call
an additional JavaScript file
(the library v60.j
s) which might cause performance decay and in some cases it might fail as well.

The
JavaScript (Compact)

Version, as the name alludes, is a self
-
contained version of our standard code, which
will not make sure of our library.

The benefits are many
, hence t
he choice to make it our recommended version:




Much faster to execute


it doesn’t need to load/process our external JavaScript library
;



Easier to implement


copy/paste implementation. No issues related to external or locally stored
JavaScript files
;



Gathers all the info we need for Hybrid
and CORE module reporting in SC;



Ideal for standard and in include files placement;

















<!
--

START Nielsen Online SiteCensus V6.0
--
>

<!
--

COPYRIGHT 2010 Nielsen Online
--
>

<script type="text/javascript">


(function () {


var d = new Image(1, 1);


d.onerror = d.onload = function () {


d.onerror = d.onload = null;


};


d.src = ["//secure
-
us.imrworldwide.com/cgi
-
bin/m?ci=us
-
123456h&cg=0&cc=1&si=", escape(window.location.href), "&rp=",
escape
(document.referrer), "&ts=compact&rnd=", (new Date()).getTime()].join('');


})();

</script>

<noscript>




CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
8

of
31

May 2010

Example of the JavaScript (Compact) Version



HTML
-
ready














Example of the JavaScript (Compact) Version


JavaScript
-
ready


1.5.2

JavaScript
-
less (
Image Only
) Version

In some cases, the client will want to avoid using a JavaScript in their website pages.
In this case, the
Nielsen
Hybrid code

can take the form of a simple image call. Obviously, the client will have to populate the URL of the
page served server
-
side.







Example of the JavaScript
-
less (Image Only) Version



1.6

NetView Dictionary

[in pr
ogress]




1.7

Hybrid client

ID

Generation Process

[in progress]



1.

Login to Nielsen NetView

(function () {


var d = new Image(1, 1);


d.onerror = d.onload = function () {


d.onerror = d.onload = null;


};


d.src = ["//secure
-
us.imrworldwide.com/cgi
-
bin/m?ci=us
-
602927h&cg=0&cc=1&si=", escape(window.location.href), "&rp=",
escape(document.referrer), "&ts=compact&rnd=", (new
Date()).getTime()].join('');


})();


<!
--

START Nielsen Online SiteCensus V6.0
--
>

<!
--

COPYRIGHT 2010 Nielsen Online
--
>

<img src="//secure
-
us
.imrworldwide.com/cgi
-
bin/m?ci=us
-
123456h&amp;cg=0&amp;cc=1&amp;si=http%3A//url&amp;ts=image"
height="1" width="1" alt="" />

<!
--

END Nielsen Online SiteCensus V6.0
--
>



CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
9

of
31

May 2010



2.

Select the Appropriate Country



3.

Click on the Dictionary button







CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
10

of
31

May 2010

4.

Search for the desired enti
ty by Parent, Brand, Channel or

domain/subdomain
.



5.

After double
clicking on the entity the

full MarketView tree will appear.
Note the Parent
Entity and make sure to copy the exact spelling and case.
If the
MarketView entity
does not exist yet, contact the Nielsen account manager who handles the client in
your local reg
ion or market
. Changes to Netview should be submitted to
netviewrequests@nielsen.com



6.

After finding the Parent Entity in the Netview Dictionar
y
,
Login

to the VCID tool

using
Internet Explorer in compatib
ility mode.
(
http://tools.netratings.com/pls/tools/INTERNAL_LOGIN
)







CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
11

of
31

May 2010

7.

Click on “Client Maint/Setup”


8.

Next Click on “Parent Search”.



9.


After the Hierarchy had loaded, use the S
earch
function or Browse through the listings
to find the
Parent Entity
.

If the entity has been created in MarketView and still does not
appear, contact Engineering Panel Support (
EngineeringPanelSupp
ort@netratings.com
)
with the full entity name and its corresponding MarketView parent entity for assistance.


10.

Click on the entity name in the MV Parent Column.







CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
12

of
31

May 2010

11.

Select the Appropriate Country and then click on ‘Add New Client Code’.


Once created
-

the

newest Client ID will appear at the top of your list
.


12.

Now you need to append an h after the numeric value the VCID tool just generated. For
example, if the tool generated a value of us
-
123456, before you distribute to client you
must to change it to:
us
-
123456h This will indentify the value as being assigned to
Hybrid during processing.



13.

Login to the Sitecensus Global Product Intranet (
http://sitecensus.netratings.com
).



14.

Navigate to the V6.0 Code Generator found under Tools> Tagging Tools. And Click on
“ Version 6.0 Tracking Code Generator”





CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
13

of
31

May 2010

15.

Select the appropriate data node and enter the CID value generated by the VCID tool.
Make sure to append an “h’ after the CID va
lue to designate that this is a Hybrid CID.
Enter “0” for the content group and then click “Generate”.





CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
14

of
31

May 2010





1.8

SC Account Creatio
n

Until the Hybrid i
nterface goes live, create a SiteCensus
account for the c
lient so that traffic numbers can be
ver
ified.

This account is NOT for client access. This is for TAM
-
access only. Client should send numbers our way
and not the way around.


1.

Login to the SiteCensus
i
nterface.



2.

Perform a search under the Client Folder to see if Client is already listed in the
SiteCensus Interface. If the Client does not exist use the Add function to add a new
listing.




3.

Use the
Add Function under Accounts to a
dd a new SiteCensus Account.

Enter then
Account name making sure to include the
Hybrid
CID and the word “hybrid” in th
e title to
ensure easy lookup and reference.

Enter the Client Name. Set the product to
SiteCensus and select the appropriate localization settings. Next select the appropriate
instrumentation server for your country/region. The account type should be set t
o CID
based. Enter the Hybrid CID for the Data Directory and the New CID.





CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
15

of
31

May 2010



4.

Next, change the scheduling level to “level 1
-
3 updates”. Enter the estimated daily PI
count. Deselect all Modules except for Core Analysis. Click on Save to create the
account.





1.9

Hybrid Client Online Database

The Hybrid Client Online Database provides
the following information to
TAM’s, Product Management
, and
Account Managers
:

-

Client name

-

Hybrid ID

-

Status

-

Sales rep

-

Volume

-

TAM assigned

-

Client
-
side Tech contact

-

Domain Name


When a new client is implemente
d, a new record must be created
To create a new record


1.

Log in to the Hybrid Client Online Database
www.nielsenonlinesupport.com/hybrid
.



CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
16

of
31

May 2010





2.

Enter the Appropriate
Information in each field and click submit.




DATA
QA &
Audit Process

Once the client confirms deployment of the Nielsen hybrid code across the domain(s), the TAM’s job is to make
sure that what
Nielsen is collecting

approximately 5%

to 10% within the r
ange of
the client internal stats.
Metrics
to compare usually don’t extend over Page Views and Unique Browsers. The period to compare can be a few
days to a week, depending on deadlines and other project dependants.

Ideally, the TAM would want to get the c
lient on track with stats before the end of the month, so that we can track
a full month worth of data for successful Hybridization.


Elements to
keep in
consi
deration
:

-

System used by client (Omniture, Quantcast, Google Analytics, etc.)

-

Position of the tag

within the page

-

Position of our tag in comparison to competitor’s (the one we are comparing stats against)

-

Method of execution (include file,
page body)

-

Custom code (example:
http://ads.foxnews.com/js/ad.js
)

-

Missing pages

(tagging audit)


In case of big discrepancies, it might be necessary to run an audit on the client’s site. For this purpose, we
subscribed to an online web
-
based service that spiders and parses the URLs automa
tically for us: ObservePoint
[login details upon request].


ABCi auditing

will also be
available

as an option to clients and at their expense.











CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
17

of
31

May 2010

QA client
internal

number with Nielsen

overview

[in progress]





























Nielsen
Hybrid Data QA








Domain:


FOXNEWS






Date Range:

June 7
-

May 14, 2010













Nielsen




Omniture



PI

UB

% PI

% UB

PI

UB

6/7/2010

23,201,083

3,842,017

-
45%

1%

42,335,539

3,789,383

6/8/2010

25,131,652

4,150,007

-
35%

2%

38,613,465

4,074,181

6/9/2010

25,381,080

3,994,670

-
37%

2%

40,299,091

3,904,957

6/10/2010

23,465,427

3,894,026

-
37%

1%

37,300,337

3,856,013

6/11/2010

20,612,068

3,593,156

-
43%

1%

35,936,793

3,551,431

6/12/2010

11,920,192

2,323,430

-
34%

-
1%

17,966,981

2,341,907

6/13/2010

11,415,466

2,363,922

-
32%

-
1%

16,726,129

2,388,680

6/14/2010

22,354,097

3,900,927

-
34%

2%

33,720,305

3,821,886

















Observe Point


ObservePoint is a web analytics auditing tool that provides insight of overall and drill down
page
-
level pixel
tracking implementation. Via the online dashboard the TAM will be able to run audits on multiple domains. The
process is automated and by default the spider does BLOCKS the pixel tracking from reaching the vendor,
avoiding generating non
-
h
uman and non
-
necessary traffic load. Op comes with a free Brow
s
er Plug
-
in. OP is
also able to tracks Flash, include
-
files and secure content (via browser plug
-
in). See ObserverPoint FAQ
in
below Appendix
for additional details.


PLEASE READ:

with this cur
rent initial subscription to ObservePoint, our account has a limited number of URLs
that can be audit every calendar month. See current limits below:


Max URLs to be scanned per month:

200,000

Max URLs to be monitored:


50


However, the shared login you
will be using currently can run a maximum of 100,000 of those URLs to avoid
overrunning and allow the USA team to use It fully for the Hybrid implementation round of clients.


1.1 Tagging Audit

Once signed in at
http://my.observepoint.com
, you’ll land in the dashboard area where you will see, currently
scheduled URL monitoring jobs, past audits and also audits that have been shared by other Nielsen users.




CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
18

of
31

May 2010



The main dashboard or Audit Summary screens list you pa
st audits and give you their main stats:



Audit name



URLs found



Overall Analytics deployed; this is NOT Nielsen
-
only, and it includes competitors as well



Status. The audit might be “pending”. In this case you will not be able to EDIT or DELETE it.



Next Aud
it. Unless you periodically want an audit to run for that specific domain (not recommended, see
instructions below, Step 4) you should see AUDIT NOW within this column. If you do NOT see anything
that is because that audit was “shared” by another user. In
this case, you will not be able to Edit nor
Launch it yourself.



Frequency. You should see On
-
Demand unless you scheduled a periodic audit. See above item.



Edit/Delete. You will see this if this is NOT a shared audit. See above item on Next Audit



Editing

an Audit

If you are the owner of the audit, you can edit and change any part of the job before or after launching it.



















CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
19

of
31

May 2010

Starting an Audit

To start an Audit, simply click on “Audit a new domain”, as indicated in the red box above.

There are a

number of configurations to take in consideration. Let’s go through them one by one.



1.
Starting

URL



This is the URL you want to start the audit with. The system is configured to crawl through a site from that point
forward. IF you need to track a
sub
-
domain that is NOT linked within the pages of the Starting URL, see note
below.


Also, if any unlinked pages exists within the domain that you need to audit, you will need to add one Starting
URL for each of those. Example: this could be the landing p
age for a specific campaign.



2. Description & Limit


Description can be anything you want it to be and it will appear in the list of scheduled Audits in the main
dashboard.


Page depth can vary from site to site. Use your judgment. Default is “Up to 4
levels deep”. This generally works
for most sites.


URL Limit is your way to limit the length of your audit. Check your personal/shared URL limit and also make a
judgment based on the size of the site you are about to audit. Example: I use “1,000 URLs per
scan” for big sites
like nytimes.com or FoxNews.com






CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
20

of
31

May 2010

3. Primary Vendor



We are working with OP to get more of our tag versions and methods included in this list. Currently, they identify
our AdEffectiveness version (Nielsen), and our general standard
page
-
level code (Nielsen Online). The ladder is
the one that should be selected for Hybrid auditing.


4. Schedule




This should be set to ON DEMAND, unless you want to run this periodically. This is NOT set by default, you set
this up manually each time
you create new auditing job.


5. Notifications


You can include your email or phone number for alerts informing you that the audit has been completed. Multiple
emails/phone numbers can be entered by separating items with a comma:


Mauro.clerici@nielsen.com,19175133132


Phone notifications might be more appropriate for URL alerts (next section).

To set up phone alerts, this is the following international format:


Country

Example

USA

1
801
5555555

United Kingdom

44
775
3455323

China

86
131
33443322









CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
21

of
31

May 2010

6. Sharing


Please check this box, unless it’s a test you don’t want to share with the team.

If you don’t check this little box, no one will be able to see neither your audit list nor the results.

This is NOT set by default; you set thi
s up manually each time you create new auditing job.



7. Advance Settings


Through this section you will be able add or amend filtering that the spider uses during the site crawling phase.
The system accepts the full set of Regular Expressions.


By defau
lt, OP will perform the audit in “silent” mode. This means the pixel will be executed to track successful
execution, but the record will be blocked from reaching the vendor’s servers (for Nielsen this would be
imrworldwide.com)


The Templates section
allows you to run a quicker audit based on template pages only. It is NOT selected by
default.


Scan Speed can be used if you are auditing a test server.




CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
22

of
31

May 2010


8. Saving



Once you save
the new job, you are taken to the Audit Summary page.



9. Audit Now



From

the Audit Summary page, you are now able to launch your audit.



A NOTE ON AUDIT RUNNING TIMES

Find below a table showing some recent jobs ran. As you can it is hard to foresee running time for a site,
regardless of its size or URLs found during the
crawling process.


Site Name

Max URL

URLs found

Time to audit

Univision.com

1,000

69

12 mins

FoxNews

1,000

1,000

2 hrs

Oprah.com

1,000

1,000

17 mins

News.in.msn.com

4,000

4,000

5 hrs

South Bend Tribune

3,000

2980

2 hrs

Gestionderiesqos

1,000

999

40
mins


There are many reasons that sites go faster or slower based simply
on overall network traffic. We can identify 3

major factors
influencing running time outcome:




CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
23

of
31

May 2010



the actual site response time:
network performance from both sides

(OP server


client

server)
will determine speed of tagging audit.



the accompanying page weight:
the heavier the content, the slower the crawling process.



tagging accuracy:
poorly tagged sites take longer.

In other words, the more pages untagged are
found, the more time the
validation process will take. In fact, OP will check the same page up to
3 times, to make sure the tag to validate the tagging status (missing, broken,

etc)..





Reading the Audit Results


Once the audit is complete, you will receive an email or a txt
message, depending on you set up the Notifications
recipients. Login and browse to either main website dashboard (Home) or from the Audit Summary page. From
there, you will see the list of audit you ran in the past and the one that just completed. Click o
n the domain name
you were notified about.



The
first thing you will notice is the web analytics overview graph listing vendor names and deployment ratio.

Once again, please note that this is an
aggregate

ratio. You might see Omniture scoring 96.30% tota
l
deployment on the site. However, if you dig deeper into their detected list of tags, you will find out the it breaks
down into a number of different values:



CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
24

of
31

May 2010




Look at this break down before jumping to rushed conclusions.

For Nielsen, the breakdown som
ething like this:



This is a breakdown of the Nielsen Online tag.



1.2

Firefox browser’s plug
-
in

Observe Point comes with a free browser plug
-
in that can be used as a sniffer in your Firefox browser.

An additional advantage of this plug
-
in, is that can be
used to monitor pages beyond password
-
protected pages.
Download the plug
-
in here:
http://www.observepoint.com/plugin.php



PLEASE READ:
In order for the plug
-
in to work, you do NOT need to be signed in

your OP account. However,
you must sign in when using the OP plug
-
in to record forms or password
-
protected pages. Please note that
when using the recording feature, URLs are counted against the account URL limit.



Once installed, an icon similar to Httpf
ox or Httpwatch will appear in the bottom right corner of the browser.
When clicked, a side bar will appear revealing the OP browser menus: Session Recorder, and Page Requests.



CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
25

of
31

May 2010


Page Requests features the following tabs: HTML, CSS, JS, Images, Flash, and

Tags. Each of this tabs, when
active, each will show traffic sniffed from the respective category. The Session recorder is used to record
session to allow pixel monitoring beyond password
-
protected pages (see below section for more details.)







1.3

URL Mon
itoring

URL monitoring is recommended and useful when TAMs have doubts on the reliability of the domain tracked.
Doubts for example, could be triggered by a page impression report (via SC or Hybrid tool) that shows a sudden
drop of traffic, even though the

tagging audit shows complete tagging implementation.

For example, due to some unusual variance between Hybrid tagging and HBX metrics, I want to monitor
Foxnews main page
http://www.foxnews.com

for a week or so, to s
ee if our pixel responds reliably to continue
pinging from a third
-
party,remote location.

1.3.1

Setting up an alert

From the left side panel click on the item “Monitor a new URL”



CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
26

of
31

May 2010



1. New URL


Enter domain and/or page to monitor and description that will
appear on dashboard list


2. Location



Enter the location to monitor from. As Foxnews traffic is mainly domestic, and I don’t have concerns coming from
overseas traffic, I will select a San Francisco node.



CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
27

of
31

May 2010


3. Frequency



Frequency can be regulating
depending on site size and environment. I’d usually leave it to 15 min pinging rate,
unless the domain monitored sits on a staging server. In this case, I’d want to minimize probing to a minimum.




4. Alerts


By default, the following is already checked
to run:




Send an “up” alert when this URL has recovered



Send a “down” alert when this URL does not respond



Alert recipient; already populated with your user name. IF you are using a shared login, please
change this to your email or phone number to send ale
rts to (see example below)


As per audit notifications, you can include your email or phone number for alerts informing you that the audit has
been completed. Multiple emails/phone numbers can be entered by separating items with a comma:


Mauro.clerici@nie
lsen.com,19175133132


Phone notifications might be more appropriate in this case.


To set up phone alerts, this is the following international format:


Country

Example

USA

1
801
5555555

United Kingdom

44
775
3455323

China

86
131
33443322



5. Sharing



CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
28

of
31

May 2010



6.

Advance settings
Some more alerts you can set up ad
-
hoc. By default they are all disabled to avoid false positives.Silent mode is
checked by default so that the pixel execution is blocked from reaching the vendor (Nielsen in this case) servers.


7.

Maintenance Windows


Unlike Audting, you don’t have to launch this manually. Once you save the job, it will start running at the preset

frequency.












8. Monitoring
Summary



CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
29

of
31

May 2010


The job now shows on the dashboard list of monitored URLs.




1.3.2

Recording a

path beyond password
-
protected pages

Sometimes audit will fail because the spider is not able to follow links beyond a site’s login page.

Follow the below steps to help OP’s spider following links beyond a password
-
pro0tected page.

The example below is for Spanish site:
http://www.infocharts.com



[
in progress
]



1.4

ABCi auditing process [optional]

This is USA
-
only and is still being worked out by the Hybrid team as an additional option for the
client


















CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
30

of
31

May 2010


TAM Tagging
FAQ

[please do NOT distribute to client
-

contain
s
confidential details]


1.

Are the botfilter rules going to be the same as in SC/MI ?

Yes, the same rules (algorithms) but limits are different (set by Hybrid

MSCi team):



page impressions max rate: 5 page impression sper second (current Census is 10 per
second)



same URL access limit : 100 events within 600 seconds (current Census is 300 per 600
seconds)



ad views daily limit: 4000 (current Sensus : 5000)



Appendix1


TAM
responsibilities

1.

T
AM

will be responsible for obtaining client information from Sales Person. This
includes:

a.

Estimated Monthly Volume

b.

Client Side Technical Contact

c.

Rollout date

2.

TAM will be responsible for Hybrid Code Generation Process as stated
above
.

3.

TAM
will be responsible for sending Hybrid Code and Implementation Guide to client.

4.

TAM will be available to respond to any technical questions or issues faced by the
client

5.

TAM will be responsible for Audit Process as stated above


Appendix 2
-

Recommendatio
ns for update to existing VCID tag generator
(in progress)



1.

Expand existing Videocensus VCID tool to handle generation and lookup of Hybrid CIDs



Videocensus and Hybrid Share similar customer base


2.

Hybrid CID Tool will generate unique alphanumeric CID (us
-
234765)



Ensures that a client’s web traffic will be accurately reported in audience
measurement services, such
as Hybrid

and MarketIntelligence.



Hybrid will be expanding globally
-

CID will be local
ized to each country



Hybrid CID may be linked to MarketView Entity as an option



Multiple ClDs may be needed depending on the complexity of the client’s
implementation


3.

Addition of the following metadata fields will provide useful reference information:




URL:

Wed address where beacon or tag can be located




Implementation Status:

Testing, Live , Dormant




Client Name:

If Hybrid CID is not linked to MV entity




TAM:

Name of TAM managing code implementation




Implementation Type
: Hybrid, Old Video
Beacon, New Video Beacon




Video Player Name:

Name of video player where code is implemented



4.

Considerations



Should Hybrid CID be linked to MV Entity at least at Parent Level?



If Unique CID’s are used Hybrid can support 3 and 6 level hierarchy without
the
need for additional variables such as c6




CONFIDENTIAL


For Internal Purposes


Hybrid Client ID Creation Process

Page
31

of
31

May 2010

Appendix 3


Regional Notes


USA

Clients in this region will fall in one of the following tiers:




Tier 1

o

Response as soon as possible.


Even if you don’t have an answer that you let them you
received their
request and are looking into it for them.

o

Even if they use the Ticketing System for queries (which I recommend) a personal email
explaining the situation.

o

Push for < 4 hr resolution times.


Goal of same day resolution of issues if practical.

o

That you have
the contact information close at hand for their Tech contacts and you
clearly know the name of the Sales Rep.

o

Personal notification (phone/email) if we see a drop in traffic. (We’ll have system that
notify us automatically).

o

Personal Ownership of the accou
nt


They have your Cell Phone Number and can
reach you directly

o

You are the dedicated TAM.


That TAM should be the only communication point unless
on vacation/sick.



Tier 2

o

Respond same day. Even if you don’t know the answer.

o

Encourage them to use Ticketin
g System for all queries but they can also cc you.

o

Be able to find the tech contact and sales reps name.



o

Aim for less than 48hr resolution time.

o

They have your Work Phone number and Email.

o

Anyone on the team can help you if required.




Tier 3



Email Suppor
t preferred.



Must use Ticketing System for any query.



No dedicated TAM.



Goal of 48hr response time.

Appendix 3


Tagging Audit expected running times


There are many reasons that sites go faster or slower based simply on overall network traffic. But two major
factors for our service are the actual site response time, with the accompanying page weight. The second has to
do with what tags are selected to

be expected, therefore we triple verify, and how well tag implementation is
done. For every page we see untagged, that page now takes at least 3 times as long, so poorly tagged sites are
slow.

As a side note, one feature that a customer is paying for i
s the ability to add more servers to a scan to go even
faster. This feature will make it into our service and your account soon, I would say every scan will now be able
to go twice as fast, if they are large and have good infrastructure.