Skip to main content

Hi there! We’ve moving into Iterable and working to create/recreate journeys we had elsewhere. And… we’re getting caught on how to compare variables within Journey elements. For example: 

We have a journey workflow that begins when an event (actionGetStarted) occurs. The actionGetStarted has an ID (actionGetStarted.id). Once the workflow has complete, we send that workflow into another. Ideally, if a person has not taken an action with X days (which results in actionSubmission event, with actionSubmission.actionId) then we’d send them a reminder. 

Using the various blocks, like yes/no, hold until, etc., I see we can check against one of those two -- for instance, I can select actionGetStarted.id from the incoming journey event - but I have no way to designate that it should check for the second item, which is actionSubmission.id, given that the input box is checking for plaintext. 

Is there any way/means to use that second box as an event comparator? 

Thanks!

 

Hi there,

Hold until tiles don’t currently support dynamic filtering.
You should, however, be able to accomplish this in a yes/no filter tile by selecting the event that does not trigger the journey on the left hand side of your query, and the value from the event that does, on the right-hand side of the query, via a merge parameter. 
So in the case of your example, if the journey is triggered by the actionGetStarted event, your filter tile would look something like:
actionSubmission.actionId = {{id}} 
where {{id}} will be the id value from the actionGetStarted event (when calling an event field in a journey triggered by that event, we don’t reference the event name in the merge parameter, as the only data Iterable can dynamically access in that filter is the payload from that triggering event).
For additional questions and troubleshooting, our support team should be able to assist you further with this query. Please submit a ticket by emailing support@iterable.com or from within the Iterable UI, click the question mark in the top-right corner, and select “submit a ticket” from the dropdown

Best,

Heather

Thanks so much! I believe that’s working -- have to test across the complexity of use-cases but at first glace it’s good to go. Much appreciated!

Reply


Terms & ConditionsCookie settings