Browser Metadata: Difference between revisions
From Engineering Client Portal
ColinBrown (talk | contribs) (Blanked the page) |
ColinBrown (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
=== Configure Metadata === | |||
Map the Nielsen keys to variables so that the content metadata is dynamically updated. | |||
The Nielsen reserved keys are: | |||
{| class="wikitable" | |||
|- | |||
! Key !! Description !! Data Type !! Value !! Required? | |||
|- | |||
| type || asset type || fixed || <code>'static'</code> || Yes | |||
|- | |||
| assetid || Unique ID for each article || dynamic || custom <br>(no [[Special Characters]]) || Yes | |||
|- | |||
| section || section of each site (e.g. section value should be first level in page URL: website.com/section). Limit to 25 unique values || dynamic || custom || Yes | |||
|- | |||
| segA || custom segment for reporting: Limit to 25 unique values across custom segments (segA + segB + segC) || dynamic || custom || No | |||
|- | |||
| segB || custom segment for reporting: Limit to 25 unique values across custom segments (segA + segB + segC) || dynamic || custom || No | |||
|- | |||
| segC || custom segment for reporting: Limit to 25 unique values across custom segments (segA + segB + segC) || dynamic || custom || No | |||
|} | |||
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) | |||
|} | |||
Revision as of 00:55, 31 July 2019
Configure Metadata
Map the Nielsen keys to variables so that the content metadata is dynamically updated.
The Nielsen reserved keys are:
| Key | Description | Data Type | Value | Required? |
|---|---|---|---|---|
| type | asset type | fixed | 'static' |
Yes |
| assetid | Unique ID for each article | dynamic | custom (no Special Characters) |
Yes |
| section | section of each site (e.g. section value should be first level in page URL: website.com/section). Limit to 25 unique values | dynamic | custom | Yes |
| segA | custom segment for reporting: Limit to 25 unique values across custom segments (segA + segB + segC) | dynamic | custom | No |
| segB | custom segment for reporting: Limit to 25 unique values across custom segments (segA + segB + segC) | dynamic | custom | No |
| segC | custom segment for reporting: Limit to 25 unique values across custom segments (segA + segB + segC) | dynamic | custom | No |
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:
| 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) |