Adobe Tags / Event Forwarding Library - Enhancement Request

Enhancement Summary
Requesting a product enhancement in Adobe Tags to support the ability to transfer, copy, or promote selected components from one library into another library within the same property. This capability would allow users to move changes such as data elements, rules, extensions, and related configurations between libraries without manually recreating or porting them.

Current State
Adobe Tags currently allows teams to create and manage libraries as part of the publishing workflow. However, when changes are created in one library, there does not appear to be a native way to push or transfer those changes into another existing library.
As a result, teams are required to manually recreate or port data elements, rules, and other configuration changes from one library to another.
 

Business Problem
The current manual process introduces unnecessary operational risk and inefficiency.
Manual porting between libraries can result in:

• Missed data elements or rules
• Inconsistent configuration between libraries
• Human error during recreation
• Increased validation and QA effort
• Delays in release timelines
• Higher risk of production defects
• Difficulty managing parallel workstreams across multiple libraries

This is especially impactful for teams managing complex tagging implementations, where multiple rules, data elements, and environment-specific changes may need to be coordinated across libraries.

Requested Enhancement
Add native functionality in Adobe Tags that allows users to transfer, copy, or promote changes from one library into another library.
Ideally, the enhancement would support:

Selecting one or more rules from an existing library and copying them into another library
Selecting one or more data elements from an existing library and copying them into another library
Including related dependencies automatically, such as referenced data elements or extension configurations

• Providing a comparison view before transfer
• Identifying conflicts when the target library already contains a different version of the same component
• Allowing users to choose whether to overwrite, skip, or create a duplicate
• Preserving change history or audit visibility where possible
• Supporting role-based access controls consistent with existing Adobe Tags permissions

Example Use Case
A team creates and validates several new rules and data elements in Library 1. Later, the team determines that those same changes are also needed in Library 2, which contains a separate release package.
Today, the team must manually recreate those rules and data elements in Library 2. This creates risk that the copied configuration may not match the original implementation.

With the requested enhancement, the team could select the approved changes from Library 1 and transfer them directly into Library 2, reducing manual effort and ensuring consistency and also supports multi- user model in Adobe Tags

If this is already available, can someone please point me in the right direction on how to solve for this - that would be perfect!

Thanks,

Ty