Interactions (drag and drop) and data volume

New
Avatar
Chamrith Jayasinghe

Hello,

1. we have come across a performance analysis for a drag and drop user interaction in a Gantt chart and a table, the users can pick a row, select and drag it to a slot in the Gantt. is there any way that the users can track these events ( Drag & Drop ) ?

2.Since INP mainly captures interactions like clicks, taps, and key presses, is it a suitable metric for pages that rely heavily on drag-and-drop interactions?

3. Developers are looking for insights into customer data size, as some errors seem to be linked to data volume. Is it possible to capture data volume so they can replicate these conditions in their test environments?
 

0

Comments

1 comment

  • Official comment
    Avatar
    Hania

    Hi Chamrith Jayasinghe !

    We've since discussed these queries via the support ticket you submitted, but just re-sharing our guidance from there for posterity.
     

    1. The initial 'click' will expectedly capture by default in Fullstory by default. We don't capture any ‘drag’ event out-of-the-box, though if the ‘release/drop’ action requires a further click - you could consider adding both click events to a Fullstory funnel, and then looking to the median time to convert surfaced there. Or if not, you could consider implementing a custom event (or series of custom events) to listen for the native dragend & drop events occurring on your live site, and pass those into Fullstory as a custom event.
       
    2. Yes, Interaction to Next Paint (INP) can be a helpful metric for measuring the initiating interactions of a drag and drop event (i.e. the click/grab and the drop/release). Since it is measuring the latency of the initial click, and how long the page takes to respond. It isn't however, designed to measure the continuous motion of the drag itself.
       
    3. As we delved into further in your support ticket, you let us know that this ask was specifically around some network and console errors you've captured - and correlating those to a specific volume of ‘task’ related content present on your live site.

      Regarding analysing network/console errors generally, you can quite easily filter for network and console errors in Fullstory, and group by/filter on factors like the network request method, or status code. Or for console errors, the text contained within such errors.

      But in terms of correlating those specific errors to the presence of specific content/assets on your live site - whether this is achievable or not will depend of if these are just visual aspects in the session replay, or whether you actively pass any information on the 'number of tasks' into Fullstory via API (within a custom event or other custom property). If you can share more detail (or ideally an example session) with us in your support ticket, we'll be able to review and advise further.

    We're on hand should you have any follow-up queries.

Please sign in to leave a comment.

Didn't find what you were looking for?

New post