You can view detailed reports with information about the performance of each Reconnect campaign.
Open a report
In Reconnect › Campaigns, hover over a campaign, and click View Report .
View report data
The Reconnect campaign report shows the number of users who triggered the campaign, the number of messages sent, and the purchases and revenue generated as a result. Learn more about Dynamic Yield reports.
Variation performance
The table displays the test results by variation and metric, with results based on the primary metric as the default. You can add metrics to display by clicking Metrics.
For Reconnect campaigns, the following metrics are available:
- Send Request: The number of times Dynamic Yield sent an API request to your messaging vendors.
- CTR: The total number of message clicks divided by the total number of impressions (if reported back to Dynamic Yield using a Tracking Pixel, this is available only for emails).
- Purchase: The total number of purchases attributed to users who clicked the message. Purchases are attributed if they occur after the user clicks the message but before the end of the attribution window.
- Revenue: The revenue attributed to users who clicked a message in this variation. Revenue is attributed if a purchase occurs after the user clicks a message but before the end of the attribution window (defined in the campaign’s Settings tab).
All metrics are normalized by the number of unique users allocated to the campaign variation (except for CTR) to get the average metric per user.
Note: The metrics of attributed events (such as Purchases and Revenue) track user actions on your site or app that occur after clicking a message. To ensure that this metric is accurately reflected, clicks must be reported back to Dynamic Yield using a tracking link for emails or push tracking for push notifications. (SMSs sent via Reconnect that have links in their content are automatically tracked, so no further action is required.) In addition, the user must be identified for the events to be attributed to the message.
Note: Campaigns created before December 14th, 2025 only measure the number of purchases, revenue, and add-to-cart events attributed to the campaign.
Channel performance
This part of the report provides a focused view of the performance of each channel, in each of the variations in the campaign, for each of the metrics. All the metrics you've added to the report are automatically added to the report's Variation Performance and Channel Performance sections.
Note: Unlike metrics in the Variation Performance dashboard, where all users who were allocated to a variation are counted, in this dashboard, all metrics relate only to users to whom a message was sent in the specific channel (a user can be allocated to a variation in a campaign, but not be opted-in to 1 or more channels in that variation).
FAQs
Why are the Purchase and Revenue metrics showing 0 events?
Attribution for Reconnect campaign begins only after a user clicks a message. If you're using an integration with one of the supported vendors, you should make sure the clicks are correctly reported to Dynamic Yield using a tracking link for emails or push tracking for push notifications.
In addition, users must be identified when making the transaction for Dynamic Yield to be able to attribute the events properly. Make sure an identification event is implemented (learn more).
I'm testing variations with different messaging channels, and the number of send requests in the Channel Performance section is lower than in the Variation Performance. Why is that?
Different channels can have varying opt-in rates among users. When a user activates a Reconnect campaign, we ensure they are opted in to at least one of the channels involved in the campaign. To maintain test integrity, users are assigned to variations regardless of the channels they are opted into. This means that a send request is counted in the Variation Performance section because the user was assigned to a variation, but not in the Channel Performance section because the message wasn't actually sent.
This approach keeps the test fair. Users are assigned to variations based on the traffic share you set, even if they aren’t opted into all channels. This enables you evaluate each channel’s performance based on actual message delivery.
Why is the number of Send Requests in the Reconnect app grid different than in the campaign report?
The Reconnect app grid includes the list of your campaigns and provides a quick view of how many send requests were made in the past 7 days, while as the Campaign Report includes the overall performance of the selected test version, which might be different timeframe than the last 7 days.
Note that if you change the report timeframe to include only part of the test duration, you'll see only the users who first triggered the campaign during that period and the events they generated. Learn more about working with custom time ranges.