Release Notes
Release Notes
Preventing multiple ecommerce events triggering in Google Analytics
May, 9

{"base64":"  ","img":{"width":81,"height":20,"type":"svg","mime":"image/svg+xml","wUnits":"px","hUnits":"px","length":931,"url":""}}

The ecommerce variable was fixed to prevent the same ecommerce event from being triggered to Google Analytics (GA) multiple times and resulting in a financial cost.

Why did we make these changes?

Previously, users of the VTEX Google Tag Manager app had the same ecommerce event fired several times to Google Analytics, resulting in a financial expense because the large number of events triggered exceeded the monthly free visits of 10 million.

Now, the ecommerce variable passes null before pushing an ecommerce event to the data layer, as Google recommends, which prevents the same event from triggering in GA and does not exceed the monthly hits of 10 million free visits.

What needs to be done?

Nothing. This improvement is already available for all VTEX IO users.

Was this helpful?
On this page