1

I have a journey which is not pulling data from our data extension correctly.

The data in the data extension is correct but the email that has been sent out has a previous value.

I update the data extension using an automation, pulling data from salesforce via sql and the data updates in there as expected. The journey fires 5 minutes after the automation is run.

The emails in the journey are about a month apart so timing shouldn't be affecting this.

The "DevLaunchDate" in the data extension is the example that hasn't changed. It should say "Early 2020" but the email states "October 2019".

Data extension: enter image description here

enter image description here

Email:

enter image description here

Thanks in advance for any help.

  • How are you pulling in the field? Lookup function or just as a personalization string? – AnonWonderer Dec 18 '19 at 18:35
  • Just a personalisation string. – Emma Dec 20 '19 at 7:48
  • 1
    Ah - personalization strings will by default use 'Journey Data' (snapshot of the fields, detailed in the answers below). You'll need to use a Lookup for the most up-to-date values for all fields. Here's a link more specific to email: help.salesforce.com/… – AnonWonderer Dec 20 '19 at 15:36
  • @AnonWonderer - great thanks very much!! – Emma Jan 6 at 15:26
2

I would suggest you to use CONTACT DATA rather than Journey DATA!

For more info on this please find details here: When in Journey Builder what is the difference between journey data and contact data?

Where in you need to relate your DE to the CONTACT model.

| improve this answer | |
  • 2
    @Emma Yeah, using Journey Data takes a snapshot of your data at entry and no matter what changes you make to it after are not reflected in this data set. Using Contact Data will allow your data to be edited and the changes reflected inside the Journey. The caveat being that using Contact Data is slower and less stable (data can be removed, potentially causing errors or failures) than Journey Data. You can also change your email to pull via a Lookup() instead and this will allow it to pull in the updated info. – Gortonington Dec 18 '19 at 14:20
  • Hi, thanks for your reply. I am using contact data which is why this problem is so strange. Support are struggling with it too – Emma Dec 18 '19 at 14:54
  • Wow!... thanks @Gortonington for sharing the trick, a simple AMPscript function 'Lookup()' will do the trick! I was NOT aware of this. – Vishal Kumar C V Dec 19 '19 at 11:53

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.