Reconnect is the Dynamic Yield omni-channel customer journey orchestration app, designed to help you deliver personalized, event-triggered messages across email, SMS, app push, and web push channels. This guide walks you through the necessary steps to launch your first Reconnect campaign—from integrating messaging channels to analyzing campaign performance.
Integrate your channels
|
To send messages across different channels, Reconnect integrates with third-party messaging providers. Reconnect doesn’t send messages directly—it triggers API events, and your selected provider handles the delivery. You can configure one integration per supported channel: Email, SMS, App Push, and Web Push. Each integration requires specific credentials and setup steps, which you can manage in the Reconnect Integrations tab. |
|
Manage your opted-in usersBefore you can send messages, you must ensure users have opted in, giving you permission to contact them. The identifier used in the opt-in list must match the one defined in your channel integration For Email and SMS, either upload a daily subscriber list to an AWS S3 bucket or use API events. For App Push and Web Push, track opt-in events via API or script. |
Learn more about how to integrate each channel and manage opted-in users: |
Identify your visitors
Identify site visitors to link their Dynamic Yield user ID (DYID) with a unique ID used for cross-channel communications (CUID), such as a hashed email address or external ID.
You can do this using any of our identification events: Login, Signup, Newsletter Subscription, or Identify user.
Learn more about Matching Users Across Channels.
Notes:
- For the SMS channel, users are identified by the primary email address CUID, and the phone number should be passed as a secondary identifier.
- If you're using Reconnect for only Web Push or App Push, omni-channel events are not required.
- Learn more about our standard events and identifying users.
- For the event implementation schema and code examples, see our Developer Docs:
Login, Signup, Newsletter Subscription, Identify user
Create campaigns and set the triggers
Reconnect supports a variety of campaign types, including:
For each trigger, you can define conditions, target audience, wait times, cancellation rules, and message capping.
Learn more about how to create a Reconnect campaign.
Create campaign variations
Each campaign includes one or more variations, each delivering a different message. You can assign a different channel to each variation and control the percentage of user traffic allocated to each for A/B testing. Reconnect also supports channel prioritization strategies to optimize delivery based on urgency or content richness.
Learn more about how to create and optimize campaign variations.
Construct your messages
Messages include the content you deliver in each channel, tailored to that channel. They're built using JSON payloads and can include dynamic variables for personalization. You can use out-of-the-box templates or create your own and save them for reuse. Variables can pull information from user data feeds, product feeds, or recommendation strategies, and include the contextual trigger data, such as items left in the cart or items with a price drop.
Learn how to build messages for each channel and use variables effectively.
Localize your campaigns
Reconnect supports localized campaigns, enabling you to serve relevant, locale-specific content to each user. Localization setup includes:
- Creating a localized product feed.
- Setting localized page context:
- For script-based implementations, this is done in the page heading.
- For API-type sections, add an additional parameter in event API calls (details follow this list).
- Adding the languages you support in your section settings.
- Defining localized values for individual variables in each variation.
(Note: Localized variation behavior is the same across Experience OS applications).
Learn more in the dedicated article Multi-language Support.
For API-only implementations, you must send the user's locale code in your Event requests under context. Make sure to reference the correct language codes.
API-type implementation refers to sections defined when they were created as the type called API. If you are working with Experience Web, even if you only do API campaigns, this is not your implementation type.
Example:
curl --request POST \
--url https://dy-api.com/v2/collect/user/event \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--header 'dy-api-key: your-api-key' \
--data '
{
"user": {
"active_consent_accepted": false
},
"context": {
"page": {
"type": "HOMEPAGE"
"locale": "fr_FR"
}
},
"options": {
......
}
}
'Analyze your campaign
Reconnect provides detailed reporting on campaign performance, including metrics like send requests, click-through rates, purchases, and revenue. Reports are broken down by variation and channel, making it easy to see which combinations perform best. Attribution is based on user clicks and requires proper tracking setup. To ensure accurate reporting and attribution, it's important that you implement the required tracking during the implementation of each channel.
Learn more about Reconnect reports.