Adversus changelog
Adversus changelog
adversus.io

Journeys: Match value conditionally

 

New

  

If you sometimes lose track of your Journey because you branch out more than what's good for the overview of it all, we're here with some great news to simplify your Journeys.

We're introducing a new function that allows you to match several different values in one action, making it much easier to edit, add or delete values when changes occur.

Practically speaking, what happens is that you tell us how you want match to your apples with your oranges, and then give a name to your preferred orange, so you can continue working with it afterwards (here, the orange symbolizes one of your campaigns). Let's grab hold of an example that we, at Adversus, use on our own account:

From time to time, our sales team uploads leads manually using a form that sends the lead directly to Adversus. We then add the lead to the individual campaign of the sales rep who created the lead - so they can contact them themselves.

Previously, we had to create a branch to filter out each specific sales rep and then add it to the correct campaign. This made the Journey quite big, not to mention time-consuming to manage whenever changes occurred. It looked sorta like this:

image 443.png

Now, we're simply using the new match value conditionally action to create the scope for sorting the leads into the correct campaigns based on the lead owner field, hence avoiding branch after branch after branch. It looks like this:

Group 593 (2).png

Group 594.png

We start by choosing Campaign because our goal is to select which campaign the lead goes into. We're then filtering based on the Lead owner field, 'cause that's how we know who created the lead, e.g., if Dwight Schrute is the owner, then it needs to go to Dwight's campaign.

Under Else, we've chosen the Scranton Leads campaign, meaning that leads that, for some reason, don't match any of the criteria mentioned above are added to this "back-up" campaign.

Lastly, you must create a label for your scope to use afterwards. As you can see in the example, we're then adding the leads to a campaign by using the match value conditionally scope as the value in the campaign field. And now we're done!

If you're in need of some other use cases, here are a few:

  • Map customers into different campaigns based on their answers to a customer survey (instead of a branch for each outcome).

  • Assign leads with zip code 8000 to agent X and leads with zip code 9000 to agent Y, etc.

  • Change values to something that matches a specific API format, e.g., map lead status to a relevant status in your external CRM.

Get in touch with our support team if you need help!