Experience Management

A connected object’s destination is managed separately from the physical item. That makes updates possible without changing the object, but it also requires clear publishing responsibility.

Experience states

An experience can move through draft, review, scheduled, published, paused, and retired states. Customer programs should identify:

• who supplies and owns content;
• who may approve publication;
• who may request changes;
• which changes require fresh legal or brand review;
• what appears if an experience is paused or retired.

Safe publishing principles

• Draft and preview access does not equal public approval.
• Brand names and assets are published only within documented authorization.
• Pricing, eligibility, fulfillment, and contractual terms remain server-authoritative.
• A destination change must stay within the agreed program purpose.
• Sensitive customer information is not embedded in public URLs or page source.
• A launch includes fallback and failure-state review, not only the happy path.

Change requests

Provide the object or campaign reference, requested change, desired timing, approving contact, and any required assets. Emergency changes should state the customer impact and whether the experience should be paused while review occurs.