Option to show data per card in form when using Google analytics widget

Hi, i got a card form and would love to get some analytics as to where people drop-off the most. This insight will help us to optimize field text and such to make the form more understandable and increase submit rate. 

Tried out your Google Analytics widget, but that was a bit of an disappointment as it didn't fire any events per card viewed. Would be cool to have this fire automatically and that the event data (category, action, label) was automatically populated (field text, unique name or such). Could dig deep and spec this more for you if you're interested as I am specialist within web analytics.

With this in place google analytics would show how many views/interaction each card got.

Alternative to this is to enrich your "Form analytics" with a new page showing data per card. 

Would love to have something like this. Already super happy with you product! Keep up the good work. 

It is good to hear that you are happy with our Form Analytics. You can explain the requirements you want here in details so we can escalate it to our developers for a feature request.

Description

As a user of Google Analytics Widget on a card based form, I want to see how many views each of my cards got. This can be done by firing a Google Analytics event each time a field is viewed. Here is a suggestion for values: 

Event Category: "Jotform interaction"
Event Action: "field viewed"
Event Label: {unique_name} OR {question-text}*
*use your own data to decide which one of these two will be most readable

Limits and reports

It may be interesting to add more types of field interactions than views (clicks etc), but I think that will complicate things too much for now. With "field viewed" in place the Event flow report in Google Analytics will be of great help to identify drop-offs.

About selecting property in Google Analytics for data collection.

If form is embedded it may be of interest to blend data from form with parent website. This will let you compare form completions from different traffic sources etc. Nice feature, but the problem is cross domain tracking. It is possible to fix as explained here, but default advice to users should be to create a dedicated property for form data for behaviour analysis solely. 

I will forward your request to our development team for consideration.  Please note that not all requests can be addressed.  Usually features are added due to overall demand for that specific feature.  If there is any progress to your request, we will let you know here in this thread.