best practices for handling 3rd party pixel or custom code in Launch

Avatar

Avatar

gokula

Avatar

gokula

gokula

17-03-2021

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. 

 

@thebenrobb 

launch Launch Extension

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar

timf13285459

Avatar

timf13285459

timf13285459

06-04-2021

An easy way to cheat is to add your custom code as a condition. Conditions are loaded with the main js file. You can also in your condition do something like

window.setTimeout(function(){ /*really load*/}, 1000) which defers the execution of the code for another second.

 

Avatar

Avatar

yuhuisg

MVP

Avatar

yuhuisg

MVP

yuhuisg
MVP

18-03-2021

If there isn't an extension for your pixel, then you're stuck with Custom Code.

If you're using Custom Code, why can't you include everything in one big Custom Code action? Then only one sub file will need to be downloaded.