Understanding the Issue
The issue at hand is that an existing identity resolution rule stopped working, and a new rule with the same criteria works fine. This suggests that the problem might not be with the rule itself, but with the underlying data or configuration. We have seen this happen when there are changes to the data sources, or when the configuration of the identity resolution rule is modified.
Root Cause Analysis
The root cause of the issue is likely due to changes in the underlying data or configuration, such as updates to the data sources, or modifications to the identity resolution rule configuration. This can cause the rule to fail, even if it was working previously.
Troubleshooting and Resolution
To troubleshoot the issue, it is essential to review the data sources, configuration, and any recent changes made to the identity resolution rule. One possible solution is to re-create the rule or reassign a new one to existing assets. Additionally, it is crucial to run tests without spiking credit consumption, especially in a sandbox environment.
To reassign a new identity resolution rule to existing assets, such as segments, flows, and data graphs, you can follow these steps. First, create a new identity resolution rule with the same criteria as the failing rule. Then, update the existing assets to use the new rule. This can be done by editing the asset configuration and selecting the new rule.
Code Example
IdentityResolutionRule.js
var rule = { "name": "New Rule", "criteria": [ { "attribute": "email", "operator": "equals", "value": "[email protected]" } ]};
Best Practices for Consumption Optimization
To run tests without spiking credit consumption, it is essential to use a sandbox environment and to monitor the usage and consumption of credits. You can do this by reviewing the usage reports and adjusting the test parameters to minimize the consumption of credits.
Heads up: When troubleshooting identity resolution rule issues, it is crucial to be mindful of credit consumption, especially in a sandbox environment.
Checklist for Resolving Identity Resolution Rule Issues
- Review the data sources and configuration for any recent changes
- Re-create the identity resolution rule or reassign a new one to existing assets
- Run tests in a sandbox environment to minimize credit consumption
- Monitor the usage and consumption of credits
- Update the existing assets to use the new rule
- Review the usage reports to adjust the test parameters
Frequently Asked Questions
What is the root cause of the issue?
The root cause of the issue is likely due to changes in the underlying data or configuration.
Can I reassign a new identity resolution rule to existing assets?
Yes, you can reassign a new identity resolution rule to existing assets, such as segments, flows, and data graphs.
How can I run tests without spiking credit consumption?
You can run tests in a sandbox environment and monitor the usage and consumption of credits to minimize the consumption.
What are the best practices for consumption optimization?
The best practices for consumption optimization include reviewing the usage reports, adjusting the test parameters, and monitoring the usage and consumption of credits.
Need help shipping this in production?
Genetrix builds and untangles Salesforce Marketing Cloud and Agentforce setups for teams that want it done right the first time. If anything in this post sounds familiar, talk to us before it ships.