The way that the tag's loading logic works is far superior to a DOM ready extension, and has some extra safety mechanisms if the code has any errors that will prevent it from causing further problems. As Andre said, it also means you can use the load rules.
If you need any assistance creating a custom container tag, there is some very detailed documentation here:
Alternatively you can reach out to support or your account manager, and we can get the custom container built for you.
Thank you @nidhi for coming back and letting us know what method worked for you. Much appreciated. I have accepted your work as a solution. You might want to accept @UnknownJ's post above as an accepted solution as well. #winkwink
Let us know if you have any other questions.
I recently implemented Snapchat pixel and all is good. I also installed "Snap Pixel Helper" which is a chrome extension. The Snapchat pixel is suppoed to fire once on all pages. The problem is on one page of our website, "Snap Pixel Helper" tells that tag is firing twice and tagging request is a duplicate request. But in network call the tag is just firing once. There is no duplication in chrome-devtools-network call but the snapchat pixel helper extension tells there is duplication.
If anyone encountered the same issue and can give any inputs would be helpful. Thank You