DCR Static Lite Browser SDK - Revision history

ColinBrown at 15:48, 23 September 2021

2021-09-23T15:48:39Z

← Older revision		Revision as of 15:48, 23 September 2021
Line 6:		Line 6:
	[[Image:AlertIcon.png\|left\|60px\|link=\|class=smallIcon]] DCR Static Lite has been Sunset. If you are currently using this solution, please reach out to your Technical Account Manager.		[[Image:AlertIcon.png\|left\|60px\|link=\|class=smallIcon]] DCR Static Lite has been Sunset. If you are currently using this solution, please reach out to your Technical Account Manager.
	</blockquote>		</blockquote>
	<--!
			<!--

	DCR Static Lite <Page Measurement> allows clients to measure the time spent by users on static content (in focus). Unlike Video measurement, the Static Lite <Page Measurement> does not require a configuration file.		DCR Static Lite <Page Measurement> allows clients to measure the time spent by users on static content (in focus). Unlike Video measurement, the Static Lite <Page Measurement> does not require a configuration file.
	* The cadence of the View and Duration pings for DCR Static Lite is same as Video content. (View ping when content is loaded completely and Duration ping every 5 minutes following that).		* The cadence of the View and Duration pings for DCR Static Lite is same as Video content. (View ping when content is loaded completely and Duration ping every 5 minutes following that).

ColinBrown at 15:48, 23 September 2021

2021-09-23T15:48:08Z

← Older revision		Revision as of 15:48, 23 September 2021
Line 3:		Line 3:

	== Overview ==		== Overview ==
			<blockquote>
			[[Image:AlertIcon.png\|left\|60px\|link=\|class=smallIcon]] DCR Static Lite has been Sunset. If you are currently using this solution, please reach out to your Technical Account Manager.
			</blockquote>
			<--!
	DCR Static Lite <Page Measurement> allows clients to measure the time spent by users on static content (in focus). Unlike Video measurement, the Static Lite <Page Measurement> does not require a configuration file.		DCR Static Lite <Page Measurement> allows clients to measure the time spent by users on static content (in focus). Unlike Video measurement, the Static Lite <Page Measurement> does not require a configuration file.
	* The cadence of the View and Duration pings for DCR Static Lite is same as Video content. (View ping when content is loaded completely and Duration ping every 5 minutes following that).		* The cadence of the View and Duration pings for DCR Static Lite is same as Video content. (View ping when content is loaded completely and Duration ping every 5 minutes following that).
Line 149:		Line 153:
	== Testing an Implementation - Browser ==		== Testing an Implementation - Browser ==
	See [[Digital Measurement Testing]].		See [[Digital Measurement Testing]].
			-->

ColinBrown at 01:01, 10 September 2020

2020-09-10T01:01:28Z

← Older revision		Revision as of 01:01, 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]]

Admin: 30m to 5m in overview

2019-05-07T20:30:55Z

30m to 5m in overview

← Older revision		Revision as of 20:30, 7 May 2019
Line 14:		Line 14:
	\| Requires a configuration file. \|\| Does not require a configuration file.		\| Requires a configuration file. \|\| Does not require a configuration file.
	\|-		\|-
	\| Duration ping cadence is every 30 minutes. \|\| Duration ping cadence is every 5 minutes.		\| Duration ping cadence is every 5 minutes. \|\| Duration ping cadence is every 5 minutes.
	\|}		\|}

Admin3 at 19:17, 28 February 2019

2019-02-28T19:17:38Z

← Older revision		Revision as of 19:17, 28 February 2019
Line 139:		Line 139:
	== Privacy and Opt-Out ==		== Privacy and Opt-Out ==
	* As a global information and measurement leader, we are committed to protecting the privacy and security of the data we collect, process and use. Our digital measurement products are not used to identify the consumer in any way, but they help us and our clients measure and analyze how consumers engage with media across online, mobile and emerging technologies, and offer insights into consumer behavior.		* As a global information and measurement leader, we are committed to protecting the privacy and security of the data we collect, process and use. Our digital measurement products are not used to identify the consumer in any way, but they help us and our clients measure and analyze how consumers engage with media across online, mobile and emerging technologies, and offer insights into consumer behavior.

	* The site must provide a means for the user to opt-out of, or opt back into, Nielsen Measurement. A user can opt-out if they would prefer not to participate in any Nielsen online measurement research. To implement the User Opt-Out option, include the following link to the Nielsen Digital Measurement Privacy Policy at https://priv-policy.imrworldwide.com/priv/browser/us/en/optout.html		* The site must provide a means for the user to opt-out of, or opt back into, Nielsen Measurement. A user can opt-out if they would prefer not to participate in any Nielsen online measurement research. To implement the User Opt-Out option, include the following link to the Nielsen Digital Measurement Privacy Policy at https://priv-policy.imrworldwide.com/priv/browser/us/en/optout.html

	* On the Nielsen Digital Measurement Privacy Policy page, users can click Choices to read more detailed information about the measurement software, learn about their options with regard to Nielsen measurement, and, if they do not want to participate in Nielsen online measurement, click a link to receive an opt-out cookie.		* On the Nielsen Digital Measurement Privacy Policy page, users can click Choices to read more detailed information about the measurement software, learn about their options with regard to Nielsen measurement, and, if they do not want to participate in Nielsen online measurement, click a link to receive an opt-out cookie.

Admin3 at 19:17, 28 February 2019

2019-02-28T19:17:05Z

← Older revision		Revision as of 19:17, 28 February 2019
Line 137:		Line 137:
	</syntaxhighlight>		</syntaxhighlight>

	== ~~Nielsen Measurement~~ Opt-Out ~~Implementation~~ ==		== Privacy and Opt-Out ==
	* As a global information and measurement leader, we are committed to protecting the privacy and security of the data we collect, process and use. Our digital measurement products are not used to identify the consumer in any way, but they help us and our clients measure and analyze how consumers engage with media across online, mobile and emerging technologies, and offer insights into consumer behavior.		* As a global information and measurement leader, we are committed to protecting the privacy and security of the data we collect, process and use. Our digital measurement products are not used to identify the consumer in any way, but they help us and our clients measure and analyze how consumers engage with media across online, mobile and emerging technologies, and offer insights into consumer behavior.
	* ~~When~~ the user ~~wants~~ to opt in or opt out of Nielsen measurement, ~~a new dynamic page (with content similar~~ to ~~http~~://~~secure~~-us.imrworldwide.com/~~nielsen_app_optout~~.html ~~should be displayed.~~		* The site must provide a means for the user to opt-out of, or opt back into, Nielsen Measurement. A user can opt-out if they would prefer not to participate in any Nielsen online measurement research. To implement the User Opt-Out option, include the following link to the Nielsen Digital Measurement Privacy Policy at https://priv-policy.imrworldwide.com/priv/browser/us/en/optout.html
	*~~For~~ more ~~details~~, ~~refer~~ to ~~[[Browser SDK API Reference#Browser Opt-Out Implementation\|Browser SDK API Reference - Browser Opt-Out Implementation]]~~ and Nielsen ~~Digital Privacy~~.		* On the Nielsen Digital Measurement Privacy Policy page, users can click Choices to read more detailed information about the measurement software, learn about their options with regard to Nielsen measurement, and, if they do not want to participate in Nielsen online measurement, click a link to receive an opt-out cookie.

	== Pre-Certification Checklists ==		== Pre-Certification Checklists ==

Admin at 23:16, 26 January 2018

2018-01-26T23:16:47Z

← Older revision		Revision as of 23:16, 26 January 2018
Line 18:		Line 18:

	== Prerequisites ==		== Prerequisites ==
	~~<br />~~		To start using the App SDK, the following items are required:
	To ~~get started~~, ~~an App ID is needed. The App ID is a unique ID assigned to~~ the ~~site. This will be provided upon starting the integration.~~		{\| class="wikitable"
			\|-
	~~<syntaxhighlight lang~~="~~html~~">		! style="width: 30px;" \|
			! style="width: 15%;" \| Item
	~~apid~~: "~~PXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX~~"		! Description
			! Source
	</~~syntaxhighlight>~~		\|-
			\|\| ☑ \|\| '''App ID (appid)''' \|\| Unique ID assigned to the player/site and configured by product. \|\| Contact Nielsen
			\|}

	== DCR Static Lite Implementation ==		== DCR Static Lite Implementation ==

Admin: dcr-cert

2017-11-14T19:52:00Z

dcr-cert

← Older revision		Revision as of 19:52, 14 November 2017
Line 35:		Line 35:

	'''with HTTPS URL'''		'''with HTTPS URL'''
	<syntaxhighlight lang='javascript'><script async src="https://seccdn-gl.imrworldwide.com/novms/js/2/nlsDcrLite510.min.js#nol_sfcode=dcr~~-cert~~&nol_ci=AB-XXXXXX&nol_apid=TXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX&nol_assetname=My_assetname&nol_apn=My_AppName&nol_ad=0&nol_vc=b02&nol_devid=XXXX-XXXX-XXXX&nol_segA=NA&nol_segB=NA&nol_segC=NA"></script></syntaxhighlight>		<syntaxhighlight lang='javascript'><script async src="https://seccdn-gl.imrworldwide.com/novms/js/2/nlsDcrLite510.min.js#nol_sfcode=dcr&nol_ci=AB-XXXXXX&nol_apid=TXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX&nol_assetname=My_assetname&nol_apn=My_AppName&nol_ad=0&nol_vc=b02&nol_devid=XXXX-XXXX-XXXX&nol_segA=NA&nol_segB=NA&nol_segC=NA"></script></syntaxhighlight>
	'''with HTTP URL'''		'''with HTTP URL'''
	<syntaxhighlight lang='javascript'><script async src="http://cdn-gl.imrworldwide.com/novms/js/2/nlsDcrLite510.min.js#nol_sfcode=dcr~~-cert~~&nol_ci=AB-XXXXXX&nol_apid=TXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX&nol_assetname=My_assetname&nol_apn=My_AppName&nol_ad=0&nol_vc=b02&nol_devid=XXXX-XXXX-XXXX&nol_segA=NA&nol_segB=NA&nol_segC=NA"></script></syntaxhighlight>		<syntaxhighlight lang='javascript'><script async src="http://cdn-gl.imrworldwide.com/novms/js/2/nlsDcrLite510.min.js#nol_sfcode=dcr&nol_ci=AB-XXXXXX&nol_apid=TXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX&nol_assetname=My_assetname&nol_apn=My_AppName&nol_ad=0&nol_vc=b02&nol_devid=XXXX-XXXX-XXXX&nol_segA=NA&nol_segB=NA&nol_segC=NA"></script></syntaxhighlight>

AndrewKlaasse: updated whole page

2017-08-14T17:13:18Z

updated whole page

← Older revision		Revision as of 17:13, 14 August 2017
Line 18:		Line 18:

	== Prerequisites ==		== Prerequisites ==
	To ~~start using the Browser SDK~~, ~~the following details are required:~~		<br />
	* '''App ID ~~(apid):''' Unique~~ ID assigned to the ~~player/~~site ~~and configured by product~~.		To get started, an App ID is needed. The App ID is a unique ID assigned to the site. This will be provided upon starting the integration.
	* '''sfcode:''' Unique identifier for the environment that the ~~SDK should point to~~. ~~Use the sfcode of~~ "~~dcr~~".
	~~If you do not have any of these pre~~-~~requisites or if you have any questions, please contact our SDK sales support team.~~		<syntaxhighlight lang="html">

			apid: "PXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"

			</syntaxhighlight>

	== DCR Static Lite Implementation ==		== DCR Static Lite Implementation ==
Line 47:		Line 51:
	! Parameter !! Description !! Required? !! Specified by !! Example		! Parameter !! Description !! Required? !! Specified by !! Example
	\|-		\|-
	\| nol_sfcode \|\| Location of collection environment. ~~During testing, all traffic should be directed to “dcr-cert”.~~ \|\| Yes \|\| Nielsen \|\| dcr~~-cert~~		\| nol_sfcode \|\| Location of collection environment. \|\| Yes \|\| Nielsen \|\| dcr
	\|-		\|-
	\| nol_ci \|\| Brand level aggregation \|\| Yes \|\| Nielsen \|\| My_ClientID		\| nol_ci \|\| Brand level aggregation \|\| Yes \|\| Nielsen \|\| My_ClientID
	\|-		\|-
	\| nol_apid \|\| UniqueID assigned to player/site. \|\| Yes \|\| Nielsen \|\| ~~TXXXXXXXX~~-XXXX-XXXX-XXXX-XXXXXXXXXXXX		\| nol_apid \|\| UniqueID assigned to player/site. \|\| Yes \|\| Nielsen \|\| PXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
	\|-		\|-
	\| nol_assetname \|\| ~~Unique ID assigned~~ to ~~content~~ \|\| Yes \|\| Client \|\| My_assetname		\| nol_assetname \|\| Section of each site (e.g. section value should be first <br />
			level in page URL: website.com/section). Limit to 25 unique values
			\|\| Yes
			\|\| Client
			\|\| My_assetname
	\|-		\|-
	\| nol_apn \|\| User-defined string value for describing the player/site. \|\| Yes \|\| Client \|\| My_AppName		\| nol_apn \|\| User-defined string value for describing the player/site. \|\| Yes \|\| Client \|\| My_AppName
	\|-		\|-
	\| nol_vc \|\| Sub-brand level aggregation \|\| Yes \|\| Client \|\| ~~vcID~~		\| nol_vc \|\| Sub-brand level aggregation \|\| Yes \|\| Client \|\| VCID
	\|-		\|-
	\| nol_segA \|\| Segment A~~. (defaults to NA)~~ \|\| No \|\| Client \|\| NA		\| nol_segA \|\| Segment A custom segment for reporting \|\| No \|\| Client \|\| NA
	\|-		\|-
	\| nol_segB \|\| Segment B~~. (defaults to NA)~~ \|\| No \|\| Client \|\| NA		\| nol_segB \|\| Segment B custom segment for reporting \|\| No \|\| Client \|\| NA
	\|-		\|-
	\| nol_segC \|\| Segment C~~. (defaults to NA)~~ \|\| No \|\| Client \|\| NA		\| nol_segC \|\| Segment C custom segment for reporting \|\| No \|\| Client \|\| NA
	\|}		\|}

			The values passed through the Nielsen keys will determine the breakouts that are seen in reporting. The custom segments (A, B & C) will roll into the sub-brand. To not use custom segments A, B and C, do not pass any value in these keys.

			'''Aggregation Limits'''
			There are limits on the number of unique values that can be aggregated on in reporting. The specific limitations by key are:
			{\| class="wikitable"
			\|-
			! Key !! Aggregation Limit
			\|-
			\| section \|\| Maximum of 25 unique values (section <= 25)
			\|-
			\| segA \|\| Maximum number of unique values allowed across segA, segB, and segC is 25 (segA + segB + segC<= 25)
			\|-
			\| segB \|\| Maximum number of unique values allowed across segA, segB, and segC is 25 (segA + segB + segC<= 25)
			\|-
			\| segC \|\| Maximum number of unique values allowed across segA, segB, and segC is 25 (segA + segB + segC<= 25)
			\|}


	== Advanced Tag Implementation ==		== Advanced Tag Implementation ==

Admin3: Removed nol_apv nol_cref1 nol_cref2 nol_ad nol_devid

2017-06-21T23:33:26Z

Removed nol_apv nol_cref1 nol_cref2 nol_ad nol_devid

← Older revision		Revision as of 23:33, 21 June 2017
Line 58:		Line 58:
	\|-		\|-
	\| nol_vc \|\| Sub-brand level aggregation \|\| Yes \|\| Client \|\| vcID		\| nol_vc \|\| Sub-brand level aggregation \|\| Yes \|\| Client \|\| vcID
	\|-
	~~\| nol_apv \|\| Version of the app build \|\| Yes \|\| Client \|\| 1.0~~
	\|-		\|-
	\| nol_segA \|\| Segment A. (defaults to NA) \|\| No \|\| Client \|\| NA		\| nol_segA \|\| Segment A. (defaults to NA) \|\| No \|\| Client \|\| NA
Line 66:		Line 64:
	\|-		\|-
	\| nol_segC \|\| Segment C. (defaults to NA) \|\| No \|\| Client \|\| NA		\| nol_segC \|\| Segment C. (defaults to NA) \|\| No \|\| Client \|\| NA
	\|-
	~~\| nol_cref1 \|\| Standard episode ID. This is a custom parameter \|\| No \|\| Client \|\| Reference11~~
	\|-
	~~\| nol_cref2 \|\| Content originator (required only for distributors). This is a custom parameter \|\| No \|\| Client \|\| Reference 22~~
	\|-
	~~\| nol_ad \|\| Access method (defaults to 0) \|\| No \|\| Client \|\| 0 for browser, 1 for app~~
	\|-
	~~\| nol_devid \|\| Device id. Defaults to blank if not provided. \|\| No \|\| Client \|\| myDeviceID~~
	\|}		\|}