Adobe Analytics Developer Expert flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

KPI to variable mapping

Each KPI in the requirements document must map to a specific event or variable; an unmapped KPI is a requirements gap, not an implementation detail.

Report suite split rule

Split into separate report suites when data retention, currency, traffic volume, or legal jurisdiction differ; otherwise use one global suite with virtual report suites.

Requirements traceability matrix

A table linking requirement ID, KPI, variable or event, report, owner, and acceptance test, used to prove the design covers every requirement.

Acceptance criteria for QA

Each requirement needs a testable condition, such as an expected beacon value, so that QA can pass or fail the implementation objectively.

Data layer contract

A versioned, documented object with stable keys; page-scoped keys reset on navigation while persistent keys are merged across pages.

Rule sequencing in Tags

Rule execution order is not guaranteed across rules; use rule chaining via custom events when one rule must complete before another fires.

Tag environment promotion

Development, staging, and production use separate embed codes; publishing promotes a library build between environments, not individual rules.

Data element default value

A data element with no default returns undefined when its source is absent, which can break beacon construction or send empty variables.

Web SDK datastream mapping

The datastream ID connects the Edge Network to a report suite and to Adobe solutions; the org ID identifies the Experience Cloud organization.

sendEvent XDM requirement

Page views require web.webPageDetails.pageViews.value set to 1 and a valid eventType; context data travels in the separate data object.

Mobile lifecycle tracking

Registering the Mobile Core lifecycle extension automatically tracks launch, upgrade, and crash events, which map to Analytics metrics.

Track action versus track state

Track state implies a page or screen view and increments page views; track action records a non-page interaction without incrementing page views.

eVar allocation

Allocation decides which value receives credit: most recent, original value, linear, or participation; changing it retroactively can lose attribution history.

eVar expiration

Expiration sets persistence beyond the hit: visit, page view, event, or a fixed period; it interacts with allocation to determine attribution.

Merchandising eVar syntax

A merchandising eVar binds a value to a product within the same hit using product syntax, and requires product syntax to be enabled.

Processing rule limits

Processing rules run at collection time and can set, copy, or delete values, but cannot create new variables or change a variable's type.

Numeric event syntax

A numeric or currency event sets its value inline, for example s.events = 'event2=10.00'; event1 is a simple counter with no value.

Products string position

The products string uses semicolon-delimited positions: category, product, quantity, price, merchandising eVars, currency; position must be preserved.

s.t versus s.tl

s.t() sends a page view hit; s.tl() sends a link or action hit and requires a link type argument of o, d, or e.

Context data mapping

Context data uses the c. prefix and becomes reportable only after a processing rule or context data mapping assigns it to a prop or eVar.

Data Sources deduplication

Data Sources uploads require a unique transaction ID; without it, re-uploading the same file double-counts metrics in the report suite.

Full versus incremental upload

Incremental Data Sources uploads append rows to existing data; full uploads replace the data for the specified date range.

Classification import key

A classification import needs a key column matching the variable value plus attribute columns; a schema mismatch fails validation.

Analytics source connector

The Experience Platform source connector mirrors Analytics report data into a dataset, which Customer Journey Analytics can then query.

Beacon validation checklist

Confirm pageName is set, eVar and prop values are populated, events count once, products syntax is valid, and no undefined strings appear.

Edge trace debugging

The Edge trace shows the raw XDM payload and the mapped Analytics hit, revealing mapping or schema errors before they reach reports.

Duplicate hit diagnosis

Count beacons per page load against expected s.t() calls; extra hits usually come from rules firing twice or a data layer event repeating.

Data element timing failure

A rule that reads a data element before the data layer populates sends empty values; fix by firing on a custom event pushed after the update.

PII collection rule

Never send email, name, phone, or free-text fields into props or eVars; hashing does not make a direct identifier safe to collect.

Consent gating

Consent state must resolve before any tag rule fires; the SDK holds or drops beacons according to the configured consent categories.

IP obfuscation setting

IP obfuscation is a report-suite setting that removes the last octet of the IP address before the data is stored.

New variable governance gate

Every new eVar or prop requires a documented owner, purpose, retention period, and data classification before it is enabled in production.