Adobe Analytics new report suite setup checklist

What this is

A report suite is the container that collects, stores, and reports one stream of Adobe Analytics data, created from the Admin Console by a system-level administrator. This card lists the creation fields, general account settings, IP obfuscation options, currencyCode behavior, success-event configuration, marketing channels, and processing rules, with the limits and ordering rules that make time zone and base currency effectively one-way doors once collection starts.

Create a report suite

Path: Analytics > Admin > Report Suites > Add Report Suite > Create Report Suite. Requires system-level administrator access granted via the Admin Console. Basis: a predefined template or an existing report suite — only settings are copied, not data.

Creation fields

Go Live Date and Estimated Page Views Per Day feed Adobe’s capacity approval.

General Account Settings

Path: Analytics > Admin > Report Suites > Edit Settings > General > General Account Settings. Covers Site Title, Base URL, Time Zone, Default Page, IP settings, Base currency, and more.

Filenames auto-stripped when Default Page is blank: index.htm, index.html, index.cgi, index.asp, default.htm, default.html, default.cgi, default.asp, home.htm, home.html, home.cgi, home.asp.

IP obfuscation and privacy

IP obfuscation is applied after Geo Lookup, Processing Rules, and IP Exclusions, so geo reports, processing rules, and IP exclusions still use the original IP. The obfuscated value is consistent for a given IP, so repeat visitors can be identified without revealing the real address.

Data processing order (relevant steps)

IP removal obfuscation is applied late, after other processing.

currencyCode

Success events

Path: Analytics > Admin > Report Suites > Edit Settings > Conversion > Success Events. Defined via the s.events variable.

Marketing channels

Path: Analytics > Admin > Report Suites > Edit Settings > Marketing Channels (Marketing Channel Manager). Two steps: (1) name/add channels, (2) create Marketing Channel Processing Rules. Adding channels is independent of creating rules.

Marketing channel processing rules

• Condition logic: If any / all of the following are true.
• Actions: Set Marketing Channel (identify the channel) and Set Marketing Channel Detail (the channel value).
• Condition types: Adobe-detected conditions (paid/natural search, internal URL, social referrers, conversational AI, first hit — no config), Hit attributes (dimension + operator + value), and Conversion variables (eVars 1 to 250).

Processing rules

Path: Analytics > Admin > Report Suites > Edit Settings > General > Processing Rules. Product admins have access by default; non-admins need a product profile that includes the Processing rules permission item.

Gotchas

1. Spike or gap in trended data → the report suite time zone was changed after go-live and Adobe re-anchors timestamps with no retroactive reprocessing → set the correct time zone at creation; if unavoidable, change during non-peak hours and annotate the changeover date.
2. A currency/revenue hit silently disappears → s.currencyCode was set to an invalid or misformatted value (not a valid 3-letter uppercase ISO code), so Adobe discards the whole hit → validate currencyCode on every revenue page/event, or leave it unset to inherit the base currency when there is only one currency.
3. Historical revenue looks inconsistent with new revenue → changing the base currency does not re-convert already-stored revenue → decide the base currency before go-live; treat any change as a reporting discontinuity and annotate the change date.
4. Direct or Internal channels steal conversion credit → Override Last-Touch Channel is enabled on the Direct/Internal channel and overwrites a persisting last-touch channel → leave Override Last-Touch Channel unchecked for Direct and Internal.
5. A processing rule blanks out both source and target variables → an Overwrite rule copied an empty source variable into the target → add a condition that verifies the source variable is set before using it to overwrite another variable.
6. An earlier rule’s value is missing in a later rule → rules execute sequentially, so once a variable is overwritten the original is gone for all later rules → order rules deliberately, capture originals before overwriting, and stay within the 150-rule / 30-condition limits.
7. The Analytics menu is grayed out; you cannot open Admin to create a suite → the account lacks system-level administrator access (or the Processing rules permission) → have a system administrator add you to a product profile with the required access.
8. Success events 81 to 1,000 do not populate although enabled → events 81 to 1,000 require H22 AppMeasurement code or higher → confirm the implementation is on H22 code or higher before relying on events above 80.

Quick recipes

// currencyCode does not persist between page views — set it on every page that reports revenue.
s.currencyCode = 'EUR';        // 3-letter UPPERCASE ISO code; an invalid code discards the whole hit
s.events = 'event1';           // success event enabled in Admin > Conversion > Success Events
s.products = ';SKU-1;1;49.99'; // value stored in the base currency, converted at the day's XE rate

// Only assign currencyCode from a validated value — a bad code discards the entire hit.
var code = dataLayer.currency;        // e.g. an unvalidated 'usd' from the data layer
if (/^[A-Z]{3}$/.test(code)) {
  s.currencyCode = code;              // valid: converts to the base currency at the day's rate
}
// else: leave s.currencyCode unset so the hit inherits the report suite base currency

Condition:  If all of the following are true
              eVar2  is set (is not empty)
Action:     Overwrite value of  eVar1  with  eVar2
# Rules run top to bottom and are not retroactive; the guard stops an empty eVar2 from wiping eVar1.

Condition:  If any of the following are true
              Adobe-detected: Paid Search
Action:     Set Marketing Channel         to  Paid Search
            Set Marketing Channel Detail  to  the tracking-code value
# Leave "Override Last-Touch Channel" UNCHECKED on Direct and Internal channels.

Condition:  (none — a rule with no condition runs on every hit)
Action:     Set event  to  event5
# Applies from save-time forward only; processing rules are never retroactive.

Related

• Hub: Adobe guides
• Lateral: Adobe Analytics implementation QA checklist · AppMeasurement to Web SDK migration

Sources

Official pages this card was read from (read 2026-07-20):

• Create a report suite (read 2026-07-20)
• New report suite settings (read 2026-07-20)
• General Account Settings (read 2026-07-20)
• Privacy overview (read 2026-07-20)
• Processing order for data in Adobe Analytics (read 2026-07-20)
• What is the currencyCode variable, and how do I use it? (read 2026-07-20)
• Success events overview (read 2026-07-20)
• Configure success events (read 2026-07-20)
• Manage marketing channels (read 2026-07-20)
• Processing rules for Marketing Channels (read 2026-07-20)
• Processing rules overview (read 2026-07-20)
• Processing rules interface (read 2026-07-20)