-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LoAF attribution #363
Comments
@gilbertococchi 's been asking for this too. IMHO not until it lands in stable Chrome without being behind a flag. We don't want people to depend on implementations that might change. In same way we're not landing soft navs in |
That'd be my preference. Best to give the community something to work with to encourage early adoption, like you mentioned for soft navs. The added maintenance overhead doesn't seem like a huge burden. If it doesn't work out, maybe someone would be willing to maintain it in a fork. |
We also need to figure out what we'd use it for. Presumably you want to link it up to the INP interaction (which is non-trivial at the moment) and then feed back the attribution in analytics? But I don't want to make assumptions here, so looking for people to document how they would see it being used in web-vitals.js. |
I think I would expect the INPAttribution interface to have The only thing that is a bit blurry to me right now is how I would handle these LoAF entries in case INP is reported more than once. I don't understand why this happens (and would really appreciate some clarification haha but I know this issue is not a place to discuss that) but in this case I think I would need to do some logic to store the Not sure if it helps but here are all the fields I'm reporting to my analytics
|
Resolved with #442 and will be included in v4. In future we may iterate further on this to pull out the most relevant data from LoAFs if common patterns emerge that would benefit this. |
Are there plans to add experimental LoAF support to the attribution build?
The text was updated successfully, but these errors were encountered: