Copy/Replicate Adobe Launch Properties (Templates)

[#1]

Being able to quickly copy a templated launch property would allow for quick standups of scripts ready to launch analytics, experience cloud id service, target, ads, facebook pixels or all of the above. Our use case comes from wanting to get a standardized, unique script so we can quickly add adobe analytics to a number of websites. This is extremely helpful for clients/agencies managing many (100+) websites and report suites.

[#2]

I saw in the Feb 12th release notes that you can now copy data elements, rules, and extensions to another Launch Property. This is a big win but copy an entire launch property and everything inside of it would be huge. We currently have 96 launch properties. We have to maintain library versions for 3+ extensions across all these. Making progress but looking forward to more.

[#3]

Or have a base property where you can inherit from! So that you don't have to change 96 launch properties when you have to change a rule

[#4]

Looks like being able to copy the whole property won't make our Summit target, but it is still coming.

[#5]

Are there any updates on the whole Property copying functionality? Is there still a plan to implement this?

[#6]

Yes, this is still part of the plan.  We had a few other things come up that had to be done first.

[#7]

This is nearing completion.  Code is wrapping up, then we'll start testing.  Probably 2-3 weeks out.

[#8]

Hi,

Appreciate if you can share any tentative timeline for this functionality to be rolled out?

Regards,

Gagan

[#9]

I'm pretty sure this is set for release tomorrow =)

[#10]

This was delivered on October 8, 2019.

[#11]

@thebenrobb This is great to see. Has there been any discussion about the support of copying a property from one ORG to another ORG? This could be very valuable to the Adobe Partners Program.