1

I have configured a journey based on a data extension which has External id as unique primary key and is sendable and Email Address relates to subscriber key. In the contact builder data model, i have used populations and since only the primary key attribute can be linked to contact key, External id is linked to contact key.

While testing the JB using sample data (not in test mode), contacts are getting injected into the journey and the decision split activities based on Even data is working fine. But decision split based on Contact data (data at the time of evaluation) is getting failed and the contact always takes the false path. As per my requirement, we have atleast 3 contact data based decision splits to send mails only if they have not registered for a program.

I tried out a similar JB by creating another data extension with Email address as primary key and rooting the population based on Email address and decision split based on contact data is working fine. My client is not willing to change the primary key as External id would the unique identifier.

Has any one experienced similar issue or got a solution/work around for this.

0

I've seen this behavior before. Essentially, Decision Split Activities that are based on Contact data fail to evaluate when in Test mode and all the Contacts are routed down the same branch. When you Activate the Interaction, the Decision Split Activity functions correctly.

I would check this by Activating the journey and use some sample records to validate this.

  • I have tried activating the journey and use sample records. Its failing in the actual interaction. – Ganesh Kumar Sep 21 '16 at 10:42
  • I assumed that you were in test mode as you stated 'While testing the JB...'. Is/are the Attribute(s) that you are using in your Decision Split Activity based on a 1:1 relationship in your Contact model? – Eliot Harper Sep 21 '16 at 10:45
  • Updated the desc that was misleading. Yes all my contacts are on a 1:1 relationship – Ganesh Kumar Sep 21 '16 at 11:00
0

Salesforce support has able to find the root cause of the issue. Issue is that in the data extension, subscriber key has been set as Email Address where as in populations, contact key is mapped to primary key which is external id.

For contact data to work, both subscriber key and contact key should be same. It worked as soon as i updated the subscriber key to External id.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.