This article is relevant only to the Restaurants vertical
Experience OS empowers quick service restaurants to deliver highly personalized recommendations and promotional content. By leveraging dynamic A/B testing, restaurants can tailor their campaigns based on user behavior, time of day, and geo-location - ensuring optimized recommendations of items and offers reach each guest at the perfect moment. With just a few steps, you can launch, test, and refine campaigns that drive traffic, boost order conversions, and elevate the overall dining experience.
Step 1: Create the campaign
From the Experience OS homepage:
- Select your Application (Experience Web, Experience App, Experience Kiosk or Experience Drive-Thru).
- Go to Create Campaign › Product Recommendations.
- Enter a campaign name, and optionally, add notes and labels for easier tracking.
- Select an API Selector name
The API Selector Name allows the restaurant to identify for which campaign you're requesting the recommendation widget.
Step 2: Configure the experience
- Create new Experience.
- Select New Variation or Copy from another Experience.
- Select the widget types to include in the variation. Each widget appears at a specific stage of the user's journey. Learn more about Widgets.
To ensure consistency across variations, define the widget structure at the start of the experience. Each variation must include the same type and number of widgets per campaign. This setup enables full control over the user journey, with personalized content adapting within a fixed structure—supporting accurate analysis and a seamless experience.
Step 3: Select the algorithm, features, and business rules
- Add a Recommendation.
-
Select the Algorithm. Learn more about algorithms
The algorithms offered in the dropdown menu are dynamically filtered based on the selected widget. Each algorithm is mapped to support both All Users and Identified Users with all users recommendations being a required baseline. - Define the Features. Learn more about features
-
Apply Business Rules. Learn more about business rules
Repeat steps 1-5 to add the optimal number of recommendations before saving the variation.
-
Click Save Widget.
Step 4: Allocate traffic
Choose the Traffic Allocation percentage between your test variations and the control group.
Step 5: Set targeting parameters
Control where, when, and to whom the campaign appears:
Display in all stores and select specific stores to apply this experience.
| WHO | |
|---|---|
| Audience |
Which segment of the population will see the recommendations. For example, all users or predefined identified users. |
| WHERE | |
|---|---|
| Screen |
Specify the screens where this experience will be applied. This can include the cart page, the current screen, product popularity views, or other relevant touchpoints within the user journey. |
| WHEN | |
|---|---|
| Date | Select dates or date ranges (by user or site time zone) |
| Day of the Week | Select specific days (such as Saturday or Sunday). Useful for weekday vs. weekend experiences. |
| Time of Day |
Set specific time ranges throughout the day (by the user or site time zone) Note: Dynamic Yield does not adjust the time based on Daylight Savings Time. |
Step 6: Activate and publish
- Set the experience status to Draft (default) or Active, and then click Save Experience
- Publish the campaign when ready.
- After the campaign is published, click the API details icon to view the API selector. This is needed to serve the recommendation widget.
Fallback Campaign
To ensure a seamless customer experience during network outages, it is recommended to configure a fallback campaign that provides default, store-specific product recommendations based on daily popularity. Learn more about fallback campaign configuration.