Google Analytics & Ingenico
Many merchants use statistics to optimize the sales performances of the webshop. Most used solution is of course Google Analytics, but the explanation below will be useful for other solutions as well.
If you have implemented Ingenico, most common workflow is to send the client with an URL-forward to the secure payment pages of the PSP. Especially with many new internetbanking payments growing rapidly but also creditcards, PayPal and pre-paid/gift cards. In terms of statistics this means breaking up the measuring of the visitors flow in the shop. How to recognize the client after the payment coming back from the PSP?
How to realize Analytics with Ingenico
The solution is very simple: use the Dynamic Template Page to change the layout of the Ingenico payment page to match the look & feel of the webshop and add your Google Analytics code to this Template Page.
- Look up your current Google Analytics codes in the webshop
- Add this code to the:
- Template Page (TP)
The Google Analytics code on the Ingenico-template will make that Google keeps track of the buyer, even on the Ingenico-platform. Next to that, the Google Analytics code on the client landingspages after the payment, will generate a full "Google visitor flow".
Google Analytics with Goals
If you define the Goals in Google Analytics, you could easily create the pipeline:
=> Webshop => Basket => Ogone* => Webshop landingspage afterwards
* The Ingenico goal-URL must be secure.ogone.com/ncol/prod/orderstandard.asp
All normal Google Analytics will be available now, like page-views, visitors, country, devices and other details.
Google Analytics E-Commerce
Next step could be to upgrade the integration to the Google Ecommerce conversions. Add the nessecary e-commerce parameters in your Google Analytics Code and next to the normal page/visitor counts, the real e-commerce volume will be tracked.
This means webshops can define e-commerce flow based on real amounts:
- Total amounts basket in basket
- Total amounts of transactions send to Ingenico
- Successful transaction amounts/volume coming back from Ingenico afterwards on the accept-landingspage
- But also unsuccessful amounts/volume coming back afterwards on the declined-, cancel- and exception landingspage.
A client coming back on the exception page still could result in a successful transaction (status-9) afterwards when the acquirer/payment method updates Ingenico of the final transaction status.
What about internetbanking payments where clients even leave Ingenico?
Unfortunately with some payment methods like iDEAL, GiroPay, BanContact/MisterCash, Ingenico has to send the clients to their bank, and only after the payment the client will be routed back to Ingenico. For now there are no options to follow the client at the bank with your Google Analytics.
Make sure to optimize the backflow to your landingspage:
As the client will return back to Ingenico and you don't want the client to close the window already, make sure to de-activate the ogone-status page. This will make the client to come back from the bank, transparently through Ingenico, directly to your landingspage (with Google Analytics code). By this you achieve the best Google Analytics results!
What if I use Session-ID's next to Google Analytics?
In that case consider the following options:
- The landingspage-URL's are dynamic per transaction. If you use ordernumbers or session-keys in the URL, you are able to recognize the returning client also based on the parameter in the URL.
Example: send the client to Ingenico for payments and use landingspage-URL's like
- Ingenico supports the PARAMVAR-field, 1000 characters long, Alfa-Numeric. You can add your session-ID in this field. Not only will Ingenico send this PARAMVAR back as postsale, but in the backoffice of Ingenico you can choose to receive transaction-statusses added to the landingspage-URL's!
Example: Send acceptlandingspage www.yourdomain.com/ogone/accept.aspx
Ingenico will return the client at: