Event Properties in Bloomreach AMP

In the API calls that trigger your Bloomreach scenarios, Wunderkind passes user-dynamic fields as properties of the trigger event ($.commands[1].data.properties in the batch request). Inside the scenario, every one of those fields is available through the Jinja event object. Use this page when implementing those fields in your email nodes and templates. For guidance on composing AMP email designs in Bloomreach, see our Help Center.
The properties on this page represent standard e-commerce events, as shown in the API payload examples. These examples are intended as a general reference and do not reflect client-specific customizations.

Dynamic Product Properties

Each payload includes an Items array, which populates one object per dynamic product. By default, the array is sorted by the recipient's interaction recency (most recent to least recent). The following keys are sent within each product object:

WkId: Unique product ID
WkCopy: Product name
WkImageUrl: Product image path (src attribute)
WkUrl: Product page URL

In certain campaigns, additional keys are available within each product object. Do not reference these keys outside of the specified campaigns:

Price Drop
- WkPrice: Original product price
- WkSalePrice: Discounted sale price
Low Stock
- WkQuantity: Remaining inventory

To render the product grid, loop over the array in your email template:

{% for item in event.Items %}
  <a href="{{ item.WkUrl }}">
    <img src="{{ item.WkImageUrl }}" alt="{{ item.WkCopy }}" />
    <p>{{ item.WkCopy }}</p>
  </a>
{% endfor %}

To cap the grid at a fixed number of products, slice the array: {% for item in event.Items[:3] %}. Wunderkind sends up to four products; your template controls how many render.