Signals in Responsys

Signals for Responsys extends the functionality of Wunderkind to the Oracle platform. The new feature embeds dynamic email or text elements within existing or new Responsys templates within API limits, defined below.

Key attributes of the Integration

Out of the box integration with Responsys Channel API's
Performance tested API and payload limits (including for peak BFCM traffic)
Leverages latest 1.4 Login (Auth) service supported by Responsys
In-product (Responsys) reporting includes Wunderkind initiated sends
Support for Movable Ink templates

Sample Signal

Click here to see a sample Signals payload for email.

Suppression Logic & Frequency Caps

Wunderkind's sender integration with Responsys means that emails are deployed from Responsys, 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 Responsys. However, before leaving the site, John opts out of all notifications.
Prior to triggering the send to John, Responsys 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, Responsys 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, Responsys 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!

As of September 7, 2025, we adhere to the following API limits with Oracle:

📌 API Method = Merge Trigger Email

Max Payload = 100KB

API Calls / min = 2000

📌 API Method = Async Merge Trigger Email

Max Payload = 100KB

API Calls / min = 3500

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

Technical Support

All Signals implementations with Responsys 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 Oracle 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