Browse the help center

Analytics dimensions reference

Every group-by dimension and filter per report type, and what each one does.

Reference network manager publisher advertiser Account → Analytics → Group by / Filters

Every Group by dimension and Filter of every report type, and what each one does. For the metric columns see Analytics metrics; for choosing a report type see Report types.

The report-type picker (General, Advanced, Impressions Log, Clicks Log, Conversions Log, Targeting Cookie, Header Bidding) decides which dimensions a report offers; see Per report type. Values that look like dimensions but cannot be selected are listed in Values that are not dimensions.

Each dimension is switched on per role by a Group/Filter By permission named after it, plus view access to its side — inventory for supply dimensions, campaigns for demand ones. One permission usually covers both the Group-by entry and the matching filter.

The entity dimensions nest, and so do their permissions: a role needs Zone to report by zone and both Zone and Placement to report by placement, Campaign to report by campaign and both Campaign and Banner to report by creative — each on top of Site or Advertiser for its side. Granting only the shallower one is how you give a role site-level or campaign-level figures without the detail underneath: the filter tree then stops at that depth rather than offering a level the report would refuse. A refusal names the shallowest permission that is missing. For who can grant what, see Users and roles.

Entity dimensions (General and Advanced)

  • Supply side: Site, OpenRTB Publisher ID, Zone, Placement, Placement Size, Placement Label.
  • Demand side: Advertiser, Campaign, Banner, Banner Label, ISCI / Ad-ID, Banner Template.
  • ISCI / Ad-ID is General only. Placement Label, Banner Label and Banner Template are group + filter on both reports.

Non-entity dimensions shared by General and Advanced: Channel, Country, Country Group, Conversion Action and Placement Type. Attribution Type, Advertiser Owner and Site Owner are General only and group-by only.

Note: Conversion Action and Attribution Type also need the Conversions column permission. Without it, granting the action dimension does nothing.

Note: Attribution Type groups conversion rows by how each conversion was attributed. Its values are Unattributed, Post-click, Post-view, Post-click (expired), Post-view (expired) and System — see the conversion attribution overview. The two (expired) buckets are zero-revenue diagnostics excluded from conversion totals. System rows (VAST playback and viewability events) are kept in the data, so grouping by Conversion Action or Attribution Type shows them, but they are not counted in the Conversions column and their money still counts. The Advanced report has no attribution dimension.

Note: OpenRTB Publisher ID is the identifier Epom puts into site.publisher.id / app.publisher.id on outgoing bid requests — the same value shown read-only on the site’s edit page. Use it to line your rows up against a DSP partner’s own report, which identifies your inventory by that number rather than by site name. There is one publisher ID per site, so grouping by it returns the same rows as grouping by Site, relabelled. Its permission ships disabled. Offered on General and Advanced; the raw logs do not carry it.

Corner case: Country Group vanishes entirely when the network has no Custom Country Groups configured. On a network that does have them, ungrouped countries fall into Ungrouped Countries. It comes with the Country permission.

Note: ISCI / Ad-ID groups delivery by the spot code set on video banners (see Video banners). Banners that share a code add up into one row, and banners without one fall into a single empty row. The code is read from the banner when the report runs, not stored per impression, so editing it re-labels past delivery. Where banner names are masked for you, the code is masked too. As a filter it works on General and on the Impressions, Clicks and Conversions logs, and lists the codes on the banners you can report on. The logs match a code through the banners that carry it now, so a code moved to another banner filters that banner’s whole history. The logs also show it as a column. Its permission ships disabled for every role.

Note: Banner Template groups delivery by the template each banner is built from, and banners built from no template add up into a single empty row. Both reports read the template a banner has now — the Advanced report’s logs record only the banner — so moving a banner to another template moves its whole history with it, deleting a template moves its banners’ history into the empty row, and the filter keeps the banners on the chosen templates today. On the Advanced report that empty row also counts the ad requests no banner answered, except on a network whose Advanced report runs on compacted logs, which leaves those requests out as it does for Banner. Grouping and filtering by it take the same two permissions: the view of the campaigns and Analytics Report Group/Filter By Banner Template; a report filtered by it without them is refused, as one grouped by it is.

Note: the Advanced report’s logs carry neither labels nor templates, so it reads a Placement Label or Banner Label filter, and a Banner Template filter or grouping, as the placements or banners carrying them now — only those the report’s own filters let through (Site, OpenRTB Publisher ID, Zone, Placement and the sites shared with you for placements; Advertiser, Campaign, Banner, Banner Label and the advertisers shared with you for banners) and that were created by the period’s last day. When one of them comes to more than the network’s limit — 20,000 unless your administrator changed it — the report is refused with a message asking you to narrow it; it is never cut short.

Corner case: the Advanced report’s logs keep the site, zone and campaign a placement or banner served under, but its labels and template are read through where it is now. Filtered by a Site, Zone, Campaign or Advertiser, the traffic a placement or banner had there before it was moved elsewhere is left out by a label or Banner Template filter, as the General report leaves it out, and counts in the empty row of a Banner Template grouping.

Note: Placement Type groups delivery by the kind of placement it ran on — Site Placement, Mobile Site Placement, Video Placement, Application Placement and so on — and names each row by the type in your interface language. The General report reads the type each placement has now; the Advanced report reads the type recorded with every event, and an event recorded without one (a placement the ad server could not resolve) adds up into a single empty row. On a network whose Advanced report runs on compacted logs it is not offered (see below). Grouping and filtering by it take the Analytics Report Group/Filter By Placement Type permission and nothing else: it names no site or placement, so a role without inventory access can use it too. The filter takes the type ids — 1 Site, 2 Mobile Site, 3 Video, 4 Non-standard, 5 Application, 6 Email, 7 Click-through, 9 Native.

Corner case: turning off Site also removes OpenRTB Publisher ID, Zone, Placement and Placement Label; turning off Advertiser also removes Campaign, Banner, Banner Label and ISCI / Ad-ID — even if their own permissions stay on.

Advanced-only dimensions

The Advanced report adds these dimensions on top of the entity set:

  • Browser, Browser Version, Operating System, OS Version — the visitor’s browser and operating system.
  • Browser Country, Language, Accept-Language, Time Zone Name, Location — what the visitor’s browser reports about locale and position.
  • Connection Type, Mobile Carrier, Proxy — the network the request came over.
  • Device format, Device Vendor, Device Model, Device Model Code, Device Release Year, Device RAM, Screen size, Price Band — the device.
  • Browser Rank, Hardware Rank, Platform Rank — device-quality rankings.
  • Is Web App, Incognito Mode — how the page was opened.
  • Risk Level, Risk Category — traffic-quality scoring.
  • Referer, Top Domain, Package Name — where the request came from.
  • Custom parameter — expands into a name and a value column.
  • Traffic Source — the integration the request arrived through.

Browser Version, OS Version, Accept-Language, Time Zone Name, Location, Screen size, Package Name and Custom parameter are available to anyone who can run Advanced reports, so they cannot be withheld from a role. Every other dimension in this list has a permission of its own: without it the dimension is hidden from the picker, and a saved report or a REST call that groups or filters by it is refused. The Custom parameter breakdown columns need the Custom Parameters column permission.

Corner case: Traffic Source names the integration a request arrived through rather than anything about the user. Today it has one value, HEADER_BIDDING, written for traffic answered by the header-bidding bid endpoint; an empty cell means the ordinary ad tag. Its permission is off for every role on upgrade. The compacted logs do not carry it, so on a network with compacted logs it is stripped from Group by (below) and a filter on it matches nothing — check with Epom support or your account manager before building a saved report on it there. Bid and no-bid counts — and so a win rate — come from ad-request records, so they need the ad-request event to be logged on that network; see Header bidding.

Compacted logs: dimensions that lose their group-by

On a network whose Advanced report runs on compacted logs, a fixed set of Advanced dimensions is removed from Group by but still accepted as filters. Twenty are always stripped:

Mobile Carrier · Connection Type · Language · Accept-Language · Time Zone Name · Browser Country · Traffic Source · Incognito Mode · Is Web App · Demand Site Platform · Placement Size · Placement Type · Device format · Proxy · Device Release Year · Device Vendor · Device Model · Device Model Code · Risk Level · Risk Category

Corner case: some networks’ compacted logs strip more on top of that list — Referer, Package Name, Top Domain, Custom parameter, Browser Version, OS Version, Location, Screen size, Device RAM, Price Band, the three Rank dimensions, and even Placement Label and Banner Label. So two networks on the same release can offer different Advanced Group-by lists. If a dimension you expect is missing and is not in the twenty above, ask Epom support or your account manager which dimensions your network’s compacted logs keep.

Corner case: the form still accepts filters on stripped dimensions, but a value the compacted logs never kept cannot match anything. Traffic Source is absent from compacted logs entirely, so a filter on it returns no rows.

Per report type

The picker offers General plus up to six more types: Advanced, Impressions Log, Clicks Log, Conversions Log, Targeting Cookie and Header Bidding. Impressions Log and Clicks Log share a column below because they carry the same attributes.

Dimension groupGeneralAdvancedImpressions / Clicks LogConversions LogTargeting CookieHeader Bidding
Entity trees (site…placement, advertiser…banner)group + filtergroup + filtercolumn + filtercolumn + filter—group + filter (site, zone, placement only)
Channelgroup + filtergroup + filtercolumn + filtercolumn + filter——
Countrygroup + filtergroup + filtercolumn + filtercolumn + filtergroupgroup + filter
Country Groupgroup + filtergroup + filter————
Placement Label, Banner Labelgroup + filtergroup + filter————
Banner Templategroup + filtergroup + filter————
Placement Sizegroup + filtergroup + filter————
Placement Typegroup + filtergroup + filter————
ISCI / Ad-IDgroup + filter—column + filtercolumn + filter——
Conversion Actiongroup + filtergroup + filter—column + filter——
Attribution Typegroup——column——
Advertiser / Site Ownergroup—————
Browser, OS—group + filtercolumn onlycolumn only——
Browser Country—group + filter————
Browser Version, OS Version, Mobile Carrier, Accept-Language, Location—group onlycolumn only———
Time Zone Name, Screen size, Top Domain—group only————
Referer, Package Name, Custom parameter—group + free-text filter (Ref.domain, Package, custom parameter name / value)column (custom parameter only)column (custom parameter only)——
Device Vendor / Model / Model Code / Release Year / RAM, Price Band, the three Ranks, Device format, Proxy, Is Web App—group + filtercolumn only———
Risk Level, Risk Category, Connection Type, Language, Incognito Mode—group + filtercolumn + filter———
Traffic Source—group + filtercolumn + filter———
Fill Source—————group + filter
Cookie name / value————column—
Validation (valid / invalid records)——filterfilter——

Notes:

  • The log types are event lists — they have no Group by at all, only filters. Their per-event attributes are described as column above and listed in Analytics metrics.
  • A log column is not always a log filter. The Impressions and Clicks Log show Browser, OS, Browser Version, OS Version, Mobile Carrier, Accept-Language, Device format, Proxy, Device Release Year, Device RAM, Price Band, Is Web App, the three Rank columns, Device Vendor / Model / Model Code and Location as columns you can read but cannot filter on. The only device- and quality-side filters the raw logs accept are Risk Level, Risk Category, Connection Type, Language, Incognito Mode and Traffic Source. To filter on Browser or OS, use the Advanced report.
  • The Custom parameter filter takes one row per parameter. Each row is a parameter name and the values it may hold: several values of one parameter count a request holding any of them, and a row left without a value counts every request that carried the parameter, whatever its value. On a parameter registered as a list, a value counts a request holding it as any one of its items (18+ counts ~other,18+); grouping still shows the whole value. Two or more rows narrow each other — a request has to carry all of them — and a switch under the rows asks for any of these instead. Grouping by Custom parameter reports one row per parameter a request actually carried, so a request holding only the first of the filtered parameters does not also produce an empty row under the second.
  • Entity filters on the raw logs are OR’d within a side and AND’d between them: Advertiser, Campaign and Banner are one OR group; Site, Zone and Placement are another. Two demand filters therefore widen the result, while a demand filter plus a supply filter narrows it.
  • Header Bidding groups by Fill Source, Country, Site, Zone and Placement, and nothing else. None of the demand-side dimensions are offered, and the filters are the same five plus the date range (no Channel, no advertiser tree).
  • Fill Source names who filled the round. It exists only on the Header Bidding report and comes with that report type. Its values are Direct campaigns (a campaign booked here won the round), Ad server (GAM) (a line item in the publisher’s own ad server filled it), AdX / AdSense (Google’s own demand outbid everyone), Unfilled (nobody took the slot), and one value per partner bidder code — shown under the bidder’s catalogue name, or under the alias itself when the tag uses one. A bidder renamed in the Prebid registry is relabelled across its whole history.
  • Targeting Cookie always aggregates by cookie name and value; Country is its single optional group-by dimension. The report has no Country filter, only the cookie name and value fragments.
  • The Validation filter appears on log types only when the network stores invalid (filtered) records alongside valid ones.

Report types other than General can only be granted by your network administrator. Targeting Cookie appears only when cookie logging is on for the network, whatever the role holds. The three log types also need view access to all inventory and all campaigns. Advanced appears only when Advanced analytics is set up for the network; Header Bidding ships disabled for every role.

Time granularity

The Time granularity selector is a separate axis; each option except None is switched on per role.

24 Hours shifts the day boundary to an hour you choose, so a “day” runs from that hour to the same hour next day.

Report typeOptions offered
GeneralNone, Hour, Day, Week, Month, Year, 24 Hours
AdvancedNone, Hour, Day, 24 Hours
Header BiddingNone, Hour, Day, Week, Month, Year
Targeting CookieNone, Day, Week
Impressions / Clicks / Conversions Logcontrol hidden — event lists have no time grouping

Corner case: the Advanced report offers no Week, Month or Year granularity. A monthly Advanced report has to be run as a date range with granularity None, or assembled from daily rows.

Date-range presets

Fourteen presets, each switched on per role:

Today · Yesterday · Current week · Last week · Last 2 weeks · Current month · Last 7 days · Last 30 days · Last month · Last 3 months · Last 6 months · Current year · Last year · Custom range

A preset your role lacks is shown greyed out in the new UI and omitted on the legacy page.

In a General report the presets are days of the network’s time zone (UTC unless your network has been set to another zone) and a week runs Monday to Sunday; an Advanced report counts them in its own Time zone. Last 7 days and Last 30 days include today.

Labels: Group by and Filters can name the same dimension differently

The Group-by picker and the filter menu do not always use the same wording for one dimension. Where they differ, this is what each says (English):

DimensionIn Group byIn Filters
Conversion ActionConversion ActionConversion Action Filter
Device VendorDevice VendorDevice vendor
Device ModelDevice ModelDevice model
Device Model CodeDevice Model CodeDevice model code
Device Release YearDevice Release YearDevice release year
Price BandPrice BandPrice band
Browser Rank, Hardware Rank, Platform Rank… Rank… rank (lower case)

Every other dimension uses the same label in both places. Two filter boxes have no Group by twin of the same name: Ref.domain is a free-text match against the referer (the Referer dimension), and there is no filter at all for Top Domain. The Package Name filter is a free-text match on the package name.

Values that are not dimensions

Some values you may meet in report output, saved reports or the API are not offered as group-by dimensions of the General or Advanced report:

ValueWhat it is
Placement Id, Zone Id, Site Id, Banner Id, Campaign Id, Advertiser Id, Action IdID columns shown beside their name column when Show IDs is on in report layout settings; never separately selectable.
Custom parameter name, Custom parameter valueThe two output columns the Custom parameter dimension expands into.
Risk ScoreA metric — see Analytics metrics. Risk Level and Risk Category are its dimension counterparts.
StatusA metric column (revenue confirmation status).
Demand Site PlatformNot offered in any report type.
Time zoneAn older timezone value distinct from Time Zone Name; not offered in any report type.
Fill SourceOffered by the Header Bidding report only.
Actions LogA report type that is not offered in the picker and cannot be run from the UI.

Masking

Entity dimensions respect sharing: rows for entities the user cannot view render as TYPE_id (e.g. SITE_45, CAMPAIGN_123) instead of the name. A role that can view all inventory or all campaigns sees every name unless it also holds Mask Inventory / Mask Campaigns; with the mask on, only entities shared with the user (owner, Can edit or Can view) keep their name, and the rest show as ids.

Related pages

Please disable Adblock
Are you using adblock? Disable it and reload the page to proceed to the destination page.

A registration has already been submitted from this page. Please try again in 10 minutes.