Can you bypass dev and stage to publish a build directly to Production?
Yes but not recommended as this sounds like tag implementation didn't go through proper testing before going into production, where you may break your website if anything goes wrong with tagging.
Moreover, you need to understand the difference between the environments in Adobe Launch and the environments of your website.
You may not have dev or staging environments for your website but you always have one staging environment and can have multiple development environments in Adobe Launch, each with its own Launch JS.
In the ideal world, you can assign and use each of those Adobe Launch JS of different Launch environments matching your website environments. However, in your case, there is only a production website without any dev and staging environment. You can use the Adobe Experience Platform Debugger to dynamically replace the Launch JS on your production website with dev or staging Launch JS to test your tagging implementation before going into production.
It is still strongly recommended to set up a staging environment for your website so all changes are properly tested before going into production.
Fully with @leocwlau
If your website does not have a non-productive environment, your are likely going to affect your prod system with bugs you are introducing along the way.
Rather use debugger extension to inject the development version and test it on your system before always pushing it straight away.
Else you will be doing an open heart surgery all the time 🫣
Cheers from Switzerland!
Related Conversations
