Use HTML in a web experiment
You can HTML in a variant for an experiment, which is particularly useful for facilitating 1:1 personalization by running dynamic data.
Most variants must also pass guest data to your organization's website, for example, the guest's first name, location, and loyalty number. To do this, you must configure the API request to include the dynamic data so that when the variant executes, the data is requested from the server and then passed to the variant.
You can use handlebars.js to access nested values by index from the API response. For example, you might want to display offers in an experiment that are returned from a decision model. Because the offer is a value that is nested in an array, you must use the array.index or array.{index} handlebars.js syntax.
If the web experiment is configured with a decision model, you can insert attributes returned by the decision model into the HTML.
To use HTML in a web experiment:
-
In the Experiment variants tile, click the Edit icon next to the variant you want to configure.
-
In the code editor, on the HTML tab, enter any HTML that you want to use in the web experiment.
-
To insert dynamic data into HTML, on the Data tab, in the Data Selector search box, enter a guest's email address or other identifier to search. This enables you to access data model attributes and paths.
TipIf there is a guest whose data you often use when configuring or testing code, click the star icon to bookmark the guest so you no longer have to search for them.
-
To include dynamic guest data, under the Guest data model tree, click
and click Copy Path as Handlebars. -
To include dynamic data from the decision model response, expand the Decision Model Response tree, click
and Copy Path as Handlebars. -
To include dynamic data from the experience response, expand the Experience Response tree, click
and Copy Path as Handlebars. -
On the HTML tab, paste the data and click Save.
-
Click
to close the code editor.You must also include the dynamic data when you compose the API request. This ensures that when the experience executes, the server requests the dynamic data and passes it to the variant.