best practices for handling 3rd party pixel or custom code in Launch
Hello,
can someone share what's the best practices for handling 3rd party pixel or custom code in Launch.
Reason being - having the launch property with multiple rules and data elements - we deploy the 3 party pixel either using extension or by adding as custom code in action part of the rule.
Now when we add the any custom js into action part of the rule - That means, for every single action of the “custom code” launch generates additional sub file.
This sub file may be less or big in size depending on the JS code but - if there are multiple sub files getting generated on landing page - its impact on the performance of the page.
So is there any way we can optimize this and includes all the things in Launch main library and not in sub files.