You are here:
Non-Image-Based Promotions
Use a non-image-based promotion with Einstein Decisions to return strings of text as decisions, such as a call-to-action selection. Typically, you use a non-image-based promotion with a server-side campaign, and the Personalization response is a string that the client computer uses. The process for creating a non-image-based promotion is the same as an image-based promotion. Depending on your template options, you can also define a promotion fallback.
A non-image-based promotion requires an asset because a content zone or tag is necessary for bandit decisioning. The asset can be a placeholder image URL or a 1x1 pixel image file. Personalization uses the asset’s content zones and tags to train the bandit and filter which promotions the bandit considers.
Because the asset is just a placeholder for content zone and tag configuration, promotion attributes help determine the data that Personalization returns in an Einstein decision. Key factors to consider include:
-
Attributes that contain information, such as call-to-action text, asset ID, or an action name, can return in the campaign response payload instead of the asset image URL.
-
The campaign response object is configurable in the template. A template developer can determine which information to return for a promotion.
There are several things a template developer must do when configuring a template for a non-image-based promotion.
-
Use the Einstein Decisions global template as the template baseline.
-
Hard code the eligible content zones or tags, such as Homepage Hero CTA or Add to Cart CTA, into the template server-side code. For more information, see Einstein Decisions - Server-Side Template.
-
Configure the campaign response object to return the applicable promotion attributes. For example, for a Homepage Hero CTA template, configure the campaign response object to return the Homepage Hero CTA attribute in the promotion.
