Last updated
Pathing and LCP
Example pathing. Not this site's traffic. A few thousand invented sessions across 40 pages. Link thickness is sessions. Color is LCP: green is good, amber needs improvement, red is poor.
Why you'd want to
The tree is a few thousand invented sessions across 40 pages, from a fixed seed. It does not read this browser, and it does not send those rows to Google or Adobe.
How to use it
Scroll sideways on a small screen. Enter opens the focused node.
Example vendor setup is marked below. eVar and event numbers are examples. This lab does not call Adobe.
The D3 lab draws an invented tidy tree of visits. Sessions, paths, and LCP numbers come from a fixed seed in the repo. The tree does not read this browser and does not send those rows to Google or Adobe.
Build a stable example log
exampleSessions walks a template path for each source and delivery. The same seed always produces the same sessions. The page says the rows are not this site's traffic.
Fold sessions into a tree
pathTree keeps one source and one delivery, then absorbs each path. nodeFrom shows the three busiest children at each level and rolls the rest into Other.
Open a page from the branch you tapped
The page card and the metric rows use the same arrival as the node. A node with 20 sessions does not open a card of every visit that ever touched that URL.
Give each metric its own columns
LCP rows name the element, the device, and the cache status. Conversion rows name the type and the value. Exit rows name the exit page and the next action.
Leave the example on the page
The lab section is marked data-track-ignore, so a click on a node is not recorded as a click event. Nothing in this file calls trackLabEvent.
One source and one delivery become the tree. Other children past the top three are collapsed.
export function pathTree(source: SourceId, delivery: Delivery, depth: number) {
const root = makeBucket(source, sourceLabel(source), "source")
for (const session of exampleSessions()) {
if (session.source !== source || session.delivery !== delivery) continue
absorb(root, session, session.path, 0)
}
return nodeFrom(root, depth, 3)
}The lab root ignores click tracking. The example sessions stay in the browser.
export function D3Lab() {
return (
<section className="mx-auto w-full min-w-0 max-w-[90rem] px-4 py-8 sm:py-10" data-d3-lab data-track-ignore>
<PathTreeLab />
</section>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: "path_node_open",
page_id: "/lab/d3",
source: "example",
delivery: "cdn",
})Example implementation. This site does not call Adobe. eVar31, prop31, and event31 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 eVar31 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: {
pathNode: "example-source",
},
},
})Example hit. eVar31 is hit-scoped in this example. prop31 dies at the same hit.
s.eVar31 = "example-source"
s.prop31 = "example-source"
s.events = "event31"
s.linkTrackVars = "eVar31,prop31,events"
s.linkTrackEvents = "event31"
s.tl(true, "o", "path_node_open")Each lab field, the GA4 name, and the example Adobe variable. Scope is the part that usually gets lost in the translation.
Entry source
GA4. Not sent. An example event parameter would be source on path_node_open.
Adobe. Example eVar31, Most Recent, expire on the hit.
Scope. Hit. A source on the user would outlive this invented session.
Page in the path
GA4. Not sent. The ordinary virtual_page_view for /lab/d3 is a different event and does not list the example path.
Adobe. Example prop31, which dies at the hit.
Scope. Hit. The tree's page is not the GA4 page_path of this screen.
CDN or origin
GA4. Not sent.
Adobe. Example eVar32, expire on the hit.
Scope. Hit. The toggle is a view state, not a user property.
LCP milliseconds
GA4. Not sent. GA4 already collects its own LCP when the tag is allowed. These numbers are the example seed.
Adobe. Example event31 if you counted an example view. Do not copy the seed into a metric.
Scope. Event. A user-scoped LCP would mix later pages into one number.
Visualization workbench: an example table, calculated fields, and a channel, page, and event drill-down. The rows are invented, not real traffic.
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.
The body of one page view, the gate it has to pass, and the record that comes back.