So what do we do with these variables?

[Jahangir147]

Let’s look at a real life example of how these variables work and how we end up with our final product – the custom report. In the following scenario we’d like to know how many users tried to contact us via an online form, to do this we need to capture the name of the form (e.g. contact us) and if a user has started the form and completed the form.
The type of report we would end up with would look similar to the following image:

custom report example

From this report we can see a lot of Form Starts, but a only a small number of Form Submits. This would make me curious and I would start to dig deeper to see if there are issues with the form. Maybe a lot of users are starting the form, but there is some type of road block stopping them from completing the form. If we aren’t collecting the data we may never really know if there is something wrong or not with the form.

How did we create this report?
Ok lets take a few steps back. This report ‘Form Name+’ shows a value ‘contact us’ with a poland email list 2.3 million contact leads number of Form Starts and Form Submits. Form Name+ is actually an eVar that is set when our form initially loads – e.g. set eVar43 to ‘contact us’.

Hold on, what is eVar43? Basically an our variables (eVar, prop and event) are defined by a number which then in our admin we give user friendly names. So we map eVar43 to the user friendly name ‘Form Name+’.
Form name+ We can then look for the report called Form Name+ which is a bit more meaningful then a report called eVar43.

Engagement Score gives context to traditional engagement metrics.
Not all content is created equal. More money and resources are spent on refining the content that better delivers on your organisation’s goals, and so you should. Traditional engagement metrics like how long a visitor spends on site and how many pages they look at (called the Engagement Index), don’t take into account what type of content your audience is looking at.