Publish Experiences

Experiences are deliberate customer guidance: tours, launchers, banners, announcements, surveys and onboarding programs. Plan availability and rollout approval expose the tools; publishing still requires permission and customer configuration. Creating a draft does not run it for visitors.

Prepare

Install the widget with verified, allowlisted attributes and a working CSP. Use an owner or administrator with experiences.manage to author and a role with experiences.publish to publish. A role that can only view should not be able to change or publish a draft.

Install the Cairn capture extension from the portal's verified store link, then pair it with the same production workspace. If no listing link has been configured yet, store distribution is not ready; a developer's unpacked build is not evidence of customer installation.

Author a tour

Open Experiences and create a tour. Use a descriptive internal name, plain customer-facing copy, and a small number of steps with one action each. Open the target page in a synthetic-data account. Use the editor's extension element picker to select the actual element; prefer stable semantic labels or dedicated data attributes over volatile CSS classes and positional selectors.

Check each step's target, placement, text, next/back controls and behavior when an element is absent. Capture/picking must retain structured selector candidates and element metadata. Do not put typed secrets or values from masked inputs in a step's capture contract. Test a dynamic menu or modal by deliberately opening it before picking its element.

Target the right people

Set the host/path rules and signed audience, actor surface or role attributes your application supplies. For AccordRx, pharmacy and buying-group guidance may differ, and customer, seller and admin pages are distinct surfaces. Do not use DEA/NPI/NCPDP/license/order/serial data as targeting attributes.

Test a matching and a nonmatching account and a matching and a nonmatching route. Browser page facts help select an experience; they do not grant access to a customer/internal guide. Signed identity and Cairn's server-side audience checks remain the boundary.

Publish and run

Review the draft with the person responsible for the workflow. Publish it deliberately, then load the actual customer page with an ordinary account. Verify its launcher or configured trigger, step order, target visibility, focus behavior, navigation and completion state. Test SPA navigation and a full reload. Confirm unpublished or unselected experiences do not start.

For an onboarding program, add the approved checklist items and confirm progress only changes when the corresponding action occurs. Verify incomplete items remain visible and completed items persist for the same verified person. Test a second person on the same browser after a full logout; progress must not transfer.

Pilot proof

AccordRx must publish and run at least one tour and one checklist on its intended surface, including extension element picking. Separately verify Cairn's own in-portal onboarding checklist. Record the experience IDs, publication revision, workspace, browser, actor role and sanitized screenshots. Exercise unpublish/retarget behavior so the owner can stop guidance without deploying the customer application.

Automation and recording require their own explicit permissions, configuration and consent. Making an Experiences screen available does not authorize the widget to execute a workflow or record a visitor.