Home/Field Guide/Sites, CMS & commerce
CONCEPT 22
Commerce, personalization, and analytics
Connect catalog and account context to buying experiences, measurement, and experiments.
Commerce context changes the answer
A catalog organizes products. Products have purchasable SKUs, while a channel represents a selling context and its configuration. The same SKU can produce a different result depending on channel, currency, account, price lists, eligibility, inventory, and promotions. Keep your storefront’s display consistent with the pricing and checkout authority.
In a B2B portal, map the customer to an account and test an eligible buyer and a buyer from another account. Check product visibility, account pricing, order access, approval, taxes, and shipping. Define how an order reaches fulfillment and how an integration handles partial failures or duplicate events.
Personalize against a baseline
Segments identify audiences according to supported criteria. Experiences can present page variants. Define which version an unknown visitor sees and test overlapping segment membership. Keep permissions independent of personalization. An audience condition changes presentation, while permissions protect data.
Measure the outcome
For a guided reordering experience, set an event definition, verify events from each version, and decide the success measure before launch. Use Analytics Cloud and supported testing features where licensed and connected. Review consent, retention, filtering, and user identity mapping before connecting environments.