Email Signals for SFMC Journey Builder: Wunderkind-Provided Components

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

• Campaign-specific journeys

• Journey Entry Event Configuration

• Sendable Data Extensions

• Personalized data payloads sent via Signals

• Default journey behavior

• Content Blocks and an Example HTML Template

Campaign-Specific Email Journeys

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

• Behavioral Campaigns

  • Cart Abandonment: wknd_email_cartabandonment

  • Product Abandonment: wknd_email_prodabandonment

  • Category Recap: wknd_email_categoryrecap

• Catalog Campaigns

  • Low Stock: wknd_email_lowstock

  • Back in Stock: wknd_email_backinstock

  • Price Drop: wknd_email_pricedrop

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

Email Cadence

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

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 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 Signals

Wunderkind leverages the Salesforce Marketing Cloud REST Interaction Events API to trigger Signals. 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 Emails 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 emails 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 emails are not subject to the same rules and do not require any cross-campaign priority configuration

Behavioral Journey - Visual Reference

Content Blocks and an Example HTML Template

As part of your Signals integration, Wunderkind will generate HTML content blocks and an example email template in your Salesforce Marketing Cloud account.

Product Grid Data

The Items field in each of your sendable data extensions will populate relevant products tailored to each recipient session. Each product passed will include the product's name, landing page URL, image URL, and a unique identifier.

HTML Content Blocks

Within your main Content Builder folder, you will see a new folder called Wunderkind Content. It has two subfolders containing the following assets. Each block is pre-configured with AMPscript code to display products passed via the Data Extension Items. All blocks are styled cleanly with a sans-serif font and black button – ready for you to apply branding as desired.

• HTML Content Blocks - JSON Field
  • Wunderkind Product Grid - 2 Column
  • Wunderkind Product Grid - 2 Column Stacking
  • Wunderkind Product Grid - Rows
  • Wunderkind Product Grid - Rows Stacking
  • Wunderkind Hero Product
• Templates - JSON Field
  • [Wunderkind Example Email Template]
     

HTML Email Blocks - Visual Reference
 

Wunderkind_Product_Grid_2_Column
Desktop	Mobile

Wunderkind_Product_Grid_2_Column_Stacking
Desktop	Mobile

Wunderkind_Product_Grid_Rows
Desktop	Mobile

Wunderkind_Product_Grid_Rows_Stacking
Desktop	Mobile

Wunderkind_Hero_Product
Desktop	Mobile

Content Block Implementation

Hero Product Block

• Leverage this block to display a single dynamic product in your email hero section. By default, this will be the product that the recipient interacted with most recently.
• If using both Wunderkind Hero Product and a Wunderkind Product Grid within the same email template, ensure that the hero block comes first – it contains AMPscript that flags to the template that the grid should start at the second dynamic product, knowing that the first product will already have been displayed in the hero.

HTML Template Implementation

You can use this pre-configured HTML template directly in Wunderkind journeys, or reference when building your own branded templates using those same blocks.

AMPScript Usage

• The code block directly within the HTML <body> sets two variables that adapt the product display to the optional inclusion of the Hero Product Block. Include this snippet at the top of every Signals email.

%%[
    /* Global Logic: Initialize deduplication to ensure the Hero product doesn't repeat in the grid */
    SET @hasHeroProduct = false
    SET @heroIndex = 1
]%%

Content Block Inclusion

We use the ContentBlockById function to display two example HTML content blocks.

• The first ID references your Wunderkind Hero Product block, which resets the @hasHeroProduct flag to true.
• The second ID references your Wunderkind Product Grid - 2 Column Stacking block, our top-performing product layout for the below-hero section.

CSS Classes

In the HTML <style> section, find all CSS classes required to support the mobile responsiveness seen throughout the visual renderings above. For example, to force product cards to “stack” on mobile, Wunderkind Product Grid blocks leverage the wknd-full class to bring containers to 100% width.

If adding a Wunderkind-provided content block to your own custom email template, ensure that all classes used by the block are present in that template’s header. All Signals classes are prefixed with wknd for easier management.

<style>
  @media screen and (min-device-width:10px) and (max-width:600px) {
    /* The classes below power the layout and responsiveness of Wunderkind-provisioned blocks. When migrating these blocks into your own custom templates, ensure the relevant CSS is present. */
    .wknd-full {width:100%!important;height:auto!important;}
    .wknd-box-lg {width:95%!important;}
    .wknd-box {width:90%!important;}
    .wknd-half {width:49%!important;}
    .wknd-prodCopy {padding:10px 0!important;font-size:16px!important;line-height:1.2!important;}
    .wknd-prodCopy-sm {font-size:14px!important;}
    .wknd-imageCol {width:35%!important;}
    .wknd-textCol {width:64%!important;}
  }
</style>

If you are a current Wunderkind client and interested in Signals for SFMC, please reach out to your Customer Success Manager (CSM) or Account Executive (AE) to learn more.

📩 For any other Signals-related questions, shoot us a note at build-support@wunderkind.co. A member of our team will get back to you as soon as possible.