Guides
Start typing to search…

Wunderkind Signals in SFMC

Guide to using Signals for Text or Email with Salesforce Marketing Cloud (SFMC)

Signals for Salesforce extends the function of Wunderkind to Marketing Cloud (SFMC). The new feature embeds dynamic email or text elements within SFMC's Journey Builder and/or data extensions and supports cross-channel campaign execution well within Salesforce's API limits.

Key attributes:

  • Behavioral-Driven Integrations -- utilize the Wunderkind ID network to drive more revenue through existing triggers for all users identified by Wunderkind
  • Rich Data Transfer -- connect Wunderkind data across your marketing ecosystem for greater efficiency and insight. This includes exporting WKND data from your Data Extension (DE) to a Customer Data Platform (CDP), Reporting or Data Analytics (DA) platform
  • Self-Service Personalization -- create tailored, dynamic experiences without reliance on additional development resources. Automatically import and leverage Wunderkind Signals using established journey builder workflows

Integration Options

Wunderkind supports three integration methods with SFMC:

🔗 Import via Data Extension (DE) -- leverage an existing or new DE to collect Signals within your existing SFMC environment. WKND will publish relevant campaign and behavioral events real time to the DE and they can later be ingested into a relevant journey or triggered send workflow as desired.

Method:

{subdomain}.rest.marketingcloudapis.com/hub/v1/dataevents/key:{key}/rowset (synchronous)

🧱 Send to Journey Builder -- automatically send timely, personalized messages using Journey Builder. Create send events with a lookup to a specific object(i.e email address). After you create the applicable rule, messages are sent each time an update or insert event occurs on the specified object.

Method:`

{subdomain}.rest.marketingcloudapis.com/interaction/v1/events

📩 Initiate Triggered Sends -- send messages using the triggered sends API. WKND will route Signals data to the relevant user or product/category template. Messages are then triggered from SFMC to user via text or email.

Method(s):

{subdomain}.rest.marketingcloudapis.com/messaging/v1/messageDefinitionSends/key:{key}/send)’ {subdomain}.rest.marketingcloudapis.com/messaging/v1/messageDefinitionSends/key{key}/sendBatch)’

Sample Signal

Click here to see a sample Signals payload for email.

Suppression Logic & Frequency Caps

Wunderkind's sender integration with SFMC means that emails are deployed from SFMC, using Wunderkind Signals and identity to determine who, what and when content should be triggered. While Wunderkind will use known customer preferences and client settings (i.e max of 2 emails a day) to suppress a user from eligibility for a campaign notification, the final decision to send a message is the responsibility of the brand and ESP.

Let's review a quick example:

  • John Smith visits your brand website, but is unknown to you.
  • Wunderkind is able to identify John based on our SmartTag <> website interaction event mapping.
  • John opts in to marketing emails on your website and his preferences are recorded in Wunderkind.
  • The next day, John is back on the site and abandons something in his cart. Wunderkind recommends sending him an email within 30 minutes of the session ending and a "cart-abandonment" Signal is sent to SFMC. However, before leaving the site, John opts out of all notifications.
  • Prior to triggering the send to John, SFMC checks current marketing opt-in status and it says "false". While Wunderkind sent a Signal for John as he was eligible for the notification at the time, SFMC and brand are responsible for suppressing this email as the ultimate source of truth for user is the ESP subscribe status.

Rate Limits and Performance

Like most ESP's, Salesforce enforces strict payload and API limits with sends generated per day. With Signals adoption, because Wunderkind will only be sending dynamic content to your org, the chances of hitting these limits is greatly reduced, even during high-peak periods like BFCM!

📣 Did you know? The average Signal payload size is only 7kb!

Technical Support

All Signals implementations with SFMC include existing access to Wunderkind professional services, product strategy, customer success and technical support. In some situations, WKND may need to engage with our contacts at Salesforce Marketing Cloud (SFMC) to triage an incident or propose a recommended solution.

‼️ Any more questions? Contact us at [email protected]

💥 Interested in joining the Wunderkind Early Access Program? Click Here


Updated 1 day ago