Hi,Each page load rule would be evaluated on every page load. If the
conditions for the rule were met, the rule would fire. If you are using
a data element, the data element would be evaluated every time it is
called. After the data element is evaluated, the rule would fire if all
conditions were met for the given rule.I'm not aware of any noticeable
delay in using either method. You could test this in your own
environment with the developer tools in your browser. Cheers,Jantzen
HI,DTM does not have any built-in function to delay page load rules.
Typically, we recommend moving from page load to an event or direct call
rules when the timing is reliant on an external factor. With that said,
I did find an article that may fit your needs on an external site.
Please keep in mind, this is not an Adobe run site and any use of its
recommendations should be tested thoroughly. You can find the article
You either set the rule to trigger on DOM Load or a better way would be
to have the script which is pulling the data from database to run
_satellite.track call and set up a direct call rule in DTM then you can
be sure the tag won't trigger until the data is loaded.
You likely could as almost anything is possible with custom code. If you
wanted to go that route, you'd need to suppress page load beacons by
having your function return false in the Analytics tool. You'd also need
to write a custom condition for event-based rules. I'd recommend writing
a script inside a data element and reusing that data element as a
condition in each of your event based rules. Keep in mind, this is going
to create a bit of overhead as each rule that may fire on those domains