web vitals | Queries

@jennifer_dungan  @harveer_singhgi1 @bjoern__koth @vinay_chauhan @zxfdafgsdh @kishore_reddy @chandratc @edwardbu3 

Hi @rudrawiley ,

I haven't used this extension so far and was hoping for someone with experience to respond on this but I believe most of the experts are busy at summit currently.

From what I could understand about the extension and it's uses I believe you can minimize the data collection volume by combining the multiple web vital metric in a single beacon. It must be achievable by using either the batch data element from extension or manually string the event data for every metric in either session/local storage or cookies and then send all this information together. 

When it comes to using other sources you should be able to use other analytics sources of your choice by either using their existing extensions in Adobe Tags catalogue or using custom postbacks to send this data.
Cheers!

I assume you're asking me these questions because I built the Web Vitals extension in Launch.

Truthfully, I only have a rudimentary understanding of Web Vitals.

I built that extension only as a service to the Launch community. My objective with the extension is to be able to have the measured values be returned through data elements without needing any custom code, so that they can be tracked as the Launch user desires. I don't have any objective to actually make use of the measured data, I leave that as something for the analysts of the Launch organisation to do.

Anyway, here's what I can say to your questions:

Data Collection Volume

• The minimum volume of data that is needed to be able to derive meaningful analysis is up to you. It is like asking how many visits are needed to analyse traffic behaviour, that is up to you / your analysts to figure out. I presume that some sort of statistical methodology would be needed.

Alternative Data Sending Options

• There are lots of other analytics platforms for you to use. For example: Snowplow, Mixpanel, or build your own with AWS or Azure.
• I suggest reading the README at https://github.com/GoogleChrome/web-vitals to figure out how to implement webvitals.js natively.

Debugging Custom Code

• I guess the simplest way to debug would be to log whatever values are getting measured by webvitals.js and see what's set/not set based on your expected results.

Hi @rudrawiley,

Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Correct Reply.'
Thank you!