-
Notifications
You must be signed in to change notification settings - Fork 11
Add nielsen docs #549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Add nielsen docs #549
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| --- | ||
| sidebar_position: 11 | ||
| --- | ||
|
|
||
| # Nielsen audience tracking | ||
|
|
||
| Nielsen is an industry-standard audience measurement system that tracks viewership data across media platforms. By embedding Nielsen markers in your audio stream, you can measure and report on your live audience in real time, providing actionable insights into viewer engagement and reach. | ||
|
|
||
| This guide explains how to enable Nielsen audience tracking on your streams in a few simple steps. | ||
|
|
||
| 1. Ensure that your ingest stream contains the Nielsen markers in your audio. This is crucial for our transcoder to pick them up and process them. | ||
|
|
||
| 2. The next step is enabling the feature when creating your channel like this: | ||
|  | ||
|
|
||
| That is all the backend configuration work that is required. This will make sure your markers are converted to the correct ID3 messages that a player can then read and report back to Nielsen. | ||
|
|
||
| 3. The final step is enabling Nielsen on your player. For THEOplayer on web for example, you can find the steps in our [guide to integrating Nielsen on Web](/theoplayer/connectors/web/nielsen). | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Broken link to non-existent Nielsen web connector guide
The link
[guide to integrating Nielsen on Web](/theoplayer/connectors/web/nielsen)points to a page that does not exist in the repository. Thetheoplayer/connectors/web/directory only containsindex.mdx— there is nonielsen.mdornielsen.mdxfile. This will result in a 404 for readers clicking the link.Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is untrue, the link works