Digital Measurement FAQ - Revision history

NickParrucci: /* Are the Privacy Policy and opt-out URLs the same? If not, is there a method that delivers the Privacy Policy URL? */

2023-04-06T15:26:27Z

Are the Privacy Policy and opt-out URLs the same? If not, is there a method that delivers the Privacy Policy URL?

← Older revision		Revision as of 15:26, 6 April 2023
Line 126:		Line 126:

	==== Are the Privacy Policy and opt-out URLs the same? If not, is there a method that delivers the Privacy Policy URL? ====		==== Are the Privacy Policy and opt-out URLs the same? If not, is there a method that delivers the Privacy Policy URL? ====
	No, they are not the same. There is a link to our opt-out page that goes into the app itself. This URL is never hardcoded into the app and there is a method [[userOptOutURLString()]] to pull the URL from the App SDK. For our Privacy Policy, refer to [[Nielsen Privacy Requirements]]~~. The same can also be accessed from the link to our privacy policy in the app store description (Work in progress)~~.		No, they are not the same. There is a link to our opt-out page that goes into the app itself. This URL is never hardcoded into the app and there is a method [[userOptOutURLString()]] to pull the URL from the App SDK. For our Privacy Policy, refer to [[Nielsen Privacy Requirements]].

	==== Is there a separate Terms & Conditions page to link to, apart from privacy policy URL? Is there a method that delivers this URL? ====		==== Is there a separate Terms & Conditions page to link to, apart from privacy policy URL? Is there a method that delivers this URL? ====

ColinBrown at 00:56, 10 September 2020

2020-09-10T00:56:57Z

← 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]]

Admin at 23:48, 29 May 2019

2019-05-29T23:48:20Z

← Older revision		Revision as of 23:48, 29 May 2019
Line 199:		Line 199:
	**com.google.android.gms.common.GooglePlayServicesRepairableException;		**com.google.android.gms.common.GooglePlayServicesRepairableException;
	**com.google.android.gms.common.GooglePlayServicesNotAvailableException		**com.google.android.gms.common.GooglePlayServicesNotAvailableException

	==== We are currently using AppSDK 1.2.3 (for Android). What is the recommended way to switch to Adobe VHL Joint SDK without affecting our current implementation? (OR) How do I get tracking metrics for both Nielsen and Adobe? ====
	Adobe VHL Joint SDK component bundle contains '''Nielsen AppSDK 4.0.0''' which is capable of measuring all Nielsen measurement products like mTVR / DTVR, Digital Audio/Radio and mDAR measurements along with Digital Content Ratings (DCR). Starting from Nielsen AppSDK version 4.0.0, Nielsen AppSDK is no longer singleton and is capable of tracking up to 4 players at a time. To accommodate this change, Nielsen AppSDK initialization API is modified from a static API <code>AppSdk.getInstance (context, config, iappNotifier)</code> to a constructor <code>AppSdk (context, config, iappNotifier)</code>. Perform [[these steps]] to implement Adobe VHL Joint SDK.

	==== We are currently using AppSDK 4.0.0 (for Android). What is the recommended way to switch to Adobe VHL Joint SDK without affecting our current implementation? (OR) How do we get tracking metrics for both Nielsen and Adobe? ====		==== We are currently using AppSDK 4.0.0 (for Android). What is the recommended way to switch to Adobe VHL Joint SDK without affecting our current implementation? (OR) How do we get tracking metrics for both Nielsen and Adobe? ====
Line 228:		Line 225:
	sendNielsenEvent('14',{type:"static",assetid:"static123",section:"sitesection",segA:"Segment1", segB:"Segment2",seg C:"Segment3"});		sendNielsenEvent('14',{type:"static",assetid:"static123",section:"sitesection",segA:"Segment1", segB:"Segment2",seg C:"Segment3"});
	</syntaxhighlight>		</syntaxhighlight>

	~~== Digital Audio ==~~
	~~=== What should a radio / audio app developer do during interrupt scenarios? ===~~
	~~Radio / audio app developer must trigger / stop the API calls during interrupt scenarios, as mentioned in [[Digital Measurement Interruption Scenarios]] section.~~

Admin at 23:47, 29 May 2019

2019-05-29T23:47:53Z

← Older revision		Revision as of 23:47, 29 May 2019
Line 144:		Line 144:
	</syntaxhighlight>		</syntaxhighlight>
	<blockquote>'''Note:''' DO NOT activate the Debug flag in production environment.</blockquote>		<blockquote>'''Note:''' DO NOT activate the Debug flag in production environment.</blockquote>

	==== We are currently using App SDK 3.2.1 (for iOS). What is the recommended way to switch to Adobe VHL Joint SDK without affecting our current implementation? (OR) How do I get tracking metrics for both Nielsen and Adobe? ====
	Adobe VHL Joint SDK component bundle contains Nielsen App SDK 4.0.0 which is capable of measuring all Nielsen measurement products like mTVR / DTVR, Digital Audio / Radio and DAR measurements along with Digital Content Ratings (DCR).

	Starting from Nielsen App SDK version 4.0.0, the SDK no longer uses shared instance and allows instantiating multiple instances of NielsenAppApi object and can be used simultaneously without any issues. Maximum of 4 SDK instances per appid are supported in the releases 4.0.0 and above.

	~~Perform [[these steps]] to implement Adobe VHL Joint SDK.~~

	==== We are currently using App SDK 4.0.0 (for iOS). What is the recommended way to switch to Adobe VHL Joint SDK without affecting our current implementation? (OR) How do we get tracking metrics for both Nielsen and Adobe? ====		==== We are currently using App SDK 4.0.0 (for iOS). What is the recommended way to switch to Adobe VHL Joint SDK without affecting our current implementation? (OR) How do we get tracking metrics for both Nielsen and Adobe? ====

Admin: Unix timestamp

2018-11-30T19:47:21Z

Unix timestamp

← Older revision		Revision as of 19:47, 30 November 2018
Line 10:		Line 10:
	Playhead position should be reported for both live streaming and VOD content streaming.		Playhead position should be reported for both live streaming and VOD content streaming.
	*For VOD content (not live) playing, playhead position must be number of seconds from the beginning of the content. This includes ads.		*For VOD content (not live) playing, playhead position must be number of seconds from the beginning of the content. This includes ads.
	*For live content playing, playhead position must be the current UTC ~~value~~.		*For live content playing, playhead position must be the current Unix timestamp (seconds since Jan-1-1970 UTC).

	==== How to send the Pause event in an Interactive radio station streams as it does not have a stop function? ====		==== How to send the Pause event in an Interactive radio station streams as it does not have a stop function? ====

LaMarHolmes: added DCR/DTVR actual wording to title

2018-07-11T22:24:15Z

added DCR/DTVR actual wording to title

← Older revision		Revision as of 22:24, 11 July 2018
Line 2:		Line 2:
	[[Category:Digital]]		[[Category:Digital]]

	== DCR/DTVR ==		== DCR/DTVR (Digital Content Ratings/Digital Television Ratings) ==
	=== SDK APIs ===		=== SDK APIs ===
	==== Should we call the [[play]] and [[stop]] methods whenever the user clicks on the pause/play button? ====		==== Should we call the [[play]] and [[stop]] methods whenever the user clicks on the pause/play button? ====

Admin at 13:19, 25 October 2017

2017-10-25T13:19:48Z

← Older revision		Revision as of 13:19, 25 October 2017
Line 178:		Line 178:
	+ "\"appVersion\" : \"" + "1.0" + "\","		+ "\"appVersion\" : \"" + "1.0" + "\","
	+ "\"sfcode\" : \"" + "uat-cert" + "\","		+ "\"sfcode\" : \"" + "uat-cert" + "\","
	+ "\"appid\" : \"" + "~~TXXXXXXXX~~-XXXX-XXXX-XXXX-XXXXXXXXXXXX"		+ "\"appid\" : \"" + "PXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
	+ "\""		+ "\""
	+ "}";		+ "}";

Admin at 15:04, 20 October 2017

2017-10-20T15:04:25Z

← Older revision		Revision as of 15:04, 20 October 2017
Line 132:		Line 132:

	=== iOS ===		=== iOS ===

	~~==== How to upgrade from pre-DCR to DCR? ====~~
	~~Please follow the [[Pre-DCR to DCR iOS Upgrade]] guide.~~

	==== Is there any debug facility to see if App SDK APIs are being called successfully? ====		==== Is there any debug facility to see if App SDK APIs are being called successfully? ====

Admin at 19:11, 7 August 2017

2017-08-07T19:11:43Z

← Older revision		Revision as of 19:11, 7 August 2017
Line 61:		Line 61:

	==== What are the possible types of play that can be sent? ====		==== What are the possible types of play that can be sent? ====
	~~‘Type~~' refers to the type of play event like preroll, midroll, postroll or ~~content~~.		'Type' refers to the type of play event like ''preroll'', ''midroll'', ''postroll'', ''content'', or ''static''.

	==== What values are typically passed for ChannelInfo? ====		==== What values are typically passed for ChannelInfo? ====

Admin2: /* SDK APIs */

2017-06-12T16:10:47Z

SDK APIs

← Older revision		Revision as of 16:10, 12 June 2017
Line 45:		Line 45:
	==== What should a video app developer do during interrupt scenarios? ====		==== What should a video app developer do during interrupt scenarios? ====
	Video app developer must trigger / stop the API calls during interrupt scenarios, as mentioned in [[Digital Measurement Interruption Scenarios]] section.		Video app developer must trigger / stop the API calls during interrupt scenarios, as mentioned in [[Digital Measurement Interruption Scenarios]] section.

	~~==== Can we always send stop(), then play(), loadMetadata() and setPlayheadPosition() even if it is brief buffering, as there is no way to predict the buffering time? ====~~
	For AppSDK (iOS and Android), do not call stop() and play() APIs in that sequence. Always call play() first and then call stop(), as play() starts a new viewing session and stop() stops the viewing session.
	*For brief buffering on all platforms, do not call stop() right away. Instead, stop sending the playheadPosition() / setPlayheadPosition() during the buffer time and start the playheadposition() / setPlayheadPosition() once the playback resumes. If there is a mechanism to know if buffering is crossing 30 sec or longer, then try to call stop() at that point.

	==== How to get the opt-out URL from App SDK? ====		==== How to get the opt-out URL from App SDK? ====