How to get SNDS and JMRP data for Salesforce/ExactTarget users when facing deliverability issues?
Michael Ko
Co-founder & CEO, Suped
Published 3 Aug 2025
Updated 19 Aug 2025
7 min read
When managing email campaigns through a robust platform like Salesforce Marketing Cloud (formerly ExactTarget), deliverability challenges can arise unexpectedly. A common issue is email blocking due to spam or sender reputation problems, especially when sending to Microsoft domains like Outlook.com or Hotmail. One of the most effective ways to diagnose and mitigate these issues is by leveraging data from Microsoft's Smart Network Data Services (SNDS) and the Junk Mail Reporting Program (JMRP).
However, obtaining this crucial data when using a third-party email service provider (ESP) such as Salesforce/ExactTarget can be a bit tricky. Unlike managing your own mail servers, where you have direct control over IP registration, ESPs often manage the underlying infrastructure. This means you might not have direct, immediate access to the SNDS portal or JMRP reports.
This article will guide you through the process of getting the SNDS and JMRP data you need to troubleshoot and improve your email deliverability, specifically as a Salesforce Marketing Cloud or ExactTarget user.
Understanding SNDS and JMRP for ESP users
SNDS provides data on your IP reputation, spam complaint rates, and bulk email filtering decisions, while JMRP delivers copies of actual junk mail reports from users. For anyone engaged in email marketing, these services are invaluable. They offer a direct line of sight into Microsoft's perception of your sending practices. Without this data, you're essentially flying blind when it comes to diagnosing why your emails might be landing in the spam folder (or junk folder, as some refer to it) or being blocked entirely.
When you use an ESP like Salesforce Marketing Cloud, the sending IP addresses belong to the ESP, not directly to you. This is why you cannot simply register your domain or email address in SNDS directly. Instead, Microsoft requires the owner of the IP address (in this case, Salesforce/ExactTarget) to grant you permission to view the data. This often involves a process where Salesforce needs to confirm your authorization, sometimes through a Docusign agreement or similar verification. Salesforce themselves recommend this process.
The type of IP you're using within Salesforce Marketing Cloud also plays a role. If you are on a dedicated IP address, obtaining SNDS/JMRP access is usually more straightforward as your sending reputation is isolated. On a shared IP, the data reflects the cumulative sending behavior of many clients, making it harder to pinpoint your specific impact on deliverability. However, even with shared IPs, understanding the overall health can provide valuable context. For more on this, you can look at how reliable SNDS data is.
IP Type
SNDS/JMRP Access
Deliverability Impact
Dedicated IP
Generally easier to get explicit access via ExactTarget or Salesforce. Data reflects only your sending.
Reputation is solely yours. Issues directly attributable to your sending practices. Easier to troubleshoot.
Shared IP
Access is less common and data is aggregated. May require more persistent requests or be unavailable.
Reputation is shared among many senders. Issues can be caused by other users on the same IP block. Harder to isolate your impact.
Requesting SNDS and JMRP access via Salesforce/ExactTarget
The primary avenue for Salesforce Marketing Cloud and ExactTarget users to get SNDS and JMRP data is through their Salesforce support team or deliverability specialists. Salesforce has a dedicated deliverability team that works closely with major mailbox providers, including Microsoft. They are typically well-versed in the Microsoft SNDS enrollment process for their IP ranges.
When contacting Salesforce support, be explicit about your need for SNDS and JMRP data for your dedicated IP addresses. You will likely need to provide specific authorization, confirming that you are the legitimate owner of the email program using those IPs. This often involves a simple statement or a signed document (like a Docusign agreement) that Salesforce then submits to Microsoft to verify your request. Remember that Salesforce Marketing Cloud offers various reports, but these may not provide the granular insight you get from SNDS.
It is important to note that the Microsoft Outlook.com Deliverability Team can sometimes be slow to respond. This is a common sentiment in the industry, often due to high volume or specific internal processes. Persistence and clear communication with your Salesforce contact are key. They have established relationships and know the correct channels to escalate requests, which can expedite the process. For more information, you can find common issues with Microsoft SNDS and how to address them.
Best practice for requesting access
Provide clear authorization: Clearly state your domain and the dedicated IP addresses in question.
Reference client representative: Offer to have your Salesforce client representative confirm your authorization, providing their email address for direct verification.
Be persistent: If you don't receive a response within a reasonable timeframe, follow up with Salesforce support.
Interpreting and utilizing SNDS and JMRP data
Once you gain access to the SNDS and JMRP data, the real work of improving deliverability begins. SNDS provides daily statistics on your sending IPs, including their reputation status (Good, Fair, Poor), spam complaint rates, and data on email filtering. JMRP provides actual copies of emails that Microsoft Outlook.com users have marked as junk.
Analyzing this data requires attention to detail. Look for trends in complaint rates: sudden spikes often indicate a problem with a recent mailing or segment. A poor IP reputation in SNDS means your emails are likely being heavily filtered or blocked. The JMRP feedback loop is crucial for identifying which specific campaigns or content trigger spam complaints. You can leverage these insights to refine your segmentation, content, and list hygiene practices, thereby improving your overall email deliverability.
One common challenge users face is discrepancies between SNDS data and Salesforce Marketing Cloud's internal reports. This can happen due to varying reporting methodologies or delays in data synchronization. If you notice significant differences, engage both Salesforce support and cross-reference with other deliverability metrics to get a complete picture of your sending health. You can resolve SNDS and SFMC discrepancies with proactive steps.
SNDS Data points
IP reputation: Good, Fair, or Poor. Direct indicator of trust.
Complaint rate: Percentage of users marking your emails as junk.
Spam trap hits: Indicates list quality and acquisition practices.
JMRP Data points
Actual junk mail reports: Copies of emails marked as junk, including headers.
User feedback: Directly helps identify content or audience issues.
Actionable insights from SNDS
Improve segmentation: Target more engaged users to lower complaint rates.
While securing SNDS and JMRP data from Salesforce Marketing Cloud or ExactTarget might require a bit of back-and-forth, the insights gained are invaluable for maintaining a healthy sending reputation. This data empowers you to make informed decisions, optimize your email campaigns, and proactively address deliverability issues before they escalate into widespread blocking or placement in the junk folder.
Remember that consistent monitoring is critical, not just when you encounter a problem. Regularly reviewing your SNDS metrics, even if they look good, can help you detect subtle shifts in your sending reputation and respond quickly. This proactive approach is a cornerstone of effective email deliverability management, regardless of the ESP you use.
By understanding the nuances of how Microsoft views your email program through SNDS and JMRP, and by working collaboratively with your Salesforce team, you can significantly improve your chances of reaching the inbox and maximizing the effectiveness of your email marketing efforts. This strategy helps you resolve Microsoft domain deliverability issues and avoid being added to a blacklist (or blocklist).
Keep in mind that factors such as GDPR compliance can also influence deliverability, as mailbox providers are increasingly sensitive to user consent and data privacy. Microsoft (Outlook.com) can be particularly sensitive in this regard. Ensuring your practices align with both regulatory requirements and ISP guidelines is essential for long-term success.
Views from the trenches
Best practices
Actively engage Salesforce deliverability support for SNDS/JMRP access.
Clearly communicate your need for specific IP reputation data.
Implement feedback from JMRP to refine content and audience targeting.
Regularly monitor your IP reputation and complaint rates in SNDS.
Common pitfalls
Attempting to register ESP IPs directly with SNDS, leading to rejections.
Underestimating the time and persistence needed to get SNDS/JMRP access.
Ignoring JMRP feedback, which can exacerbate spam complaints and blocks.
Not understanding the difference between dedicated vs shared IPs for data access.
Expert tips
Use a Docusign or formal authorization if required by Salesforce for SNDS access.
Reference your Salesforce client representative when requesting data.
Focus on the 'abuse@exacttarget' email address for direct inquiries.
Be patient, as the Outlook.com Deliverability Team can be slow to respond.
Marketer view
Marketer from Email Geeks says that they tried joining SNDS and JMRP and even completed Docusign, but they could not see any data, suggesting Salesforce/ExactTarget might need to grant permission.
2018-06-01 - Email Geeks
Marketer view
Marketer from Email Geeks says that some ESPs allow direct access to JMRP/SNDS for dedicated ranges, but Salesforce/ExactTarget might charge for access.