Google Tag Manager表单提交事件被JavaScript setAttribute()意外触发的修复方案咨询

It sounds like your custom JavaScript that updates the submit button's value is inadvertently triggering GTM's Form Submission trigger—likely because GTM's listener is picking up on a change to the form element that it misinterprets as a submission event. Here are two straightforward fixes to resolve this:

Solution 1: Update the Button's Value Property Directly (Recommended) #

Instead of using setAttribute('value', ...) to modify the submit button's text, use the button's value property directly. This is the standard way to update the visible text of a submit button and avoids triggering any unintended attribute-change events that GTM might be listening for.

Replace your existing code with this:

document.querySelectorAll('[data-showlabel]').forEach(item => {
  const showLabel = item.getAttribute('data-showlabel');
  const submitBtn = item.querySelector('input[type="submit"]');
  if (submitBtn) {
    submitBtn.value = showLabel; // Use the value property instead of setAttribute
  }
});

Why this works: The setAttribute method modifies the underlying HTML attribute, which can sometimes trigger DOM mutation events that GTM's form listeners might pick up. Setting the value property directly updates the button's current display value without altering the original HTML attribute, which is less likely to trigger false positives.

Solution 2: Tweak Your GTM Trigger to Exclude False Positives #

If Solution 1 doesn't resolve the issue, you can adjust your GTM Form Submission trigger to only fire when the submission is initiated by a user interaction (not by code changes). Here's how:

1. Open your GTM workspace and navigate to the Form Submission trigger in question.
2. Under the Trigger Conditions section, add a new condition to filter out non-user-initiated submissions:
   • For example, add gtm.elementEvent equals click (this ensures the trigger only fires when the submit button is clicked by a user).
   • Alternatively, if you want to include submissions triggered by pressing Enter in an input field, add an OR condition: gtm.elementEvent equals keypress AND event.keyCode equals 13.
3. Save the trigger and publish your GTM container.

This ensures that GTM only fires the Form Submission event when a user actively submits the form, not when your code modifies the button's value.

Either of these solutions should stop the accidental trigger on page load. Start with Solution 1 since it's a simple code adjustment that addresses the root cause of the false positive.

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