Nielsen DTVR Destination

Segment makes it easy to send your data to Nielsen DTVR (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Nielsen DTVR in the format they understand. Learn more about how to use Nielsen DTVR with Segment.

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.

This destination requires a Device-based Connection Mode for Mobile data. Follow the steps above to ensure you have packaged the Nielsen DTVR SDK with Segment’s.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.


Enter your Nielsen DCR App ID.

Enable Debug Mode

Check this setting if you would like to activate the Debug flag. Once the flag is active, it logs each API call made and the data passed. Note: DO NOT: activate the Debug flag in a production environment.


Indicate the key in your payload associated with the id3 tag. If one is not provided we will default to id3

Instance Name

Required for Web only: A user-defined string value for describing the player/site.

Events to Send Id3 Tags

Add the event names you would like to trigger Segment to sendId3 tags.


Required for mobile only: Add the unique identifier for the environment that the Nielsen SDK should point to. For production applications, please enter the value “us”.

Questions? Need help? Contact us!
Can we improve this doc?
Email us:!