Data Layer事件推送异常：自定义事件参数被篡改问题咨询

Hey Mike, let's break down why your pushed Data Layer event is showing up with unexpected values (checkout as the event action, shop appended to your item name) in the analytics.js request. Here are the most likely culprits and how to track them down:

1. GTM Triggers/Variables Overriding Your Values #

This is the most common cause. Your Google Tag Manager setup might have existing configurations modifying the event parameters when they fire:

• Check event listeners: Look for all GTM triggers set to listen for the item event. One of these could be mapping your item_name to the Event Category with a hardcoded shop suffix (like {{item_name}} shop).
• Inspect variables: Check any custom variables used for Event Category, Action, or Label in your GA tags. A Custom JavaScript variable or Lookup Table might be altering item_name or forcing checkout as the default Event Action.
• Use GTM Preview Mode: Fire the event again in preview mode. Check the Data Layer tab to confirm your original event object is pushed correctly, then look at the GA tag firing details to see which variables populate each parameter.

2. GA Settings Variable Defaults or Enhancements #

If you're using a GA Settings variable in GTM, it might apply default values or enhanced logic that overrides your event data:

• Check Fields to Set: Open your GA Settings variable and look for any default values set for eventAction (this could be forcing checkout) or eventCategory.
• Temporarily disable Enhanced Ecommerce: If Enhanced Ecommerce is enabled in the settings variable, it might auto-map your item event to a predefined checkout flow, adding extra context like shop.

3. Custom JavaScript Tampering with the Data Layer #

There might be code on your page modifying the Data Layer after you push your event:

• Inspect Data Layer history: In your browser's console, type dataLayer and expand the array to see the full event history. Look for entries that modify your original item event after it's pushed.
• Search for Data Layer listeners: Scan your site's JavaScript code for dataLayer.push listeners or functions that directly modify Data Layer objects. For example, code like this could append shop to your item name:

  dataLayer.push(function() {
    var lastEvent = this.get('event');
    if (lastEvent === 'item') {
      this.set('item_name', this.get('item_name') + ' shop');
      this.set('event', 'checkout');
    }
  });
  

4. Enhanced Ecommerce Auto-Mapping Conflicts #

If your site uses Enhanced Ecommerce tracking, GA might automatically categorize your item event into a checkout flow:

• Check GTM's Enhanced Ecommerce setup: Look for tags configured to send checkout step events, and see if they're accidentally triggered by your item event.
• Review GA Admin Settings: In your Google Analytics admin panel, check for auto-event tracking rules for ecommerce that could alter your event parameters.

Quick Test Steps #

1. Confirm your event is pushed correctly by logging it to the console right after pushing:

   dataLayer.push({ 
     'event': 'item', 
     'item_name' : 'generic user', 
     'item_value' : 'commenced' 
   });
   console.log('Pushed event:', dataLayer[dataLayer.length - 1]);
   

2. Create a test GA tag in GTM that uses raw Data Layer variables (no custom transformations) and fires on the item event. See if this tag sends the correct parameters to GA.

内容的提问来源于stack exchange，提问作者Mike