As email marketers, we often obsess over open rates and click-throughs. But for operational emails — the password resets, shipping confirmations and two-factor authentication (2FA) codes — there is a much more fundamental metric: Did it actually go out?

High-velocity transactional sends operate on a unique level of urgency. When a customer is waiting for a security code to log in, every second is vital. In a high-volume, high-speed environment, the journey of an individual message can be complex. Standard aggregate reports are excellent for general performance. However, for mission-critical requests, brands often require a more granular, individual lifecycle view in real time. This is where Transactional Reconciliation comes in. 

Transactional Reconciliation is a special feature in Marketing Cloud Engagement released last year that provides complete visibility into your important transactional messages, such as password resets, order confirmations and deal alerts. Transactional Reconciliation works like a flight recorder. It tracks every attempt to send an email or SMS. If a message is blocked or queued, it can tell you exactly why and when it happened, usually within 15 minutes. This way, you never have to wonder if a crucial email was sent.

By using the _ReconcilableDispositionView data view, you gain full visibility into three critical states:

• Queued (0): Messages remain in this state from the moment they are triggered until they are processed and sent
• Sent (1): Successfully sent from the platform
• Not Sent (2): Blocked by a filter, exclusion list, system error or List Detective

Let’s take a look at how to use this tool to get better insights into your email marketing. 

Why Transactional Reconciliation matters for your email marketing

Beyond technical tracking, this feature offers strategic value for marketers and brands:

• Protects customer trust: Reliability is crucial for transactional emails and SMS. If a customer doesn’t get their password reset, they can’t use your product. Reconciliation ensures you find and fix breakages before they erode trust.
• Reduces support costs: Proactive monitoring of Not Sent statuses (Disposition 2) allows you to resolve data issues before the customer ever picks up the phone to call support.
• Provides regulatory compliance: In highly regulated industries, you often need an audit trail proving that mandatory notices were attempted. This feature provides the “proof of attempt” that standard delivery logs might miss.

How to get started with Transactional Reconciliation: A step-by-step guide for new users

If you’re ready to move from “standard” to “reconcilable” sends, here’s how you set it up for the first time:

1. Create a specialized audience: Navigate to Email Studio and create a new Data Extension. You must select Create from Template and choose the Sendable_Reconcilable_Data_Extension. This adds a mandatory MessageKey field.
2. Enable High Throughput Sending (HTS): If you are using Journey Builder, ensure HTS is enabled in your Journey Settings. This is the engine that allows reconciliation to run.
3. Configure delivery options: Within your email activity (Journey Builder) or Send Definition (Email Studio), look for the Transactional Reconciliation checkbox.
4. Set an expiration window: Choose a timeframe (1–72 hours). This tells the system when to “give up” on a retry and mark a message as Expired. For a 2FA code, set this to 1 hour; for a shipping update, 24 hours is usually better. Crucially, setting this window provides a guarantee from the system that once the time is up, the message will not be sent, preventing users from receiving stale or confusing information after it’s no longer useful.

For more information, visit our Transactional Reconciliation Help Page.

How Transactional Reconciliation can scale your email strategy

If you’re already using this feature, here’s how to take your reporting to the next level:

• Automated archive: Because the system only stores reconciliation data for seven days, set up a daily SQL query in Automation Studio. Move data from _ReconcilableDispositionView into a permanent Reconciliation Archive Data Extension.
• The not sent alert: Build a filter to find all Disposition = 2 (Not Sent) entries. If a specific error code (like a data binding error) spikes, you can set up a Slack or email alert for your dev team.
• REST API integration: For developers, ensure your /messaging/v1/email/definitions payload includes isReconcilable: true. You can pass your own unique MessageKey from your external system to tie Marketing Cloud Engagement logs back to your internal database perfectly.

4 best practices for Transactional Reconciliation

If you are using this feature, follow these four tips to get the most benefit from it:

1. Standardize your message keys: While the system can automatically generate a MessageKey for you, you have the option to provide your own when you need to reference an external system. For example, if you use a unique ID from your internal order management system as the MessageKey, your customer service team can easily bridge the gap between a missing order email and the exact status in Marketing Cloud Engagement.
   
2. Prioritize high-value journeys first: You don’t need to enable reconciliation for every single send. Focus on high value journeys first, like account registration, payment confirmations, and security alerts. This ensures your data views remain clean and focused on the messages where 100% delivery is non-negotiable.
   
3. Export your data weekly: The system keeps reconciliation data for only seven days to remain efficient. If you need to retain records for legal or audit purposes, set up an automation to move this data into a permanent archive every 24 hours.
   
4. Watch the “Not Sent” disposition: In your reporting, specifically filter for Disposition = 2 (Not Sent). This is your fix-it list. It shows you VIP clients who were blocked by accidental exclusions or list filters, allowing you to address the issue immediately.

Transactional Reconciliation moves you from guessing to knowing if your emails and SMS messages were sent. By providing a granular look at why messages fail to leave your platform, you can proactively manage your most important customer touchpoints. That could mean the difference between keeping a customer and losing them – and staying a step ahead of your competition.