Required scopes: marketing_templates_readStructured objects blocks bind (cartContext, reviewRequest, tracker, orderSummary). Typed or upcoming block payload keys that bind this object (trackableSummary, products, qrCode, …).
Schema data type, e.g. Trackable Summary or Cart Context.
CamelCase key to store on the block’s schemaFieldName, e.g. orderSummary.
Paths a DYNAMIC table may use as rowCollection. Cell bindings stay empty until nested item schemas exist. Known {{ }} paths on each row. Empty until nested item schemas exist; empty when openEnded is true. What the path resolves to on each row.
Expression to put in a dynamic cell, including the item alias, e.g. item.product.title. Write {{ item.product.title }}.
What the collection holds.
Row alias each row is bound as. Always item; cells must use {{ item.… }}.
Element type, e.g. Line Item, Trackable Line Item, or Object.
True when nested array paths under this object are merchant-defined (custom-event properties). Append the array key to path.
Value for rowCollection, e.g. relevantLineItems or properties.order_products.
The trigger this catalog was built for.
CamelCase Url / Maybe Url keys for DYNAMIC_VARIABLE button and image bindings. CamelCase key to store on schemaFieldName / clickthroughSchemaFieldName, e.g. trackingLink.
Names for {{ }} in subject, preview text, text blocks, and other authored strings. Schema data type, including Maybe/Multiple prefixes, e.g. Maybe Text.
What the value holds at send time.
True when the email/SMS insert-variable picker would show this name. Hidden and structured fields still resolve if authored.
True when send-time resolution depends on a connected integration. The name is still listed; a missing integration yields an empty value.
CamelCase schema key this name came from, e.g. customerFirstName.
Snake_case identifier, e.g. customer_first_name. Write {{ name }}.
Whether this name comes from the trigger, renderer, or store.
