Pod name

This page covers the Pod name reporting dimension. See Ad break name for how to collect this variable.

The Pod name dimension reports the friendly name of each ad break (for example, "pre-roll", "mid-roll-1"). In Customer Journey Analytics it is a discrete dimension populated directly from the implementation variable. In Adobe Analytics it is available through two approaches: a classification of the Ad pod dimension, or an eVar populated using a processing rule.

How this dimension is populated

Pod name is sourced from the Ad break name value the player sets on ad break start.

Reporting system
Source
Adobe Analytics (processing rule)
Create a Processing rule that maps a.media.ad.podFriendlyName to an eVar.
Adobe Analytics (classification)
Classification of the Ad pod dimension — Adobe automatically creates this classification when Media Ads is enabled for the report suite. You are responsible for populating and maintaining classification values.
Customer Journey Analytics
mediaReporting.advertisingPodDetails.friendlyName
Data feeds (processing rule)
evar1-evar250, post_evar1-post_evar250 (the eVar that your processing rule maps a.media.ad.podFriendlyName to)
Data feeds (classification)
N/A — Data feeds do not support classifications.
Audience Manager
c_contextdata.a.media.ad.podFriendlyName

Classification approach

Adobe creates the Pod name classification structure automatically when Media Ads is enabled for the report suite. You are responsible for populating and maintaining the classification using Classification sets.

This approach provides a guaranteed 1:1 relationship between each pod ID and its friendly name. Classification updates apply retroactively across all historical data for that ID.

IMPORTANT
Do not change the Pod name classification name. Renaming it can cause Adobe to recreate the original classification, resulting in a duplicate.

Processing rule approach

Create a Processing rule that maps a.media.ad.podFriendlyName to an eVar. This approach captures the friendly name as a per-hit value without requiring classification maintenance.

The trade-off is that you lose the guaranteed 1:1 relationship between the pod name and the parent Ad pod dimension. If your implementation sends inconsistent values for the same pod ID across events, multiple names can appear under the same ad pod. Updating a value only applies to data moving forward.

Dimension items

Each item is the literal ad break name reported on ad break start.

recommendation-more-help
media-analytics-help