Last updated
Visualization workbench
Edit example rows, then follow channel, page, and event. Every record here is invented. It is not GA4, not site traffic, and not the D3 lab. Live device readings stay on that other page.
Why you'd want to
An in-memory example table groups by channel, then page, then event, and a timer can count visibility in component state. The rows are invented, and this section sends no event of its own.
How to use it
Demo metrics are off. Off until you check it. It counts chart selections, how long a panel stayed visible, and how long the chart took to update. It does not read what you type, and it does not leave this page.
All example channels
Choose a bar to drill down. Counts are the example numbers you can edit.
Example visitor builder
8 valid visitor rows are in the chart for this scope. Empty counts stay empty. Invalid rows stay in the table and out of the bars.
| Channel · text | Page · text | Event · text | Count · raw | Minute · raw | Share · calculated | |
|---|---|---|---|---|---|---|
| 35% | ||||||
| 5% | ||||||
| 19% | ||||||
| 16% | ||||||
| 10% | ||||||
| 6% | ||||||
| 8% | ||||||
| 2% |
Working in this mockup: the visitor drill-down and the walk speed bars. Not built here, so there is no control for them: a heatmap, a geographic map, and a separate flow diagram. Share and pace are calculated on this page from the cells. Nothing is uploaded, stored, or put in the address.
Example vendor setup is marked below. eVar and event numbers are examples. This lab does not call Adobe.
The visualization workbench groups an in-memory example table by channel, then page, then event, and it can time visibility in component state. The section ignores click tracking, sends no event of its own, and does not call Adobe.
Keep the rows in memory
EXAMPLE_VISITORS and EXAMPLE_WALK_ROWS are the starting tables. Edits stay in React state. visitorIssues and walkIssues reject a bad channel, path, event, or number before a row can enter a total.
Group one level at a time
groupsFor filters with rowsInScope, then buckets by channel, page, or event. A numeric count is added. An empty count increments missing and does not become a zero that was typed.
Drill without leaving the page
drillInto sets channel, then page, then event. scopeBack removes the deepest key. pickBar stops once the event level is set.
Count demo metrics only while they are on
applyMetric returns the same state when disabled. Otherwise it adds an interaction, adds visible milliseconds, or stores the last update time. Hiding the tab turns the switch off. The section is data-track-ignore, so those clicks are not recorded as click events.
One level of the example table. Empty counts are missing, not a fabricated zero.
export function groupsFor(rows: VisitorDraft[], scope: Scope): BarGroup[] {
const scoped = rowsInScope(rows, scope)
const level = !scope.channel ? "channel" : !scope.page ? "page" : "event"
const buckets = new Map<string, BarGroup>()
for (const row of scoped) {
const key = row[level]
const current = buckets.get(key) ?? { key, total: 0, missing: 0 }
const count = parseNumber(row.count)
if (typeof count !== "number") {
if (count == null) current.missing += 1
buckets.set(key, current)
continue
}
current.total += count
buckets.set(key, current)
}
return [...buckets.values()]
}Demo metrics stay in memory. Disabled collection returns the previous state.
export function applyMetric(
state: MetricState,
enabled: boolean,
event: { type: "interaction" } | { type: "visible"; ms: number } | { type: "update"; ms: number },
): MetricState {
if (!enabled) return state
if (event.type === "interaction") return { ...state, interactions: state.interactions + 1 }
if (event.type === "visible") return { ...state, visibleMs: state.visibleMs + event.ms }
return { ...state, lastUpdateMs: event.ms }
}This lab does not queue its own event. The Google block shows an example of how you would track the interaction. Adobe is an example too.
This lab does not queue an analytics event of its own. After Accept, the site still queues virtual_page_view for the page, with page_path and page_title. Clicks inside a data-track-ignore region are not recorded. The push below is an example, not a call this page makes. This site does not call gtag('set') or Adobe.
Example only. This page does not push this object.
// Example only. This lab does not queue this event.
dataLayer.push({
event: "chart_drill_example",
level: "channel",
key: "Organic",
})Example implementation. This site does not call Adobe. eVar114, prop114, and event114 are example variable numbers. In Launch, a data element reads the value and a rule sends it when the value changes. In the report suite, enable eVar114 with Most Recent allocation and expire it on the hit. A processing rule is unnecessary if the data element maps straight to that eVar.
Example alloy payload. _example is a placeholder schema, not a real tenant.
alloy("sendEvent", {
xdm: {
eventType: "web.webinteraction.linkClicks",
_example: {
drillKey: "Organic",
},
},
})Example hit. eVar114 is hit-scoped in this example. prop114 dies at the same hit.
s.eVar114 = "Organic"
s.prop114 = "Organic"
s.events = "event114"
s.linkTrackVars = "eVar114,prop114,events"
s.linkTrackEvents = "event114"
s.tl(true, "o", "chart_drill_example")Each lab field, the GA4 name, and the example Adobe variable. Scope is the part that usually gets lost in the translation.
Drill key
GA4. Not sent. Channel, page, and event stay in component state.
Adobe. Example eVar114, expire on the hit. Not sent.
Scope. Hit, if you tracked the bar. It is not a user property.
Bar total
GA4. Not sent. The total is the sum of example counts.
Adobe. Example prop114. Do not write the total into a prop. Not sent.
Scope. A calculated example. It is not a hit metric and not a visit property.
Visible time
GA4. Not sent. applyMetric keeps milliseconds in memory.
Adobe. Example eVar114. Not sent.
Scope. Local state. It is not an event and not a user property.
Interaction count
GA4. Not sent. The overlay says the numbers are demo metrics.
Adobe. Example prop114. Not sent.
Scope. In-memory state for this view. It is not a visit event.
Funnel drop-off analysis across visit, lab page, white paper, and lead for the last 28 days, with device and source filters. Counts come from stored events.
Cohort retention analysis by Monday-start week. Each cell is that group share with a later page view. A free table built from stored first visits.
The body of one page view, the gate it has to pass, and the record that comes back.