SFMC Journey Builder AMP Integrations for Text: Wunderkind-Provided Components

Wunderkind will configure the foundational pieces of your AMP-powered text journeys in SFMC, including:

• Campaign-Specific Journeys 
• Journey Entry Event Configuration 
• Sendable Data Extensions
• Personalized data payloads sent via Signals 
• Default journey behavior 
• Wunderkind Dynamic User Data
  • Wunderkind Content Block Template
  • Dynamic Item Variables
• UTM Configuration

---

Campaign-Specific Journeys

Wunderkind will configure campaign-specific journeys in SFMC for the following campaign types. These journeys will be located in your Journey Builder UI and tagged with wknd_signals_text for easy identification.

• Behavioral Campaigns

  • Cart Abandonment: wknd_text_cartabandonment

  • Product Abandonment: wknd_text_prodabandonment

  • Category Recap: wknd_text_categoryrecap

• Catalog Campaigns

  • Low Stock: wknd_text_lowstock

  • Back in Stock: wknd_text_backinstock

  • Price Drop: wknd_text_pricedrop

• For existing Wunderkind clients migrating to SFMC Journey Builder, all currently supported modules will be supported. 

 

Text Cadence 

The provided journeys follow a defined text cadence based on observed performance and best practices. This cadence serves as the default structure unless your team is migrating with an adjusted strategy.

Customer and Prospect text series follow the same series length and send delays

Campaign Type	Series Length	Part 1 Delay	Part 2 Delay
Cart Abandonment	1 Part	2 Minutes	N/A
Product Abandonment	2 Parts	2 Minutes	3 Days
Category Recap	2 Parts	2 Minutes	3 Days

 

Campaign Type	Series Length	Part 1 Delay	Part 2 Delay
Back in Stock	2 Parts	0 Minutes	22 Hours
Price Drop	2 Parts	0 Minutes	22 Hours
Low Stock	2 Parts	0 Minutes	22 Hours

---

Journey Entry Event Configuration

Wunderkind will configure the Journey Entry Event used to trigger each campaign. These events allow external systems to send campaign triggers into Journey Builder via the Salesforce Marketing Cloud API. Events will be located in your Journey Builder UI under the events tab. Enter keyword wknd to display all Wunderkind events. 

---

Sendable Data Extensions

Wunderkind will create the sendable Data Extensions required to support each journey. These Data Extensions store the event data used to personalize and send campaign emails. They will be located in Contact Builder under the Data Extensions tab in a Wunderkind or Wunderkind Text folder. 

For existing clients migrating to SFMC Journey Builder, data extensions will be located in a Wunderkind Signals folder within your existing Wunderkind folder (if applicable).

---

Personalized data payloads sent via AMP

Wunderkind leverages the Salesforce Marketing Cloud REST Interaction Events API to trigger messages. Upon successful submission: 

1. A record containing the ContactKey and associated personalized data is written to the Journey's Event Data Extension.
2. The contact is injected into the configured Journey entry source.

This allows for dynamic messaging within the journey, based on their session behavior. 

---

Default Journey Behavior 

In addition to the campaign-specific journeys, Wunderkind configures default behavior within each journey, including: 

Entry source configuration

• Each journey is configured with the appropriate API entry source, so users are injected when triggered by the corresponding Wunderkind Signal.

• All journeys are configured to prevent contacts from re-entering until they've exited.

Prospect vs. Customer Segmentation

• Journeys will be configured with a decision split to create prospect and customer paths within the journey. 

• The decision split uses the userType attribute provided by Wunderkind in the Signals payload. This attribute represents Wunderkind’s classification of a user’s conversion behavior, based on conversion pixel data and historical customer data provided during onboarding.

Cross-Campaign Priority (Behavioral Text Only)

• For behavioral campaigns, a priority framework is applied to ensure the following behavior 

  • If a user is in journey, then goes back to the site and takes a higher-intent action, they'll always receive the higher-priority journey. The configuration will skip the remaining text in the current journey.

  • If a user is in a journey, then goes back to the site and takes a lower-intent action, the configuration will prevent their entry into the lower-priority journey.

• Catalog texts are not subject to the same rules and do not require any cross-campaign priority configuration

Behavioral Journey - Visual Reference

---

Wunderkind Dynamic User Data 

Wunderkind Content Block Template

Wunderkind’s Content Block Template contains SFMC specific code that pulls user’s dynamic item data into the text message. To use it, copy and paste the entire code block below. Do not modify the Content Block itself, and ensure it is placed before the message content. You may edit only the message content.

%%[/***** WUNDERKIND SMS CONTENT BLOCK: Do not edit logic. Use %%=v(@copy)=%% for COPY and %%=v(@url)=%% for URL *****/ SET @itemsJson=AttributeValue("Items") IF NOT Empty(@itemsJson) THEN SET @rs=BuildRowSetFromJson(@itemsJson,"$[0]",0) IF RowCount(@rs)0 THEN SET @row=Row(@rs,1) SET @copy=Field(@row,"WkCopy") SET @url=Field(@row,"WkUrl") ENDIF ENDIF /***** EDIT MESSAGE FROM THIS POINT FORWARD: *****/]%% [Brand Name]: Did you see something you liked? Take another look at %%=v(@copy)=%%: %%=v(@url)=%%

Note: This content block includes a sample message, make sure to update Brand Name to the proper Brand Name and alter the message to suit the send.

In your message text, reference the variables with:

• %%=v(@copy)=%% for the dynamic item copy

• %%=v(@url)=%% for the dynamic item URL

Example SMS: [Brand Name]: Did you see something you liked? Take another look at %%=v(@copy)=%%: %%=v(@url)=%%

Do not edit the logic between DYNAMIC SMS CONTENT BLOCK: Do not edit logic and EDIT MESSAGE FROM THIS POINT FORWARD.

• This section is responsible for reading the Items JSON and setting @copy and @url.

You can safely edit the actual SMS sentence below that comment (brand name, tone, punctuation, etc.) as long as you leave the variable calls (%%=v(@copy)=%% and %%=v(@url)=%%) in place where you want the user's personalization to appear.

Dynamic Item Variables

If you choose not to use the Content Block Template, you still must paste in the following ampscript before the dynamic variables (%%=v(@copy)=%% or %%=v(@url)=%%) to ensure the variables populate correctly within the text message:

%%[SET @itemsJson=AttributeValue("Items") IF NOT Empty(@itemsJson) THEN SET @rs=BuildRowSetFromJson(@itemsJson,"$[0]",0) IF RowCount(@rs)0 THEN SET @row=Row(@rs,1) SET @copy=Field(@row,"WkCopy") SET @url=Field(@row,"WkUrl") ENDIF ENDIF]%%

After pasting the ampscript into the text message, add your message content and include the appropriate dynamic variables where they are needed:

• Dynamic item copy: %%=v(@copy)=%%

• Dynamic item URL: %%=v(@url)=%%

Example Text Message:

%%[SET @itemsJson=AttributeValue("Items") IF NOT Empty(@itemsJson) THEN SET @rs=BuildRowSetFromJson(@itemsJson,"$[0]",0) IF RowCount(@rs)0 THEN SET @row=Row(@rs,1) SET @copy=Field(@row,"WkCopy") SET @url=Field(@row,"WkUrl") ENDIF ENDIF]%% [Brand Name]: Enter Text Content here using dynamic variables such as %%=v(@copy)=%% or %%=v(@url)=%%

---

UTM Configuration

Wunderkind will append utm_term=wknd_signals to all links passed in the JSON payload.