Skip to content

Releases: groupby/gb-tracker-client

v5.4.0

01 Mar 20:55
c7373be

Choose a tag to compare

What's Changed

Full Changelog: v5.3.0...v5.4.0

v5.3.0

22 Feb 15:02
33d9b66

Choose a tag to compare

v5.1.4

20 Oct 14:37
410b0db

Choose a tag to compare

What's Changed

Full Changelog: v5.1.3...v5.1.4

v5.1.3

10 Oct 18:22
9b2a4fe

Choose a tag to compare

What's Changed

Full Changelog: v5.1.2...v5.1.3

v5.1.2

06 Sep 13:29
1597f76

Choose a tag to compare

What's Changed

Full Changelog: v5.1.1...v5.1.2

v5.2.0-pre-release

14 Aug 19:18

Choose a tag to compare

v5.2.0-pre-release Pre-release
Pre-release

@KseniyaKondrashevich-GBI has advised that we should treat this tag as pre-release pending further development & QA.

What's Changed

Full Changelog: v5.1.1...v5.2.0

v5.1.1

11 Aug 14:47

Choose a tag to compare

What's Changed

Full Changelog: 3.12.0...v5.1.1

Add shared apex domain cross-domain support

17 Nov 19:46
7e0d134

Choose a tag to compare

Adds support for cross-domain tracking of shoppers, provided a some rules are met. See the readme for details.

Breaking changes

IMPORTANT

This version changes how shopper tracking works. If you use this version and your TLD is not .com, shopper tracking may break for you, and you should instead wait for tracker version 5.1.0+. See the readme for details.

Non-breaking changes

If you use a TLD like .com that is not affected by the issue described above, then this is a non-breaking change because the code used to call the constructor and event-sending functions does not change.

If you use version 4 right now, you can update by just updating the <script> tag or NPM dependency you use.

If you use version 3 right now, you should check the release notes for version 4 first to make sure the breaking changes do not affect you before upgrading from 3 to 5.

Restore front end validation for search event

27 Oct 19:12
593963d

Choose a tag to compare

Summary

Restores the old behavior for validating search events that was present in version 3.13.0. We unintentionally removed the validation for this event. In the future, it will be validated server side only (like the other event types), but for now, it will be validated in the browser JS the way it was before to help with implementing it. Errors will appear in the JS console.

Example:

image

Version is bumped to 4.0.0. You will need to manually bump the version you use via <script> tag (or via NPM) to 4 to get this change.

Note that despite being a major version increase to be strict with semantic versioning, any search event implementation using version 3.13.0 will work exactly the same with this version. Any search event implementation using a version after 3.13.0 will need to be tested with this version to ensure search beacons pass client side validation.

Details

What's Changed

  • INFO level logging for removed event types by @mattwelke in #95
  • WIS-2652 | Restore front end validation for search beacons by @mattwelke in #96
  • WIS-2652 | Restore front end validation for search beacons by @mattwelke in #97

Full Changelog: 3.13.1...4.0.0

Remove client side validation, deprecate some event types

31 Aug 18:06
a2cf40b

Choose a tag to compare

  • Remove validation portion of "sanitization and validation" code because we're doing validation on the server now. 400 responses replace JS console errors. This is designed to be a non-breaking change from the perspective of GroupBy customers.
  • Deprecate viewCart and moreRefinements event types. Calling functions is now a no-op. Functions will be removed in a future major version.