Reconnect Custom campaigns are the most flexible campaign type. They enable you to define a wide range of user actions as triggers, making them ideal for engaging users based on behavioral signals beyond standard cart or product interactions.
Use cases include:
- Following up on a product of a specific brand added to the cart
- Engaging users who fired a custom event, such as completing a survey or adding an item to their wishlist
Trigger Logic
Trigger conditions
A custom campaign can be triggered based on:
- Category page visits (any or specific category)
- Product views (any, with property, or without property)
- Product added to cart (any, with property, or without property)
- Product Purchased (any, with property, or without property)
-
Custom events fired by the user, based on:
- The event name
- An event property
Wait time
- Defines how long after the trigger the message is sent
- The default wait time is 3 hours
Send to
You can target either:
- All users who meet the trigger condition
- Specific users based on audience filters (for example, new users or based on location)
Don’t send if (cancel conditions)
Cancel conditions are fully customizable.
For example, you can cancel the message if the user:
- Purchased any product
- Visited the site again
- Added another product to the cart
You can define any available event or behavior from the dropdown list in the campaign editor.
Priority logic
Custom campaigns do not compete with each other—all eligible campaigns will be sent.
However, you can give one custom campaign top priority by selecting Cancel all other messages if triggered, which stops all other Reconnect messages to the user (except for Change in User Attribute campaigns).
External events
Custom Reconnect campaigns can also be triggered by external (offline) events, such as:
- Returning a product in-store
- Contacting customer care
- Any other offline interaction reported back to Dynamic Yield
Requirements:
- The event must be reported with the user’s primary identifier (CUID)
- The user must have opted in to receive messages
- No additional online login, identify, or signup event is required at the time of the event
Offline event triggers enable true omni-channel engagement.
For more details, see Enrich User Data with External Events.
Message content configuration
Custom campaigns support the following variable types:
-
Items in cart
Display data about the items from your product feed, such as:- Product name
- Price
- Image
- Brand, category, or other custom attribute
-
Recently viewed items
Render details of recently viewed products using product feed data -
Recommendation blocks
- Use any strategy and set Reconnect App as the page type
- Contextual strategies can use cart items or recent views for context (configured in the Variables tab)
-
User data
Use fields from your User Data feed to personalize messages, such as loyalty status, region, or last purchase category.
FAQs
Q: Can a user receive multiple custom campaign messages?
A: Yes. Custom campaigns are non-competing, so multiple messages are sent if multiple triggers are satisfied, subject to the global cap of 5 messages per channel per user in 24-hours.
Q: What does “Cancel all other messages if triggered” do?
A: It provides a campaign with top priority and cancels all other eligible messages from both custom and non-custom campaign types, except for Change in User Attribute campaigns.
Q: Can I combine multiple triggers in a single custom campaign?
A: You can’t mix different trigger types (say, Product View and Event) in the same campaign, but you can use OR logic within one type.
Examples:
- You can create product view campaign that's triggered if the user adds product X, product Y, or product Z to the cart.
- You can create an event-based campaign that's triggered if the user fires Event 1, Event 2, or Event 3.
- You can't mix a product trigger and an event trigger using OR.
Q: Can I target event properties? Say, if a user added an item of a particular brand to their cart?
A: Yes. Trigger conditions can include event properties defined in your tracking schema.