Hello,
I’m facing an issue where the number of visits recorded for some entry pages is significantly lower than expected, yet the form completion numbers are disproportionately high. This discrepancy occurs consistently across multiple days, and I’m unsure what could be causing it. I observed that specific entry pages show very low visit counts on certain dates, but the corresponding form submission numbers are much higher. I have attached anonymized screenshots of the data to illustrate the problem.
Any insights or suggestions would be greatly appreciated!
Views
Replies
Total Likes
Just because the visitors don't enter on the page where the for ultimately gets sent.
what are the entry pages when the form gets sent? This might be a good use case for the flow visualization where you place the form submit event on the right side of the configuration and work your way backwards and check what pages the users have visited before. Sometimes this gives you very surprising and unexpected results.
Yeah, I would agree... I don't think I would use Entry Page in this context....Entry Page is a weird one... it's not specifically tied to the entry, but rather the first value seen by that dimension in a Visit.. but it tends to get confused when you apply segmentation to it; even if that segmentation is a "quick segment" which is achieved by adding dragging a dimension into the table (which is what is done on Form - I can see the yellow/orange of a dimension there).... I suspect this is causing a lot of confusion in the calculation of the values.... As in, the entry is being calculated differently because of the dimension "quick segment" in the column, and thereby causing disproportionate data.
Start by trying to break your report down by non-calculated values... like just "Page" and see what that looks like....
Column 1 is the Day broken down by Entry Page, Column 2 is Visits, & column 3 is the form completion event broken down by form name. I didn't use any quick segmentation /segments in this report.
I can see a stacked dimension in columns 2 and 3... what it is has been hidden, but I can see the yellow/orange of a dimension... when added to a column like this, it acts like a quick dimension:
Thank you, @Jennifer_Dungan; I aim to determine/analyze the pages that lead to Form completions on the site. Can you please elaborate on the meaning of the "non-calculated values"?
Views
Replies
Total Likes
The "Page" dimension is not calculated... this is every value that was sent to the Page dimension... "Entry Page" however is calculated... Adobe tries to determine the first value that was set during a visit. When that is mixed with a segment (whether a full segment, or a quick segment, or stacking a dimension in a column that works like a quick segment) the calculation of that value get muddled...
So let's say I visited:
Page A > Page B > Page C
Adobe will calculate that my entry page was Page A... but if I apply a segment that looks for hits on Page B, in this context, Adobe cannot see "Page A" and therefore might try to tell me my entry page is Page B (which obviously isn't correct).
Now when you say you want to "analyze the pages that lead to Form completions on the site", are you trying to find the first page of the visit, or the page that directly lead to the form submission? If you want the pages that lead to a form submission. If the form is submitted from those pages (via a modal popup, or the form is embedded on the page), this would be easy to capture on the form submission... if not, and you want to know the page directly before the form, I would be more tempted to create a complex segment that looks at the sequence leading to the form submission.
Does the Page dimension have values other than the page name? I'm trying to find the first page of the visit that leads to form completion and the page users visited before or before the form submission page. Do you have an example or documentation for creating this complex segment?
Views
Replies
Total Likes