Docs: Callback with Custom Event about km-support HOT 5 CLOSED

Is this primarily to add abstraction to waiting for when the KM object is ready?

_kmq.push(function() {
    $.event.trigger("kmLoaded");
    // This function executes *because* KM has loaded
    // why not doStuff here?
});

from km-support.

In my particular use case, the abstraction provides better interoperability with my tag management platform's script firing conditions and (I think?) some timing / performance benefits as well.

BrightTag, the tag manager we are using, manages all events and data in one place to determine the conditions when any particular code block will execute without placing the entire burden on client-side JS. For my use it's convenient and efficient to have an event to bind to because there's a place for event firing conditions in their interface and their system deals with code optimization for me.

In general and for users with a more traditional setup, I would imagine pushing heavy functions to _kmq being something that slow things down a bit... but I'm by no means an expert in these things. Just figured others could find this useful if they either use a 3rd party tag manager, or if they would like timing to be managed outside of KM.

On Jul 18, 2013, at 5:13 PM, Eric Fung [email protected] wrote:

Is this primarily to add abstraction to waiting for when the KM object is ready?

_kmq.push(function() {
$.event.trigger("kmLoaded");
// This function executes because KM has loaded
// why not doStuff here?
});

—
Reply to this email directly or view it on GitHub.

from km-support.

Ah, good point. If tag managers get involved, I can see how this would be useful.

I can incorporate your explanation into an alternate version of http://support.kissmetrics.com/apis/javascript/javascript-specific/#callback-functions

from km-support.

071c6a1

from km-support.

Just wanna say that I was halfway through typing my request to support when I ran into the part in the kissmetrics docs where it said this trick. It's exactly what I needed and for similar reasons, so thanks both @eskfung and @jonazri!

from km-support.