Simulation
Concierge
Type a goal. Keyword rules build a path of real pages, with a reason for each stop. No model call.
Understanding the labHow to use it and why you'd want to
Why you'd want to
A sentence is matched to the first keyword list, and that list's three real pages are laid out with a reason id. After Accept the page queues lab_interaction with the path id.
How to use it
- Type a goal. The first matching word list wins.
- The stops are real pages on this site.
- Each stop shows the reason beside the link.
- After Accept, the queued id is the path, not the sentence.
Simulation. Keyword rules build the path. The sentence is not stored and is not sent to a model.
Goal
A path through this site
Why am I seeing this? The first matching list wins: learn, measurement, personalization, or help. Each stop is a real page and the reason is the rule id, not a generated paragraph. No match means no path.
WalkthroughHow we built itShowHide
Example vendor setup is marked below. eVar and event numbers are examples. This lab does not call Adobe.
The concierge lab matches a sentence to the first keyword list and lays out that list's three real pages, each with a reason id. After Accept it queues lab_interaction, and the lab does not call Adobe.
Match the first word list
pathForGoal lowercases the sentence and finds the first path whose word appears in it. The lists are basics, measurement, personalization, and help.
Return the stops
A match returns the path id and its stops. Each stop is a path on this site and a reason id such as measurement-word or gate. No match returns null.
Show the reason beside the link
The page looks up a sentence for the reason id and links to the localized path. The sentence is not generated.
Queue the path id
useLabView queues action view. Build a path calls trackLab with the path id, or no-match. The stops are not parameters.
From the code
The first keyword list becomes the path. No match returns null.
export function pathForGoal(text: string): ConciergePath | null {
const query = text.toLowerCase()
const match = PATHS.find((path) => path.words.some((word) => query.includes(word)))
if (!match) return null
return { id: match.id, stops: match.stops }
}One path: three real pages and a reason id on each stop.
{
id: "measurement",
words: ["ga4", "measurement", "datalayer", "analytics", "tag"],
stops: [
{ href: "/lab/datalayer", reason: "measurement-word" },
{ href: "/lab/server-side", reason: "same-event-server" },
{ href: "/lab/consent", reason: "gate" },
],
},Google and Adobe
Google queues lab_interaction after Accept. Adobe is an example of the same fields.
Queued only after Accept. The page queues lab_interaction with action view and label page. Building a path queues action run_demo with label set to the path id, or no-match. The stops and reason ids are not parameters. This site does not call gtag('set') or Adobe.
Simplified shape of the object queued after Accept. Register any new parameter as an event-scoped custom dimension. This site does not call gtag('set').
dataLayer.push({
event: "lab_interaction",
lab_id: "concierge",
action: "run_demo",
label: "measurement",
})Example implementation. This site does not call Adobe. eVar58, prop58, and event58 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 eVar58 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: {
conciergePath: "measurement",
},
},
})Example hit. eVar58 is hit-scoped in this example. prop58 dies at the same hit.
s.eVar58 = "measurement"
s.prop58 = "measurement"
s.events = "event58"
s.linkTrackVars = "eVar58,prop58,events"
s.linkTrackEvents = "event58"
s.tl(true, "o", "lab_interaction")Translation
Each lab field, the GA4 name, and the example Adobe variable. Scope is the part that usually gets lost in the translation.
Path id
GA4. label on lab_interaction when action is run_demo. basics, measurement, personalization, help, or no-match.
Adobe. Example eVar58, expire on the hit.
Scope. Event. A user property would keep measurement onto the next sentence.
Stop
GA4. Not sent. Each stop href stays on the page.
Adobe. Example prop58 on the hit.
Scope. Hit, if you tracked one link. The queued label is the path id, not the href.
Reason id
GA4. Not sent. The page translates the reason id into a sentence.
Adobe. Example eVar58 if you sent the reason. This event sends the path id.
Scope. Hit. The reason explains this stop, not the visitor.
Sentence
GA4. Not sent. The matcher reads it and drops it.
Adobe. Example: do not write the sentence into prop58.
Scope. Not an event parameter and not a user property.
Recommended next
Why these picksReading path transitions…