Ability to create an audience based on the the Journey or Campaign Name, not just the Journey ID and Message Name | Community
Skip to main content
Level 4
January 29, 2025
Investigating

Ability to create an audience based on the the Journey or Campaign Name, not just the Journey ID and Message Name

  • January 29, 2025
  • 5 replies
  • 579 views

Description -

We need the Abiltiy  to determine the engagement of customer based on the the Journey or Campaign Name in an audience.  In particular, to state, if the Journey Name starts with/contains "xyzFY25..."

 

Why is this feature important to you -

Currently, we can only use the Journey ID, which means that we need to manually update the audience each time a different journey would be applied. 

When a Journey is updated and republished this creates a different ID, more additional work. 

 

How would you like the feature to work -

Journey Name would be a variable when creating Audiences and searching for an event. 

 

 

Current Behaviour -

Only the Journey Version is available.

5 replies

TylerKrause
Adobe Champion
Adobe Champion
January 31, 2025

Great idea! It is very frustrating to have to go lookup the IDs and manage them instead of being able to utlilize the Journey Name. Great suggestion!

Sukrity_Wadhwa
Community Manager
Community Manager
April 17, 2025
No text available
Sukrity Wadhwa
May 2, 2025

I also support this Idea! Additional it would be great to use the tags of a journey / campaign for filtering.

Adobe Employee
September 5, 2025

Using name labels for this could be a bit tricky as they may not always be unique or may change. 

 

Couple of alternatives we are considering. Let me know your thoughts. 

1) Add option at end of Action Campaign to auto-create a retargeting audience. Spawns a new audience upon activation. 

2) Allow tags or other upcoming metadata fields to be a catch all for creating an audience - i.e. any users that went through a "Welcome" journey or campaign. 

 

Let me know your thoughts on this. 

Caveman77Author
Level 4
September 8, 2025

1) Using tags could be an options.  That way we could label a series of journeys and include/exclude anyone that is in the journey or recently completed.  This would avoid having to search for the Journey ID.   

 

The naming of a journey changes subtly by versions, so as long as we could use the the ability to refine by using  "contains" or "starts with" this would work for our needs.  

 

What is frustrating is that we have a process that export leads to our CRM.  Every time we modify some of the leads journeys that are qualifies, we have to 'remember' to update this segment that exports. I would not have to do this if I could say export anyone who has been in a journey where [JourneyName] contains "xyz"