Hi Anthony,
It sounds like you may be better off rolling out your own real-time data collection using the Web Vitals JS (https://github.com/GoogleChrome/web-vitals). I’m doubtful that Regex would be considered for the API. It’s a heavy operation for such dataset.
By rolling your own solution rather than using the CrUX API, it is possible to see the events as they occur, along with isolating spit testing for rapid feedback. Aggregating the page types would provide you with a much more usable dataset as you mention. How many events are you expecting per day?
Best regards,
Ryan
Ryan Siddle / Digital Director
ryan....@merj.com
Merj
+44 (0) 2033 222 660 / Ext: #101
9th Floor, 1 Ropemaker Street, London, EC2Y 9HT
merj.com
--
You received this message because you are subscribed to the Google Groups "Chrome UX Report (Discussions)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
chrome-ux-repo...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/b6aa8fff-9e3c-4269-b759-325d201f1156n%40chromium.org.
What is the specific time that it takes for the results to show up in CRuX
Also, does this mean that unless the data reflects in CRuX, the improvements made will not be accounted in search rankings?