Follow Up Regarding Click Tracking and Form Conversions

[user70977]

When setting up click tracking in Adobe Analytics, should we set it up at the hit or visit level? Thank you!

[user70977]

To follow up, are there any concerns with using one vs the other?

[Jennifer_Dungan · Accepted solution]

Hi,

It really depends on what you are trying to achieve... generally speaking, you would track clicks (what button was clicked, on what page, etc) at a hit level. So that every subsequent tracking request for the rest of the visit doesn't count as "click x".

However, if you trying to correlate this to a conversion later in the visit, you might need to have some of the information set to a Visit level attribution to persist those values to the moment of conversion. Sometimes, rather than doing this on the click, an internal campaign is used instead (different from your external campaigns, the internal campaign can be a simpler notation to indicate an internal promotion was engage with).

Maybe if you told us a little bit more about your site, what the button does, and what you plan to report on it would help us to better provide advice.

[user70977]

Thank you Jennifer for your quick response. To follow up, can you help clarify why click needs to expire at visit for form conversions? What business question does that help answer? I thought since form conversions is already at the visit level, even if click expires at the hit, we can still see the # of form conversions from a specific button click. Does click need to expire at the visit in order to do this type of analysis?

For a more specific example, I would like to look at click using the user flow diagram, would we still be able to have this information if click expires at the hit level?

[user70977]

I have a follow-up question from this previous post: https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/when-setting-up-click-tra...

I have 2 questions:

1. If I am interested in click behavior using the user flow diagram, would we still be able to have this information if click expires at the hit level?

2. Why does click evar needs to expire at visit to look at the number of form conversions from a button? I thought since form conversions is already at the visit level, even if click expires at the hit, we can still see the # of form conversions from a specific button click. Does click need to expire at the visit in order to look at form conversions from a specific button?

[RiteshY18]

@user70977  The idea here to capture different user interactions and track them 

• Track form clicks
• Track field interactions example email 
• Track successful submissions
• Track errors

assign a corresponding evar for each interaction, if you are going to use only one then will not get enough insight

[Jennifer_Dungan]

Hello again!

Oops, sorry I missed answering your question in the last post.. I am going to merge the posts to keep the conversation going in a single location.

[Jennifer_Dungan]

So, to answer your questions:

---

1. If I am interested in click behavior using the user flow diagram, would we still be able to have this information if click expires at the hit level?

---

In the flow diagram, hit behaviour does work better. I will give you that... but if you are talking about a click, you can use the Custom Link value, (which is a hit based dimension, or even a custom hit based dimension on the click), while still having other visit (or other attribution) dimensions that persist the values through to your conversion.

Flow diagrams don't work so well with persisted values, since the value persist on every hit afterwards until it expires or a new value is set...  This can muddy the flow diagram.

On a button hit, all your dimensions don't have to have the same expiry, you can set what you need only on the hit to a "hit expiry", and values you need to persist for conversion to "visit expiry". 

---

2. Why does click evar needs to expire at visit to look at the number of form conversions from a button? I thought since form conversions is already at the visit level, even if click expires at the hit, we can still see the # of form conversions from a specific button click. Does click need to expire at the visit in order to look at form conversions from a specific button?

---

If you are only talking about form conversions then no, you probably don't need a visit level expiry... this is more for attributing a button hit to something like an purchase/order or subscribing to a newsletter, etc later in the visit.

For instance, maybe your "click" is a promotional banner...  this banner takes the user to a product page, then the user adds that to their cart, then they check a few more things, add a few more items to their cart, then they make a purchase...  having a visit level dimension from that promo banner click allows you to see on that order that the user interacted with the promo before making a purchase.

However, if your implementation is simply:

• Form Page
• Submit Form

And you want to create a conversion rate based on "Form Submissions / Form Page Views" then yes, HIT is all you need, since its all contained to the actual submission.

Since your original question was pretty open to interpretation, without a specific use case, I tried to answer it with as broad an answer as possible, it's also why I said "It really depends on what you are trying to achieve", because there are so many different use cases out there, knowing more about yours helps us to better guide you.

[Jennifer_Dungan]

Also, @RiteshY18 brings up some good points... while you can start with success rate, tracking form failures, or trying to determine where/if user fall off while filling in the form can be valuable information... but also be mindful of the number of potential server calls to achieve this... 

[user70977]

Hi Jennifer!! Thank you so much for this detailed response. This cleared up my concerns. I appreciate your help!