MVA / FIELD GUIDES / Conversion tracking
The tag is paused. Why is the event still showing up?
A paused tag is a clue about one collection path. Ask the implementation owner which version is live and where a newly sent event is coming from.
First: did the pause reach the live site?
If an event still appears after a tag is paused, your team needs to know whether the change reached the website and whether another route is sending it. Start by asking the tracking owner which version is live.
In GTM, a paused tag must be saved and published for the change to take effect on the live configuration. A pause left in a workspace is not enough. Confirm the intended container, published version, environment, and site.
Have the owner follow a fresh journey after the change. Separate a newly sent event from an older event still visible in a report, and record which destination received it.
Now look beyond that one tag.
A GTM event tag
The change applies to this tag in the configuration you published.
A native integration
A website or commerce integration may send a similar event through another route.
A direct script
Page code may send events independently of the paused GTM tag.
The same GA4 destination
Trace the live request and its source. The diagram lists possibilities; it does not show that all three are active.
GA4 events can be implemented through GTM or through a Google tag in the site’s code. If your site has another container or a platform integration, that may provide another route to inspect. The event name alone cannot identify which route sent it.
Ask for a trace of the newly sent event, its destination, and the action that produced it. The owner should compare that evidence with the code and integrations present on the site. A settings screen shows configuration; it does not by itself show what happened in the journey.
Ask for a trace before agreeing to a change.
- Which version is published on the site?
- Was a fresh event sent after the pause?
- Which destination received it?
- What evidence identifies the sending route?
- What else depends on that route, and who owns the correction?
The person investigating can use GTM Preview and Tag Assistant to inspect tag behavior. The review needs to identify whether it used a draft or published version. The absence of a tag from one preview does not establish that the entire website stopped sending the event.
Change the route you can explain.
Once the source is supported by evidence, agree on the correction and who owns it. Consider the other analytics or advertising destinations that rely on that route. Removing a shared integration to stop one event can affect more than the report you were looking at.
Record what changed, which journeys were reviewed, and what still needs investigation. If you have only narrowed the possibilities, say so. That is useful progress, and a much better basis for the next change than treating every similar event as the same implementation.