Upbuild
Data reference · Adobe Launch
Every Adobe Launch metric and dimension you can ask for.
Adobe Launch, now Experience Platform Tags, is configuration: so this reference lists the entities Upbuild reads when you ask what a property deploys. Properties, rules, data elements, extensions and the publishing flow, all read-only by scope.
Source: Reactor API, read scopes · Updated September 2026
Properties
5 fieldsThe container-equivalents of the Adobe world.
Ask it in Upbuild AI, or in Claude, ChatGPT, Copilot Studio and Gemini Enterprise through the Upbuild connector
| Field | Type | What it is |
|---|---|---|
property.id | Dimension | Property ID, PR-prefixed. |
property.attributes.name | Dimension | Property display name. “list our Launch properties” |
property.attributes.platform | Dimension | web or mobile. |
property.attributes.domains | Dimension | Domains declared on the property. |
property.attributes.development | Dimension | Whether it is a development property. |
Rules
13 fieldsWhen and what fires: each rule chains events, conditions and actions.
Ask it in Upbuild AI, or in Claude, ChatGPT, Copilot Studio and Gemini Enterprise through the Upbuild connector
| Field | Type | What it is |
|---|---|---|
rule.id | Dimension | Rule ID, RL-prefixed. |
rule.attributes.name | Dimension | Rule display name. “list all rules in property X” |
rule.attributes.enabled | Dimension | Whether the rule is on. “any disabled rules” |
ruleComponent.delegate_descriptor_id | Dimension | What the component is: the type ids below. |
core::events::click | Dimension | Click event. |
core::events::library-loaded | Dimension | Library Loaded, page top. |
core::events::page-bottom | Dimension | Page Bottom. |
core::events::dom-ready | Dimension | DOM Ready. |
core::events::window-loaded | Dimension | Window Loaded. |
core::events::direct-call | Dimension | Direct call rules, _satellite.track. “rules triggered by direct call” |
core::conditions::custom-code | Dimension | Custom code conditions: audit these. |
adobe-analytics::actions::set-variables | Dimension | Sets Analytics variables. |
adobe-analytics::actions::send-beacon | Dimension | Fires the Analytics beacon. “which rules send Analytics beacons” |
Data elements
10 fieldsWhere values come from, with their storage behaviour.
Ask it in Upbuild AI, or in Claude, ChatGPT, Copilot Studio and Gemini Enterprise through the Upbuild connector
| Field | Type | What it is |
|---|---|---|
dataElement.id | Dimension | Data element ID, DE-prefixed. |
dataElement.attributes.name | Dimension | Data element name. “list data elements in property X” |
core::dataElements::javascript-variable | Dimension | Reads a JS variable. |
core::dataElements::query-string-parameter | Dimension | Reads a URL parameter. |
core::dataElements::cookie | Dimension | Reads a cookie. |
core::dataElements::local-storage | Dimension | Reads localStorage. |
core::dataElements::custom-code | Dimension | Custom code element: the audit hotspot. “audit custom code data elements” |
core::dataElements::constant | Dimension | A fixed value. |
dataElement.attributes.storage_duration | Dimension | none, pageview, session or visitor. |
dataElement.attributes.clean_text | Dimension | Whether whitespace gets normalised. |
Extensions
5 fieldsInstalled capability packages and their versions.
Ask it in Upbuild AI, or in Claude, ChatGPT, Copilot Studio and Gemini Enterprise through the Upbuild connector
| Field | Type | What it is |
|---|---|---|
extension.id | Dimension | Extension install ID, EX-prefixed. |
extensionPackage.name | Dimension | core, adobe-analytics, experience-cloud-id-service and friends. “which extensions are installed” |
extension.attributes.version | Dimension | Installed version. “extensions running old versions” |
extension.attributes.enabled | Dimension | Whether the extension is active. |
extensionPackage.display_name | Dimension | Human name of the package. |
Environments and hosts
5 fieldsWhere builds go and how they are served.
Ask it in Upbuild AI, or in Claude, ChatGPT, Copilot Studio and Gemini Enterprise through the Upbuild connector
| Field | Type | What it is |
|---|---|---|
environment.id | Dimension | Environment ID, EN-prefixed. |
environment.attributes.name | Dimension | Environment display name. |
environment.attributes.stage | Dimension | development, staging or production. “embed codes per environment” |
environment.attributes.archive | Dimension | Whether it serves as archive. |
host.attributes.type_of | Dimension | akamai or sftp delivery. |
Libraries and publishing
5 fieldsThe publishing flow: what is drafted, submitted and live.
Ask it in Upbuild AI, or in Claude, ChatGPT, Copilot Studio and Gemini Enterprise through the Upbuild connector
| Field | Type | What it is |
|---|---|---|
library.id | Dimension | Library ID, LB-prefixed. |
library.attributes.name | Dimension | Library name. |
library.attributes.state | Dimension | development, submitted, approved or published. “what is waiting in the publish flow” |
library.attributes.published_at | Dimension | When it went live. |
build.attributes.status | Dimension | Build succeeded or failed. |
Good to know
Adobe Launch questions.
Can the assistant change or publish anything?
No. Upbuild's Launch access is read-only: it lists and describes rules, data elements, extensions and libraries, and cannot create, edit or publish.
How does this relate to the Adobe Analytics pages?
Launch is where the Analytics implementation lives: the set-variables and send-beacon actions here populate the eVars, props and events you query on the Adobe Analytics reference page. Auditing both together is the point.
What are those long delegate ids?
Type identifiers: extension::kind::type. The assistant translates them, so ask for click rules or custom code data elements in plain words and it maps to the ids.
Can I see what changed in production recently?
Yes: libraries carry their state and published_at, so the publish history and what each library contained are one question away.
Next