When working with marketing pixels, my site performance guy and I use the Load Order for Rules document to make sure we are putting the pixel in the least disruptive location on the page (while still getting the pixel what it needs).
In the Launch Rules, I see the 4 page load phases (see screen shot 1 below). But, when I go to set-up my pixel in the Action Configuration, I only see JavaScript and HTML (see screen shot 2 below). In DTM, I am able to choose Sequential HTML, Sequential JavaScript, Non-Sequential HTML, and Non-Sequential JavaScript (see screen shot 3 below).
Screen Shot 1 :: 4 Page Load Phases in Launch
Screen Shot 2 :: Only 2 Options in Launch (JavaScript and HTML)
Screen Shot 3 :: 4 Options in DTM
Solved! Go to Solution.
SarahEOwen I don't have any problem talking about load order in the meeting but I'll defer to thebenrobb since he's the PM. It sounds like you're interested in some of the deeper details though. I'm happy to dive deeper here so you can have something written that your group can stew on. Some of this is from memory, so if it's inaccurate, I apologize.
In DTM:
In Launch:
A couple notable items:
You can now use document.write within your custom scripts regardless of the events configured for the rule. In DTM, document.write inside custom scripts would only work on page top or page bottom rules.
You can now order different custom code types amongst each other. For example, you can now have a JavaScript custom code action, then an HTML custom code action, then a JavaScript custom code action. Launch will ensure that they are executed in that order. This wasn't the case in DTM.
I hope that helps!
Hi Sarah,
In Launch, when a rule fires, the "custom action" scripts in the rule are loaded as quickly as possible in parallel, but they are executed in the order you've set within the rule, even if they finish loading out of order. In the case of rules that use the page top or page bottom event, the "custom action" scripts are actually included in the main Launch library instead of being loaded from the server through separate requests. They will always be executed in the order you've indicated in the rule.
We used e.g the sequential html to load css directly into the DOM. Non-sequntial always opens an iFrame for this.
How will this be handled in Launch?
Views
Replies
Total Likes
HI thebenrobb and Aaronius9er9er -
In the 8/22 or 8/29 meeting, can we talk about the difference between DTM Load Order and what Launch is doing?
I want to make sure I convey to my site performance guy what differences he may see - especially with the ubiquitous marketing pixels.
Thanks -
Sarah
FYI I would also mention Ambria but I don't see/know her @ handle
Views
Replies
Total Likes
Till, we no longer use iframes to load custom code. You can use the custom code action to load css directly into the DOM. It also doesn't matter which event types are used in your rule.
Views
Replies
Total Likes
SarahEOwen I don't have any problem talking about load order in the meeting but I'll defer to thebenrobb since he's the PM. It sounds like you're interested in some of the deeper details though. I'm happy to dive deeper here so you can have something written that your group can stew on. Some of this is from memory, so if it's inaccurate, I apologize.
In DTM:
In Launch:
A couple notable items:
You can now use document.write within your custom scripts regardless of the events configured for the rule. In DTM, document.write inside custom scripts would only work on page top or page bottom rules.
You can now order different custom code types amongst each other. For example, you can now have a JavaScript custom code action, then an HTML custom code action, then a JavaScript custom code action. Launch will ensure that they are executed in that order. This wasn't the case in DTM.
I hope that helps!
SarahEOwen I don't mind talking about it in the 8/29 meeting (next office hours), but I won't be able to say anything that Aaronius9er9er9er didn't just say much better =)
Views
Replies
Total Likes
Hi Aaronius9er9er and thebenrobb -
Thanks for the write-up! I've printed it off to read over it - I'll follow up with any questions.
THANKS!
Sarah
Views
Replies
Total Likes
wow good to know. Thanks for the information.
Hi Aaronius9er9er -
Just got out of a meeting with the developers and the site performance guy. We really appreciate your detailed explanation and the link to postscribe on github.
Based on this info, we are going to try moving toward using DOM Ready instead of Page Bottom to take advantage of the postscribe functionality.
At this time, we do not have any follow-up questions.
Thanks -
Sarah
Views
Like
Replies
Views
Likes
Replies
Views
Likes
Replies