Adobe Launch properties be categorised based on whether they use only page view tracking or also custom tracking ?

[KumarRishii]

Is there a way to identify or segregate over 100 Adobe Launch properties based on whether they use only Page view-level tracking or also include Custom Tracking (such as clicks, form submits, or custom Events)?

[Jennifer_Dungan · Accepted solution]

Unfortunately, I don't believe so... aside from maybe adding something into the name of the property...

There is no concept of keyword / tags in Adobe Launch (that could be a good idea to submit, but there's no guarantee that Adobe will add it.

You could create a separate documentation file that provides insights for each property... but that's not available to filter all properties with "x" or "y"

If I were you, I would consider a naming convention... Take something like your existing names, and add something like "(PV, C, FS, CE...)" to the end... I am using shortforms to keep the names shorter... but you could add the relevant details to each property, and add to that name if something new is added....

So you might end up with a list of properties that looks like:

• Property 1 (PV)
• Property 2 (PV, C)
• Property 3 (FS)
• Property 4 (PV, C, FS, CE)

Then if you need to find your properties with Form Submits, you can search for "FS".. this still might pull up other properties with those letter combinations... if that is an issue, you might need to get a little more creative with the naming convention, like using "R:PV" (for rule: page view) or "R:FS" (for rule: form submit), etc....

[Vinay_Chauhan]

Yeah, there’s no quick or native way in Launch to sort or filter properties based on whether they’re just doing basic page view tracking or also include custom stuff like clicks or form submits. It’s one of those things that would be super helpful, but just doesn’t exist out of the box right now.

What a few teams I’ve worked with have done is keep a separate tracker (Google Sheet or Confluence table) where each property is listed along with what types of tracking are implemented. It’s a bit manual at first, but once it’s set up, it’s easy to keep updated whenever a change is made.

Another option is to just open up a few of the properties and skim through the rules, if you see anything other than page load events (like event-based triggers or custom conditions), it’s safe to assume custom tracking is in play.

It’s not perfect, but a naming convention or tracker is usually the way to go when you’re managing dozens (or hundreds) of Launch properties.