Advanced architecture
Agent to agent
Two agents can negotiate the next step without a chat product. Choose a goal. A visitor agent asks, and the site agent answers with a lab on this site and a consent check. The transcript is the exchange. No hosted model is called.
The turns are rules in this page. A hosted visitor agent and a hosted site agent are not connected.
Understanding the labHow to use it and why you'd want to
Why you'd want to
You want the negotiation written down, not hidden in a chat product. Pick a goal and read each turn, and no hosted model is called.
How to use it
- Pick measure, privacy, or packages.
- Press Negotiate and read the transcript.
- Open the lab the site agent named.
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.
negotiate returns a short MCP-shaped transcript for a goal and a consent state. The site agent names a public lab. The function does not call a model.
Map the goal to a lab
measure goes to the dataLayer lab, privacy to consent, and packages to experiments.
Say consent out loud
When consent is denied, the site agent still names the lab and says it will not record the visit.
Show the turns
The page prints each role, method, and sentence. The MCP player walks the same exchange.
From the code
The destination is a public path on this site.
const destination = goal === "measure" ? "/lab/datalayer" : goal === "privacy" ? "/lab/consent" : "/lab/experiments"The transcript is the return value, rendered.
turns.map((turn) => <li key={turn.method + turn.text}>{turn.role}: {turn.text}</li>)Google and Adobe
This lab does not queue its own event. The Google block is an example. Adobe is an example too.
This lab does not queue an analytics event of its own. The push below is an example, not a call this page makes. This site does not call Adobe.
Example only. This page does not push this object.
// Example only. This lab does not queue this event.
dataLayer.push({
event: "agent_to_agent_example",
lab_id: "agent-to-agent",
})Example implementation. This site does not call Adobe. eVar172, prop172, and event172 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 eVar172 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: {
agentGoal: "privacy",
},
},
})Example hit. eVar172 is hit-scoped in this example.
s.eVar172 = "privacy"
s.prop172 = "privacy"
s.events = "event172"
s.tl(true, "o", "agent-to-agent_example")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…