One Launch property, governed

The situation

Our Adobe Launch (Experience Platform Tags) property has years of rules, data elements, and extensions in it, and nobody who set most of them up still works here.

The pain

Every proposed change carries hidden risk, so the team either freezes the property out of fear or breaks something they didn't know was connected.

What we implement

We audit every rule, data element, and extension in the property against what the site actually runs today, clean up what's dead or duplicated, and put a lightweight review process around future publishes - governance for what's called tag management.

What you get

• A Launch property where every active rule maps to something real on the site.
• A documented process so the next change doesn't need archaeology first.
• Fewer surprise regressions when a new tool or campaign gets added.

Illustrative, not a measured result: an enterprise property with rules dating back to the DTM era might find a meaningful share of its active rules no longer firing on any live page.

FAQ

Do we need to rebuild our Launch property from scratch?

Rarely. Most properties need cleanup and governance, not a rebuild - dead rules removed, duplicated data elements consolidated, and a review step added before publish. A full rebuild is only worth it when the property is small enough that starting clean is faster than untangling it.

How do you know which rules are actually still needed?

We check what fires on real, current pages using the Adobe Experience Platform Debugger and publish logs, not assumptions from the rule names. A rule that hasn't fired anywhere in a normal traffic sample is a strong candidate for removal, but we confirm before we cut.