Transaction Goal Count Over-Counting Against Actual Sales[ Edited ]
January 2016 - last edited January 2016
I'm Ian. First post here. Sorry if this has been covered, but I couldn't find the answer.
So, we have our goal set-up to track website transactions. It's quite simple, the last page of the sales journey is "/basket/complete". Only users who have had a successful transaction will reach this page, so therefore this is our Analytics goal URL. Our developer has ensured that this page can't be entered from it's URL alone, only from the checkout page of a successful transaction.
This has been working very well for us and we've been creating weekly reports based off it. Recently, however, we've been finding discrepancies, in that the total number of recorded conversions (i.e. hits to "basket/complete") is different to the number of actual sales we're getting. We have our CMS back-end report and our Stripe payments data too - which both match up together, but not with Analytics.
So, for example, Analytics records 11 conversions, but in reality only 9 sales were carried out in the same period on Stripe and our back-end.
Is this common? Maybe there's an obvious reason, but I can't see it.
All help welcomed.
Re: Transaction Goal Count Over-Counting Against Actual Sales
is it possible that the user can visit the confirmation page in multiple sessions / multiple devices - if he/ she bookmarks or saves the confirmation page? If so the goal will be recorded multiple times for the same thing.