Advanced architecture
Vitals and behavior
A slow page and a quiet page are different problems. This lab joins example LCP, INP, and CLS to an example engagement rate so you can see the two side by side. Filter the rows. They are not field data from this site.
Example data, not real traffic.
A live join would read CrUX or the site's own RUM plus consented engagement. Those sources are not queried here.
Understanding the labHow to use it and why you'd want to
Why you'd want to
You want speed and engagement on the same row before you blame the page. Every number is an example, so filter to one path and read both sides.
How to use it
- Read LCP, INP, CLS, and engagement.
- Filter the table by a path.
- Keep the example label in view.
Loading the lab…
WalkthroughHow we built itShowHide
Example vendor setup is marked below. eVar and event numbers are examples. This lab does not call Adobe.
EXAMPLE_VITALS is a fixed list of LCP, INP, CLS, and an engagement rate. filterVitals keeps rows whose path contains the query. The page labels the table as example data.
Keep the rows in the module
Five paths are written in EXAMPLE_VITALS. They are not read from CrUX or from the database.
Filter by path
filterVitals lowercases the query and keeps rows whose page includes it.
Draw both axes
The chart maps LCP to x and engagement to y so a slow row and a quiet row are visible together.
From the code
The rows are a constant.
export const EXAMPLE_VITALS = [
{ page: "/lab", lcp: 2.4, inp: 180, cls: 0.04, engaged: 0.62 },
]The filter is a substring on the path.
return EXAMPLE_VITALS.filter((row) => !needle || row.page.includes(needle))Google and Adobe
Google queues advanced_lab_view after Accept. Adobe is an example of the same fields.
After Accept, this lab queues advanced_lab_view. The demo payload stays on the page. This site does not call Adobe.
Simplified shape of the object queued after Accept.
dataLayer.push({
event: "advanced_lab_view",
lab_id: "vitals-vs-behavior",
})Example implementation. This site does not call Adobe. eVar166, prop166, and event166 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 eVar166 with Most Recent allocation and expire it on the hit.
Example alloy payload. _example is a placeholder schema, not a real tenant.
alloy("sendEvent", {
xdm: {
eventType: "web.webinteraction.linkClicks",
_example: {
vitalsSource: "example",
},
},
})Example hit. eVar166 is hit-scoped in this example.
s.eVar166 = "example"
s.prop166 = "example"
s.events = "event166"
s.tl(true, "o", "advanced_lab_view")Translation
Each lab field, the GA4 name, and the example Adobe variable. Scope is the part that usually gets lost in the translation.
Lab id
GA4. Parameter lab_id on advanced_lab_view.
Adobe. Example eVar, expire on the hit.
Scope. Event. It names this lab, not the user.
Demo value
GA4. Not sent. Scores, proofs, and payloads stay on the page.
Adobe. Example prop. Do not copy the demo value.
Scope. Local state. It is not a user property.
Example counts
GA4. Not sent. Labeled example data is not a metric.
Adobe. Example event. Not sent.
Scope. A figure on the page, not a hit.
Consent
GA4. The view event is skipped until Accept.
Adobe. Example: skip the hit while consent is off.
Scope. A gate on the hit.
Recommended next
Why these picksReading path transitions…