This blog post will cover the following topics:
- New events
- Page performance context
- Link content
- Tracker core integration
- Custom callbacks
- Outbound queue
- New example page
- Other improvements
- Getting help
Enable automatic form tracking using the
Whenever a user changes the value of a field in a form, the Tracker will fire a
change_form unstructured event capturing the name, type, and CSS classes of the changed element, the ID of the parent form, and the new value of the field.
Whenever a user submits a form, the Tracker will fire a
submit_form event. This event captures the ID of the parent form and the names, types, and final values of all
textarea elements in the form.
When you call the method, it will only attach event listeners to existing forms, so you should call it again whenever you create a new form element. (This is safe - the Tracker will not attach more than one event listener to an element.)
Use them like this:
trackSocialInteraction method lets you track
social_interaction events on you site. This is its signature:
site_search event describes a user performing a search on a website. It can capture the search terms and search filters used, the number of results found, and the number of results displayed on the first page.
This is the signature of the corresponding method:
And an example of
trackSiteSearch in action:
filters parameter is a dictionary whose values can be strings or booleans.
trackPageView method now accepts an additional boolean parameter named “performanceTracking”:
If you set this parameter to
PerformanceTiming context will be added to the page view event. This context will contain all the data found in the
window.performance.timing variable, and so can be used to calculate how long the page took to load.
link_click event has been updated to include an optional
content field. This will be populated with the
innerHTML property of the link. The
enableLinkClickTracking now has a “trackContent” parameter which you must set to
true to capture the innerHTML of clicked links:
trackLinkClick method, which is used to track individual clicks manually, now accepts an additional string parameter named “content”:
This release integrates the core into the client-side Tracker. As a consequence, the random 6-digit “transaction ID” attached to all events has been replaced by a unique type 4 UUID, which will serve as the
event_id for this event. This makes the false positive rate for detecting duplicate events negligible.
You can now specify callback functions which will only be called when
sp.js has been loaded and initialized:
By default, events are sent to a collector using the same protocol (“http” or “https”) as the current page. Huge thanks to community member @kujo4pmZ for contributing the option to force the tracker to send all events over https! Just add a
forceSecureTracker field when creating a tracker:
Previous versions of the tracker had a
pageUnloadTimer which you could use to set a pause between an event being created and the page unloading, to give the tracker time to fire the event. Version 2.1.1 makes the timeout more intelligent: once all queued events have been sent, the page will unload, even if the
pageUnloadTimer has not yet expired.
We have also:
- Moved the context field to the end of the querystring in case it gets truncated #204
- Improved the efficiency of link click tracking #254
- Extracted link tracking functionality into its own file #266
- Made the regular expression used to match IP addresses more strict #267
- Renamed the “dist” directory to “deploy” #216
- Improved the CodeClimate rating for the project #150
- Added further Intern unit tests #76
- Added a section to the README for contributors on getting the Vagrant environment set up #169
Finally, we thank Kevin Simper (@kevinsimper on GitHub) for his contribution preventing the
localStorage queue of events from being incorrectly parsed.
Note that this version introduces BREAKING changes to the
trackLinkClick methods, all of which now have an additional penultimate parameter.
The deprecated legacy method
trackImpression has been removed entirely; use
If you are using Amazon Redshift, the new event types and performance context will require you to deploy new tables into your Redshift cluster.
For instructions on this, please see today’s Snowplow 0.9.10 release blog post.
We have published full documentation for version 2.1.1.