Feature request: Allow calling _gat._getTrackerByName()._trackEvent about analytics.js HOT 4 CLOSED

We actually have two helper methods for track called trackLink and trackForm. We just put up some documentation about them here: https://segment.io/libraries/analytics.js#trackLink They'll insert a small timeout that gives the events time to fire before the page unloads. So you shouldn't need to use the synchronous call there anymore (and you still get a nice clean API for it).

If you're using Segment.io, you'll need to update your snippet so that the two methods are available to you.

Cheers

from analytics.js.

You might want to add trackClose or trackNavAway, which also add a small timeout before they allow closure or nav away to allow enough time for event tracking.
And even if their implementation is just the same as trackLink or trackForm, it's still semantically cleaner.

from analytics.js.

trackClose is interesting. Which events do you want to track then? And how is that different than trackNavAway?

from analytics.js.

trackClose and trackNavAway are the same, it's just two different names
that came to mind.
My use case is that I have a video show and during the show I send tracking
events to see which segments were watched or not. But I also want to know
if a user leaves in the middle of the show, in the middle of a segment -
when did she leave exactly? So I want to send an event when she either
closes the browser tab or navigates away to a different site.

On Mon, Jan 28, 2013 at 8:58 AM, Ian Storm Taylor
[email protected]:

trackClose is interesting. Which events do you want to track then? And
how is that different than trackNavAway?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/50#issuecomment-12770551.

/Ran
http://tavory.com

from analytics.js.