Code Monkey home page Code Monkey logo

Comments (6)

philipwalton avatar philipwalton commented on May 23, 2024 1

I'm going to close this as I suspect the issue is with this specific property's implementation and not an issue with the web-vitals library or its usage instructions related to GA. Please reply here if you discover otherwise.

from web-vitals.

philipwalton avatar philipwalton commented on May 23, 2024

Hmmm, I'm not sure why that would be. What is the hostname for the pageviews in that session?

In my experience bots and spammers send data containing URLs with an incorrect hostname, and so setting a filter on your view to only accepts hits with a hostname that matches your domain has generally worked for me to avoid all spam.

from web-vitals.

pec92 avatar pec92 commented on May 23, 2024

Hi Philip !

thanks for your hint.

I've added the hostname as secondary dimension for all not set landings, but it seems that all the traffic is coming from the correct website hostname, so I cannot filter it out.
It's really weird because (not set) landing were registered only when we had the web vitals tag active, and stopped just after we stopped the tag.

Thanks,
Daniela

from web-vitals.

robflaherty avatar robflaherty commented on May 23, 2024

Did you see a drop in pageviews too? Looks like pageviews may not be firing which would explain the not set landing page and the low number of sessions.

from web-vitals.

psabharwal123 avatar psabharwal123 commented on May 23, 2024

this happens when event is the first interaction on a page, we fixed it by making sure that web vital events always fire after the first page view.

from web-vitals.

smhmic avatar smhmic commented on May 23, 2024

The reason for this is because CLS can send multiple times per pageload and LCP will send when the tab unloads. If sending these values to GA as a non-interactive hit (which you should) then these hits will not extend the GA session. And if no subsequent pageview fires, then these hits will cause Landing Page = (not set).

So basically this will happen whenever:

  • the user has the page open longer than the GA session timeout (30 min by default) w/o triggering other tracked events
  • the user opens the page shortly before midnight based on the timezone you have set the GA view settings

I just submitted a new request which may help address this.

from web-vitals.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.