Dynamic Tags in Journeys
under review
C
Cameron Wheatley
Allow tags to be added (and created) in journeys that are based on a merge strategy e.g. “Add tag = {{latest_activity.some_field}}”
So when a journey is triggered by a salesforce activity a tag can be added that pulls in the value of one of the activity attributes.
Reason this is useful is so we can use those tags to target within liquid code, that doesn't work on activity data. Another solution would be to make liquid code work using activity attributes beyond 30 days if that's simpler.
Log In
Peter Bartlett
marked this post as
under review
Peter Bartlett
Hi Cameron Wheatley thanks for the suggestion, would you mind sharing more details on the entire flow you are hoping to achieve here? (Feel free to share via support if you prefer). You mentioned you want to add liquid based on members having a tag, or preferably use it based on activity attributes. The 30-day limit you refer to only applies in some scenarios, so understanding the whole flow, along with expected timelines between when events could happen, would help me better understand whether anything we have now could achieve this for you, or what the best feature update would be.
Thanks
C
Cameron Wheatley
Peter Bartlett thanks Peter. Basically in our Salesforce, donations are tracked as 'Opportunity Won', this activity has a field called 'Campaign' which identifies which appeal the donation was a part of. We'd want to use liquid code to show specific text within email to people based on this 'Campaign' field on that activity. Our current solution is to set up a new audience for each new donation campaign so we can use the audience to target those donors with the liquid code ... but this requires us to remember to create a new audience for each new donation appeal. A journey would be useful if it could take the 'Campaign' field on the 'Opportunity Won' activity and add that as tag to the person ... then it would just be one set and forget journey and all donors would get tags based on their donations which we could use with the liquid coding.
Peter Bartlett
Cameron Wheatley: That makes sense, though I think you can already achieve this without needing tags or audiences.
If you have a journey that is triggered off "Opportunity won occurs", we keep the details of that activity for the duration of that journey, regardless of any new opportunity activities come through for that contact.
So if you have an email within that journey where you want to utilise the
Campaign
field to populate appropriate text to the contact, you can do that like this (note, the exact liquid ID for the campaign attribute might differ slightly in your account):"Thanks for your donation to
{{ activity.salesforce_custom.opportunity-won.campaign }}
, you are helping make a real difference."^ This is where you directly insert the campaign name in the email.
If you prefer to use the campaign to show/hide certain material, you can use it in a conditional statement instead:
{% if activity.salesforce_custom.opportunity-won.campaign == "Feb fundraiser" %}
Content for members of this campaign
{% else %}
Content for everyone else
{% endif %}
You would need to use liquid code like the above if you use a tag or audience anyway, but this way you don't need the extra step of dynamically adding a tag or audience to people first before your email content will work.
C
Cameron Wheatley
Peter Bartlett ah okay, that makes sense. Although we need to use this information across a few different teams and lots of different communications, so only being able to access it within a single journey is not ideal - but still good to know!
Peter Bartlett
Cameron Wheatley: Glad it helps. The other thing you can do, the Campaign attribute should be available as a field on the contact (this will always be set to the campaign from the latest Opportunity Won activity), and you can use this for filtering, and reporting.
The field is called
Opportunity campaign