Best Practices and Testing
Best Practices
-
The Checkin.com loader script is very lightweight, but greatly helps the loading speed. For optimal performance, you should load the Checkin.com script on page load, instead of importing it on a button click or with a function
-
Trigger the Checkin.com module directly on a landing page without re-directing first
-
Set the language to the same as is used on the parent site
-
The Checkin.com Framework is designed to handle traffic from all countries in the world, so you do not need to set the country manually
-
Clear and localized error messages give the user a better experience and increases the chance of the user coming back and converting at a later time
-
To make sure the legal content displayed within the Checkin.com module is always up to date, you can provide us with HTML pages which we can embed within the Checkin.com module. This way, legal documents will always be up to date with what you have without involving the integration team at Checkin.com. These HTML pages should only contain the legal content without menus and images
-
The Checkin.com sign-up flow is a front-end representational layer and you should have back-end validations in place to ensure you are not allowing customers you should not be allowing (such as from a country you do not support)
Testing
To make sure your integration is working as intended and in the best possible way, here are a few important scenarios to check:
- The Checkin.com modal is triggered properly
- When you have finalized a registration, the user or sign-up is created in your database
- If you try to register another one with the same details, an error should be thrown
Updated about 3 years ago