Digital Measurement Testing - Revision history

ColinBrown at 00:56, 10 September 2020

2020-09-10T00:56:30Z

← Older revision		Revision as of 00:56, 10 September 2020
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|DCR & DTVR}} {{CurrentBreadcrumb}}		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|US DCR & DTVR}} {{CurrentBreadcrumb}}
	[[Category:Digital]]		[[Category:Digital]]

LaMarHolmes: /* Step 6: Static View Ping */

2020-08-03T18:27:48Z

Step 6: Static View Ping

← Older revision		Revision as of 18:27, 3 August 2020
Line 55:		Line 55:
	\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| us-123456		\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| us-123456
	\|-		\|-
	\| asn \|\| Asset Name~~/Section~~ – this value should represent the asset’s name assigned in the metadata. \|\| Page-Asset		\| asn \|\| Section/Asset Name – this value should represent the asset’s name assigned in the metadata. \|\| Page-Asset
	\|-		\|-
	\| at \|\| Action Type \|\| Start		\| at \|\| Action Type \|\| Start

LaMarHolmes at 18:27, 3 August 2020

2020-08-03T18:27:17Z

← Older revision		Revision as of 18:27, 3 August 2020
Line 55:		Line 55:
	\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| us-123456		\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| us-123456
	\|-		\|-
	\| asn \|\| Asset Name – this value should represent the asset’s name assigned in the metadata. \|\| Page-Asset		\| asn \|\| Asset Name/Section – this value should represent the asset’s name assigned in the metadata. \|\| Page-Asset
	\|-		\|-
	\| at \|\| Action Type \|\| Start		\| at \|\| Action Type \|\| Start

Admin: +Testing note

2019-01-14T21:20:49Z

+Testing note

← Older revision		Revision as of 21:20, 14 January 2019
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|DCR & DTVR}} {{CurrentBreadcrumb}}		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|DCR & DTVR}} {{CurrentBreadcrumb}}
	[[Category:Digital]]		[[Category:Digital]]

			<blockquote>'''Note:''' Due to the variable and unique nature of each application, there may be additional testing required by Nielsen that is not listed here. These tests are completed to ensure the quality of data collected. Please speak with your account manager if you have any questions.</blockquote>

	== Monitoring Tools ==		== Monitoring Tools ==

ShaneHartman: Moved user agent check out of header into numbered list

2018-05-18T14:48:50Z

Moved user agent check out of header into numbered list

← Older revision		Revision as of 14:48, 18 May 2018
Line 7:		Line 7:
	*'''Fiddler:''' http://www.telerik.com/fiddler		*'''Fiddler:''' http://www.telerik.com/fiddler

	== Verify User Agent ==		== Step 1: Filter traffic ==
			Filter HTTP traffic with the string "imr" to capture traffic from the SDK as shown in the below figure. This will capture traffic going to Nielsen servers. Now set up the device to proxy to this traffic analyzer.
			<blockquote>'''Note:''' Instructions may vary from device to device and are available online.</blockquote>
			[[File:fiddler-web-debugger.png\|link=]]

			== Step 2: Verify User Agent ==
	Verify that your user agent is not being flagged as bot traffic. <br />		Verify that your user agent is not being flagged as bot traffic. <br />

Line 20:		Line 25:
	.build();</syntaxhighlight>		.build();</syntaxhighlight>

	== Step ~~1: Filter traffic ==~~		== Step 3: Check Opt-Out ==
	Filter HTTP traffic with the string "imr" to capture traffic from the SDK as shown in the below figure. This will capture traffic going to Nielsen servers. Now set up the device to proxy to this traffic analyzer.
	~~<blockquote>'''Note:''' Instructions may vary from device to device and are available online.</blockquote>~~
	~~[[File:fiddler-web-debugger.png\|link=]]~~

	~~== Step 2~~: Check Opt-Out ==
	If the opt-out function or app disable feature is previously tested, it has to be ensured that an opt-in is completed on the device before continuing. Terminate the app completely before starting.		If the opt-out function or app disable feature is previously tested, it has to be ensured that an opt-in is completed on the device before continuing. Terminate the app completely before starting.

	== Step 3: Hello Ping ==		== Step 4: Hello Ping ==
	The first HTTPS traffic that should be seen is the SDK request for configuration information, called a '''hello ping'''. In order to see this ping, Charles / Fiddler has to be configured to capture HTTPS traffic.		The first HTTPS traffic that should be seen is the SDK request for configuration information, called a '''hello ping'''. In order to see this ping, Charles / Fiddler has to be configured to capture HTTPS traffic.

Line 36:		Line 36:
	<blockquote>'''Note:''' If this ping fails to fire, it is likely that the instance of the SDK failed to initialize. Please see Initialization ([[iOS SDK API Reference#Initialization\|iOS SDK API Reference - Initialization]] and [[Android SDK API Reference#Initialization\|Android SDK API Reference - Initialization]]) to see how to initialize the SDK.</blockquote>		<blockquote>'''Note:''' If this ping fails to fire, it is likely that the instance of the SDK failed to initialize. Please see Initialization ([[iOS SDK API Reference#Initialization\|iOS SDK API Reference - Initialization]] and [[Android SDK API Reference#Initialization\|Android SDK API Reference - Initialization]]) to see how to initialize the SDK.</blockquote>

	== Step 4: The L Ping ==		== Step 5: The L Ping ==
	When the app is started after installing for the first time, and app is measuring '''DCR Static''' content only, a DCR static app launch known as '''L''' ping firing to secure-dcr.imrworldwide.com server in the traffic-monitor should be seen. However, the '''L''' ping will be observed again if app goes into background and resumes back after 5 minutes.		When the app is started after installing for the first time, and app is measuring '''DCR Static''' content only, a DCR static app launch known as '''L''' ping firing to secure-dcr.imrworldwide.com server in the traffic-monitor should be seen. However, the '''L''' ping will be observed again if app goes into background and resumes back after 5 minutes.

Line 43:		Line 43:
	If the app is measuring '''DCR Video Content''' only, then the '''hello ping''' will fire but the '''L''' ping will not be observed upon app launch.		If the app is measuring '''DCR Video Content''' only, then the '''hello ping''' will fire but the '''L''' ping will not be observed upon app launch.

	== Step 5: Static View Ping ==		== Step 6: Static View Ping ==
	For any sections that are tagged for static content, a '''DCR Static – view''' ping should be received. The first landing page should always be tagged. An example of this ping is:		For any sections that are tagged for static content, a '''DCR Static – view''' ping should be received. The first landing page should always be tagged. An example of this ping is:

Line 68:		Line 68:
	\|}		\|}

	== Step 6: Video View Ping ==		== Step 7: Video View Ping ==
	Approximately 60 seconds into viewing of the stream, a '''DCR Video – view''' ping fire to secure-dcr.imrworldwide.com server indicated by the '''cr''' value containing a '''V''' in the format of 4_00_99_'''V'''1_00000 should be seen.		Approximately 60 seconds into viewing of the stream, a '''DCR Video – view''' ping fire to secure-dcr.imrworldwide.com server indicated by the '''cr''' value containing a '''V''' in the format of 4_00_99_'''V'''1_00000 should be seen.

Line 91:		Line 91:
	<blockquote>'''Note:''' If this ping fails to fire, a common cause is improper metadata being passed to the SDK. Examples of the proper metadata to be passed in the </code>loadMetadata</code></blockquote>		<blockquote>'''Note:''' If this ping fails to fire, a common cause is improper metadata being passed to the SDK. Examples of the proper metadata to be passed in the </code>loadMetadata</code></blockquote>

	== Step 7: Video Duration Ping ==		== Step 8: Video Duration Ping ==
	The first duration ping is fired after 5 minutes of content is viewed. A '''DCR Video''' – duration ping fire to secure-dcr.imrworldwide.com indicated by the '''cr''' value containing a '''D''' in the format of 4_00_99_'''D'''1_11111 should be seen. This D ping should fire approximately every 5 minutes after the initial duration ping has fired or when the content switches to an advertisement. The ad length (c51) is the total ad duration viewed in the previous session, and the ad count (c52) is the number of ads viewed in previous segment.		The first duration ping is fired after 5 minutes of content is viewed. A '''DCR Video''' – duration ping fire to secure-dcr.imrworldwide.com indicated by the '''cr''' value containing a '''D''' in the format of 4_00_99_'''D'''1_11111 should be seen. This D ping should fire approximately every 5 minutes after the initial duration ping has fired or when the content switches to an advertisement. The ad length (c51) is the total ad duration viewed in the previous session, and the ad count (c52) is the number of ads viewed in previous segment.
	{\| class="wikitable"		{\| class="wikitable"
Line 117:		Line 117:
	<blockquote>'''Note:''' If this ping fails to fire, it may be caused by not passing the setPlayheadPosition API call as expected. The instruction as well as examples can be found in the Developer’s Guide.</code></blockquote>		<blockquote>'''Note:''' If this ping fails to fire, it may be caused by not passing the setPlayheadPosition API call as expected. The instruction as well as examples can be found in the Developer’s Guide.</code></blockquote>

	== Step 8: 5min Duration Ping ==		== Step 9: 5min Duration Ping ==
	View all channels for 5 minutes to ensure all channels fire a '''duration''' ping.		View all channels for 5 minutes to ensure all channels fire a '''duration''' ping.

	== Step 9: Pending Duration Ping ==		== Step 10: Pending Duration Ping ==
	Play a stream and move the app to the background. A pending '''duration''' ping should fire; crediting the appropriate number of minutes viewed from last ping (i.e. 4_00_99_D1_'''111'''00). No other pings should fire after it has been moved to the background. In case SDK does not get a chance to send out the ping while going to background, SDK will send the pending ping on next re-launch.		Play a stream and move the app to the background. A pending '''duration''' ping should fire; crediting the appropriate number of minutes viewed from last ping (i.e. 4_00_99_D1_'''111'''00). No other pings should fire after it has been moved to the background. In case SDK does not get a chance to send out the ping while going to background, SDK will send the pending ping on next re-launch.

	== Step 10: Pending Duration Pings cont. ==		== Step 11: Pending Duration Pings cont. ==
	The same action will occur with any interruption to the stream’s playback (e.g., alarm, incoming call, etc.).		The same action will occur with any interruption to the stream’s playback (e.g., alarm, incoming call, etc.).

	== Step 11: Opt-Out Implementation ==		== Step 12: Opt-Out Implementation ==
	Test the Opt-Out implementation in four steps.		Test the Opt-Out implementation in four steps.
	*Complete an opt-out in the app through the Nielsen opt-out webview.		*Complete an opt-out in the app through the Nielsen opt-out webview.

ShaneHartman: added instructions to verify user agent using Device Atlas Tool

2018-04-18T21:45:47Z

added instructions to verify user agent using Device Atlas Tool

@@ Line 6: / Line 6: @@
 *'''Charles:''' http://www.charlesproxy.com
 *'''Fiddler:''' http://www.telerik.com/fiddler
 == Step 1: Filter traffic ==

MagdalenaKostulska: /* Step 7: Video Duration Ping */

2017-10-26T09:11:26Z

Step 7: Video Duration Ping

← Older revision		Revision as of 09:11, 26 October 2017
Line 84:		Line 84:
	! Parameter !! Description !! Example		! Parameter !! Description !! Example
	\|-		\|-
	\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| ~~APRP7~~		\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| us-123456
	\|-		\|-
	\| asn \|\| Asset Name – this value should represent asset’s name assigned in the metadata. \|\| Video-Asset		\| asn \|\| Asset Name – this value should represent asset’s name assigned in the metadata. \|\| Video-Asset

MagdalenaKostulska: /* Step 6: Video View Ping */

2017-10-26T09:10:56Z

Step 6: Video View Ping

← Older revision		Revision as of 09:10, 26 October 2017
Line 62:		Line 62:
	! Parameter !! Description !! Example		! Parameter !! Description !! Example
	\|-		\|-
	\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| ~~APRP7~~		\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| us-123456
	\|-		\|-
	\| asn \|\| Asset Name – this value should represent asset’s name assigned in the metadata. \|\| Video-Asset		\| asn \|\| Asset Name – this value should represent asset’s name assigned in the metadata. \|\| Video-Asset

MagdalenaKostulska: /* Step 5: Static View Ping */

2017-10-26T09:10:25Z

Step 5: Static View Ping

← Older revision		Revision as of 09:10, 26 October 2017
Line 38:		Line 38:
	! Parameter !! Description !! Example		! Parameter !! Description !! Example
	\|-		\|-
	\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| ~~APRP7~~		\| ci \|\| Client ID – this value should be consistent throughout all of the pings that fire for the implementation. \|\| us-123456
	\|-		\|-
	\| asn \|\| Asset Name – this value should represent the asset’s name assigned in the metadata. \|\| Page-Asset		\| asn \|\| Asset Name – this value should represent the asset’s name assigned in the metadata. \|\| Page-Asset

Admin at 19:01, 7 August 2017

2017-08-07T19:01:05Z

← Older revision		Revision as of 19:01, 7 August 2017
Line 90:		Line 90:
	\| tl \|\| Episode Title \|\| Episode Name – S2 – E1 – LF		\| tl \|\| Episode Title \|\| Episode Name – S2 – E1 – LF
	\|-		\|-
	\| cr \|\| Crediting Ping Identifier \|\| ~~1_00_99_D1_11111~~		\| cr \|\| Crediting Ping Identifier \|\| 4_00_99_V1_00000
	\|-		\|-
	\| rt \|\| This Value should be “video” and indicates that this is a DCR tag for video content. \|\| video		\| rt \|\| This Value should be “video” and indicates that this is a DCR tag for video content. \|\| video