You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.
A client recently asked me to explain an odd spike in their GA traffic.
The spike was associated with a single URL, which was of the format: admin/entries/channelHandle/new.
It appears that if you create a new entry in a channel and immediately open live preview, before saving the entry first, then SEOmatic doesn't suppress the GA code as it does for all normal Live Preview views. Thus, as the client creates the entry with Live Preview open, dozens of page views are registered with GA.
As soon as an entry is saved, so it actually exists as an entry in Craft, and Live Preview is subsequently opened when editing the entry, then SEOmatic correctly suppresses the GA code as expected.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Craft CMS 2.6.3008
SEOmatic 1.1.56
A client recently asked me to explain an odd spike in their GA traffic.
The spike was associated with a single URL, which was of the format:
admin/entries/channelHandle/new
.It appears that if you create a new entry in a channel and immediately open live preview, before saving the entry first, then SEOmatic doesn't suppress the GA code as it does for all normal Live Preview views. Thus, as the client creates the entry with Live Preview open, dozens of page views are registered with GA.
As soon as an entry is saved, so it actually exists as an entry in Craft, and Live Preview is subsequently opened when editing the entry, then SEOmatic correctly suppresses the GA code as expected.
The text was updated successfully, but these errors were encountered: