StevenHook
asked on
How do I track customers after visiting our payment gateway in analytics?
Hi,
I have google analytics on my site.
It tracks the users nicely through the ordering process.
But as soon as they get to our payment gateway, they are lost. showing as a never returning exit.
Surely there must be a way of tracking them once they return to the confirmation page after payment?
Plug the hole in the goal funnel?
Thanks
Steve
analytics.png
I have google analytics on my site.
It tracks the users nicely through the ordering process.
But as soon as they get to our payment gateway, they are lost. showing as a never returning exit.
Surely there must be a way of tracking them once they return to the confirmation page after payment?
Plug the hole in the goal funnel?
Thanks
Steve
analytics.png
ASKER
Hi,
There is a return URL
And the users do see the conformation / thank you page back on out site.
But they are still being shown to have exited en mass at the payment stage.
Is there some kind of setting to tell analytics this is normal and link them back up with their whole purchase process path when they return?
There is a return URL
And the users do see the conformation / thank you page back on out site.
But they are still being shown to have exited en mass at the payment stage.
Is there some kind of setting to tell analytics this is normal and link them back up with their whole purchase process path when they return?
The refirect to the thank you page is effectively static you could try to use a php/asp page as the thank you and query for the cookie to identify the user who went to the payment, though once someone leaves your site, the return to thank you page is actually seen as a new visitor.
When one leaves set a non-expiring cookie that last 45 minutes as an example. On return and before displaying the page check for the cookie, if you revord what the person chose to purchase, include that in the thank you page, I.e. Thank you for buying, 1 if item A, 3 of item B an item C.
Make sure when the user clicks on the third party payment, you do not clear the parameters detailing the user's info/references..
When one leaves set a non-expiring cookie that last 45 minutes as an example. On return and before displaying the page check for the cookie, if you revord what the person chose to purchase, include that in the thank you page, I.e. Thank you for buying, 1 if item A, 3 of item B an item C.
Make sure when the user clicks on the third party payment, you do not clear the parameters detailing the user's info/references..
ASKER
Hi,
The thank you page is dynamic, it shows the user's order number etc.
This isn't really the question.
I'm asking about analytics. My analytics show that people are abandoning the process when they go to pay, and it does not pick them up when they return.
Surely this is something many people track, there must be a way to correctly get google analytics to recognise returning users from a successful or unsuccessful payment?
Thanks
Steve
The thank you page is dynamic, it shows the user's order number etc.
This isn't really the question.
I'm asking about analytics. My analytics show that people are abandoning the process when they go to pay, and it does not pick them up when they return.
Surely this is something many people track, there must be a way to correctly get google analytics to recognise returning users from a successful or unsuccessful payment?
Thanks
Steve
The way to track, your return URL needs to include the reference.
There are different ways to track one uses cookies, if your cookie expires with the session, when they leave, the cookie expires. Having an expiry cookie longer than a session when they return ....
The other option is to incorporate the payer API into your own pages to avoid the need to send the user to the external processor rather have your code interact with the processor to submit the information for payment.
There are different ways to track one uses cookies, if your cookie expires with the session, when they leave, the cookie expires. Having an expiry cookie longer than a session when they return ....
The other option is to incorporate the payer API into your own pages to avoid the need to send the user to the external processor rather have your code interact with the processor to submit the information for payment.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
But you seem to have a third party handling the payment processing part with their payment received thank you message.
You have to check whether the user of a redirect back would include the payment referencing information that you would use aggregate/match the user to their purchase/comfirmation...