Articles
Monetate Experiences Overview
Monetate allows you to create, test, and deploy real-time personalized experiences across digital channels.
Capturing any interaction, behavior, or visitor segment and storing this data against an anonymous customer profile is an essent...
Experience Statuses
Any experience that you create within Monetate has a particular state or status. Experience status is important for many reasons. To begin with, this is how Monetate defines whether or not an experience is running, is scheduled to run, is ...
Configure the WHY of a Web Experience
Follow these steps to configure the WHY settings, including the metrics tracked, of a Web experience.
Dynamic Testing and Automated Personalization experiences optimize toward the goal metric you select, so ensure that you put some thou...
Default Metrics for Experiences
Monetate tracks and reports a variety of metrics for Web experiences. Each key performance indicator (KPI) listed here works out of the box without any additional tracking from the Monetate JavaScript API:
Bounce rate
Average page...
Configure the WHO of a Web Experience
An experience is the combination of data, content, and conditions that unifies and personalizes a customer's path across multiple channels. All experiences use a sentence-based structure that consists of four parts: WHY, WHO, WHAT, and WHEN....
Action Descriptions
Action Builder has five categories of actions that you can build.
Inserting New Content
The Insert Content tab contains options to build actions that insert images, HTML content, CSS styles, or JavaScript as well as to duplicate ...
Action Slotting
To prevent duplicate actions from firing, Monetate actions have slots. Slotting enables action prioritization. If two actions have the same slot, only the action with the highest priority displays.
How Monetate Defines a Slot
A stand...
Action Conditions
Action conditions specify the prerequisites for actions to fire. You can use them as a further level of granularity to determine the audience for an experience. Just as WHO targets define who is eligible for an experience, action conditions de...
Add Variants to a Web Experience
You can add variants to a Web experience and define the percentage of site traffic to participate in each variant within the WHAT settings.
Automated Personalization experiences have a limit of 10 variants per experience. All ot...
Configure the WHEN of a Web Experience
Experiences are the combination of data, content, and conditions that unify and personalize a customer's path across multiple channels. Simply put, they're all the stuff that makes your customers feel like your site was made just for them. All Mon...
Create a 100% Experience
A 100% Experience allows you to quickly make changes to your site content—text, images, styles, and more—without any support from a Web developer. This experience type is a useful agility tool because it shows every site visitor in your defined ...
Create a Full-Page Test Experience
A Full-Page Test (FPT) experience allows you to redirect all site visitors to an alternate version of a full page on your site. It's useful when you want to test an entire alternate page or if you want to track data and audiences using a p...
Activate an Experience for Preview and Testing
You have multiple options for previewing an experience before you activate it to ensure the WHAT action or actions work as you expect. In some situations you must first activate the experience so that you can then test it, specifically to ...
Preview Mode Limitations
The preview options available for a Web experience can help you confirm that an action works the way you intended.
Recent updates to Safari Intelligent Tracking Prevention (ITP) block third-party cookies on your website. This upda...
Experience QA Tips
You've built an action and it's looking pretty great. Congrats! Now you need to make sure that your visitors have the same positive experience. The tips below are a few considerations that can save the day when you QA your own work.
U...
Troubleshooting an 'Unknown' Track
When the Monetate tag runs, Monetate runs custom.js , a compiled JavaScript file with all the necessary code to execute actions and collect relevant page information. By default, this script waits until the DOMContentLoaded browser...
Experience Priority
Experience priority is a system that determines which experience takes precedence on a site when multiple experiences use the same action or when actions have the same settings for an overlapping target audience. For example, if you have one expe...
Enable Auto-Promotion for Experiences
You can configure experiences to auto-promote within Monetate. An experience must meet two guidelines to enable auto-promotion:
The control threshold as defined by the slider in the WHY part of the experience must be greater than zero.
...
View Experience Change History
After you build an experience, you may want to review what has changed over time. To do this, review the Experience History. To view the history, click the experience on the All Web Experiences list page. Next, on the Experience Editor page, clic...
Duplicate a Web Experience
You cannot edit some portions of a Web experience after you have activated it. Duplicating an experience provides you with one workaround you can use if you need to revise an active experience.
Duplicating an Experience Within the Sam...
Duplicate an Experience into a Market
Follow these steps to duplicate a Web experience into a market .
You cannot duplicate into another account a recommendations experience configured with a recommendation strategy that uses a product catalog that is not the default o...
Web Experiences FAQ
General What are retailers vs. account instances? Monetate operates within a parent/child account structure. The parent is referred to as the retailer, and the children are referred to as account instances. In the following example, The Gromme...