#Personalization2 personnes en discutent

Hey Gokul, 

Salesforce's own Decisioning API diagnostics doc covers exactly this pattern. Two documented causes for targeting rules not evaluating as expected: 

1. Targeting rules were misconfigured, check the rule configuration in the UI directly for the affected decision 

2. Rules couldn't be evaluated at runtime due to unexpected data format in the associated profile data graph, this is the "inconsistent" part you're seeing, if the visitor's profile data doesn't match the expected format/type the rule is checking against, evaluation silently fails for that individual even though the rule looks correct in the builder 

Since you're seeing inconsistent results (works for some eligible users, not others) rather than a total failure, cause #2 is more likely, worth checking the actual Data Graph feeding your targeting rule for inconsistent or missing attribute formats across profiles, rather than assuming the rule logic itself is wrong. 

Practical next step: check the Decisioning API diagnostic codes returned for the failing requests (via PersonalizationLog for unauthenticated requests), that'll tell you definitively whether it's a rule misconfiguration or a data format mismatch at runtime, rather than guessing from the UI alone. 

Reference:

Hey Gokul, 

Salesforce's own Decisioning API diagnostics doc covers exactly this pattern. Two documented causes for targeting rules not evaluating as expected: 

1. Targeting rules were misconfigured, check the rule configuration in the UI directly for the affected decision 

2. Rules couldn't be evaluated at runtime due to unexpected data format in the associated profile data graph, this is the "inconsistent" part you're seeing, if the visitor's profile data doesn't match the expected format/type the rule is checking against, evaluation silently fails for that individual even though the rule looks correct in the builder 

Since you're seeing inconsistent results (works for some eligible users, not others) rather than a total failure, cause #2 is more likely, worth checking the actual Data Graph feeding your targeting rule for inconsistent or missing attribute formats across profiles, rather than assuming the rule logic itself is wrong. 

Practical next step: check the Decisioning API diagnostic codes returned for the failing requests (via PersonalizationLog for unauthenticated requests), that'll tell you definitively whether it's a rule misconfiguration or a data format mismatch at runtime, rather than guessing from the UI alone. 

Reference:

Hi @Christopher Daniel Vargas Cruz

Check out this document it includes some key features and aspects of Salesforce Data Cloud.

https://kizzyconsulting.com/salesforce-data-cloud/

Hope this helps

Thankyou

Saurabh

Are you a Salesforce partner? Please check the conditions below.

https://help.salesforce.com/s/articleView?id=000390865&type=1

As outlined in this help document, if you are a Salesforce partner, please request permission to use Marketing Cloud Personalization from the alliance representative at your company. If you cannot find the alliance representative at your company, we recommend consulting with a Salesforce AE whom you know.