Do you know you can fix your live website issue using adobe launch.

Hey @amruthesh_ag,

Yep! I've used Launch this way before.

One such example was to clear some cookies for an A/B test that wasn't designed the best... they used the A/B tool to set a cookie, then if our developers saw the cookie, they showed the alternate page...in theory, it wasn't a bad approach, but the problem was that we had to stop the test early.. which... oops.. all the users still had the cookie. So it came down to, do we do a hot fix to take out the logic for the page variations...until I suggested using Launch to nuke the cookie. We took the second approach and had a resolution within 30 mins.

But, I would like to mention @amruthesh_ag this isn't really an "idea"... but more of a discussion..  Ideas are basically for the Adobe product team to try and push new features into the product roadmap.  If you are okay, I am going to move it to discussions.

Hi @amruthesh_ag ,

I agree, you can fix a lot with Launch, but this also raise a couple of questions and complications. For example, will the original issue be fixed on the platform side and when, meaning you may have to synchronize releases to remove patches in the future. Also, this will add an additional layer of complexity in launch and bloat the code base which may make maintenance harder.

I have seen other tools like Target being ab/used in a similar way where winners of A/B tests were pushed and remained active as the standard implementation instead of making sure implement the needed changes and deactivate the test asap.

Best case scenario is always a hotfix of the system that causes the problem instead of asking you as Tag Management owner to fix other people's problems. Sometimes this is not possible and you may need to make an exception, but in general, I would try to keep your tag management system as lean as possible.

This can be used as a last resort to temporarily fixing deadly issues but should not considered as a norm or practice. The development, compliance, and security teams could be unhappy with that, as it skips the regular development cycle and change management of the website.

Moreover, I would prefer to keep tools to their original purpose, even if they can do more. Adobe Launch is a tag management tool and its purpose is to trigger tags/pixels, where the definition of tags/pixels is getting blurred now, as some features enablement are also considered as tags now, such as adding a social feed into the web page. That is already on the edge of what I think a tag management solution should do.

@leocwlau @bjoern__koth  @jennifer_dungan
Thanks for your suggestions

Yes you guys are right, its just a hot-fix and temporary solution its not recommended for every release.

What I am following like Once issue is fixed I am creating ticket in JIRA to take care of this fix from AEM development on next release. then I am removing this fix from Adobe launch.

Hi @amruthesh_ag ,

Thanks for the mention. As an organization for which development is heavily dependent on Vendor and more often than not, we keep coming across issues that have serious implications on user journeys, we use Adobe Launch as you described above as hotfix solution. For us, raising a ticket to vendor and getting it resolved from them does take much longer time, not to mention the cost. So even though I totally agree with @bjoern__koth @leocwlau & @jennifer_dungan here on the additional layer of complexity, as well as addition of extra code, this does provide some flexibility when the solution needs to be deployed quickly. Only issue I see is, when my dev team deploys a hotfix through Launch, there almost every time is flicker which is bound to happen as Adobe Launch can only manipulate the elements once they become available on page which sometimes makes them visible to users before modification.