background Layer 1

We Scan Tickets Blog

3 September 2019

Advanced features our checkout can offer

There are so many small key features our checkout offers which we simply don't talk about enough. Little tweaks and code snippets that handle a lot of issues. The biggest issue checkouts have is scrolling. A checkout with scrollbars inside an event website is an absolute no. On a mobile device, this creates a horrible user experience.

To rectify this we allow the event website and checkout to communicate, and constantly update the containing height of the embedded frame. This makes the checkout seamlessly embed into the website, giving the client the impression that there is no embed, that it is part of the standard website. That's exactly how we want our checkout to be seen and to top it off, we have none of our branding. By embedding the checkout we keep all security and sensitive data within scope and out of range of the parent website, taking away the responsibility of security from the organisers.

Another feature of the checkout is the SSL detection. In today's web standards all websites are recommended to be secure (https), and a software solution like ours, we are required to be secure. If you somehow still don't know what an SSL certificate does then allow me to explain. An SSL certificate will encrypt all the data send from your phone or computer to our web application on our server, meaning anyone in between won't be able to read the information. As an example, someone would have a much better chance at reading your credit card details during a transaction if SSL certificates were not available.

Onto my point, our checkout has a nice SSL detection system, which will identify if your event website is encrypted, if not it will open a new window at the second stage of the checkout, just before the user enters personal details. This allows the checkout to still be embedded initially but then take the sensitive details securely later. This also keeps the number of steps or pages the same for secure and initially non secure checkouts.

They're the two main factors for user interaction. I'm going to briefly cover our tracking system.

There are 3 types of tracking events: PageView, Interact, Purchase. You can probably guess what they do but I'll explain anyway. PageView fires when the checkout is loaded and in view of the user. Interact fires when the user interacts with the checkout, for example if a drop-down box is opened or a button is clicked, keep in mind this event only fires once per page load. Finally the purchase event which you guess it, fires when a successful purchase is made.

If you want to go quick and easy with your event tickets, you can view these tracking events in the form of charts and graph with breakdowns and funnels in our dashboard. If your a more advanced user and want to see conversion and patterns, you can connect Facebook Pixel or google Analytics and these tracking events will fire in the connected tracking solution, even more you can create targeted advertisement based on the usage of your checkout, and you can get really specific. But that's another blog for another day.