SFMC Journey Builder AMP Integrations for Email: Wunderkind Campaign Decisioning Engine

This documentation provides an overview of how Wunderkind campaigns are configured and managed within Wunderkind Core, how campaign eligibility is evaluated, and how AMP triggers a message in your ESP. It also outlines when signals are sent and how they are intended to interact with your ESP environment in a controlled and intentional way.

Campaign Selection (per visit)

• At the end of a user’s visit, we evaluate campaigns in priority order and send a signal for the single highest-priority behavioral campaign the user is eligible for during that visit

• Catalog emails are not subject to the same prioritization rules as behavioral emails and texts. Catalog signals are scheduled to send at the same local time of day as the user’s original interaction with the item

Campaign Definition

• We have campaigns ordered by priority (highest to lowest) in our backend. Each campaign maps to a signal  

• All signals are triggered by a single-part Wunderkind Campaign. In practice, this means 

  • The signal is intended to initiate a Journey in SFMC

  • If the Journey includes multiple steps, those additional parts live in the ESP

  • The data in the initial signal will persist throughout the multi-part Journey

Specific Campaign Criteria

Behavioral Emails

Cart Abandonment

• Send Delay: 10 minutes after endvisit

  • Total ~40 minutes after inactivity

• Rendered Items: Max 4

  • Unless you are a migrating client, your max will remain the same.

• Campaign Trigger: End of Visit

• Campaign Eligibility Criteria: 

  • User has triggered add to cart this visit

  • User did not abandon with an empty cart

  • User has not converted since last add to cart event

• Dynamic content:

  • Items added to cart

  • product urls contain cart replenishment param

  • Homepage url with cart param

Product Abandonment

• Send Delay: 10 minutes after endvisit

  • Total ~40 minutes after inactivity

• Campaign Trigger: End of Visit

• Campaign Eligibility Criteria:

  • User has triggered view product this visit

  • User has not converted since last view product event

  • User is not eligible for a higher priority series from this visit (cart abandonment)

• Dynamic Content

  • Items viewed, then backfilled from the same category

Category Recap

• Send Delay: 10 minutes after endvisit

  • Total ~40 minutes after inactivity

• Campaign Trigger: End of Visit

• Campaign Eligibility Criteria:

  • User has triggered view category this visit

  • User has not converted in the last 1 hour

    • Internal note: This is set to one hour due to a Core UI limitation, but the end-user experience should closely mirror a “since last view category” event.

  • User is not eligible for a higher priority series from this visit (cart or product abandonment)

• Dynamic Content

  • Items from last viewed category list page

  • last viewed category page URL

Catalog Emails

Back in Stock

• Send Delay: Dynamic. The signal is scheduled to be sent at the same time of day as the user’s original interaction with the item, following detection of a qualifying product change.

• Campaign Eligibility:

  • User has triggered Back in Stock Product Change

    • An item that a user viewed within the last 180 days was previously OOS and is now back in stock

  • User has not converted since last Back in Stock event

Price Drop

• Send Delay: Dynamic. The signal is scheduled to send at the same time of day as the user’s original interaction with the item, following detection of a qualifying product change.

• Campaign Eligibility:

  • User has triggered Price Drop Product Change

    • An item that a user viewed within the last 180 days has a price drop

    • Products contain variables for price and sale price

  • User has not converted since last Price Drop event

Low Stock

• Send Delay: Dynamic. The signal is scheduled to send at the same time of day as the user’s original interaction with the item, following detection of a qualifying product change. 

• Campaign Eligibility:

  • User has triggered Low Stock Product Change

    • An item that a user viewed within last 14 days is considered low stock

    • Products contain a variable for the quantity remaining

  • User has not converted since last Low Stock event

Send limits across visits 

• A user may only receive one signal for a given campaign within a rolling 24-hour window.

• Within 24 hours of a user’s most recent send:

  • The same campaign will not be sent again.

  • Other campaigns may still be sent if their eligibility conditions are met.

• As a result, a user may receive multiple signals within 24 hours, provided each is for a different campaign. 

  • Wunderkind will provide campaign and cross-campaign priority within the ESP to determine which campaign is sent to the end user.

• After 24 hours from the last send of a specific campaign, that campaign becomes eligible again according to its standard eligibility rules.