Expand my Community achievements bar.

Number of bookings discrepancy

Avatar

Level 2

Hi,

 

I'm seeking to understand if there's a method to create a segment or calculated metric that doesn't count page reloads.

For a form submission, I need to capture the number of bookings. However, if a visitor reopens the page, the form step instance is counted twice.

For example, if a visitor starts and completes the booking in one session, it's counted as one visitor with one booking (form step instance). But if the same visitor reloads the appointment page without initiating the booking, the number of bookings (form step instance) is recorded as two.

5 Replies

Avatar

Level 4

@AsthaKhetrapal you can drop in the reload metric to the segment to exclude any page reloads

juliusonyancha_0-1724139851767.png

 

Avatar

Level 2

Thanks @juliusonyancha for your suggestion.

 

I will rephrase my query. 

 

If a visitor accesses the booking appointment page without initiating the booking form (referring to a previous booking), the form step instances count it as a second booking instead of just a page visit. To exclude this from happening, is it possible to create a segment? I attempted to create the following segment, but it was not successful.

 

AsthaKhetrapal_0-1724198586596.png

 

Avatar

Level 4

@AsthaKhetrapal I will consider,

 

1. Setting up a segment as below, however, this will depend on the tracking setup.

 

juliusonyancha_0-1724228261493.png

 

OR

 

2. Using a fallout based on visitors to view those who complete assuming that the form steps (start and completions) are tracked separately/separate events are fired.

Avatar

Level 5

Hi @AsthaKhetrapal 


To prevent counting page reloads as additional form submissions, create a segment or calculated metric that ensures each form submission is counted only once per session.

Next, create a distinct ID for tracking purposes, such as a session ID or visitor ID. To filter out more submissions within the same session, set up your analytics platform to count form submissions based on this unique identity. 

 

Our other choice is to configure event tracking to fire only upon successful form submission, excluding page reloads. Only the initial form submission event for each session or visitor should be included using segments.  This method gives you a more precise count of unique bookings by preventing your booking counts from rising when you reload the page.

 

Let me know if this helps.

Thanks