Need help?

Implementation Key Concepts

Checkin.com is a framework built to provide the best registration and KYC process available. It is continuously optimized based on user behavioral data, incorporates many third party providers, and is localized for all countries across the world out of the box - all designed to guarantee the highest conversion rate, the best quality of data, and a smooth and unique user experience.

Your Checkin.com flow should replace your current registration form and will be pre-configured to collect the exact same data - named and formatted accordingly - as you are already collecting today. By making sure you can re-use all your current API endpoints, your Checkin.com flow only requires a super simple front-end-only integration to get up and running in no time.

Technical Key Concepts

  • It is a front-end integration only
  • The sign-up flow is contextual: It can be triggered from any page and, once a sign-up is completed, you can re-direct anywhere
  • The solution is rendered seamlessly as part of your web and/or native application
    • On mobile devices it is offered as a full bleed experience for optimal conversion rate and user experience
    • On desktop the default (and recommended) way is to have it rendered as a modal to drive user interaction, but it can also be integrated in other ways depending on your
  • User data is sent continuously after each step of the user journey
  • Checkin.com provides a comprehensive SDK that will allow you to control all the stages of the flow
  • SDK functions to control the data flow changes are provided for storing and handling user data, as well as throwing errors and tracking the user journey
  • To ensure the highest data quality, your Checkin.com flow comes loaded with front-end validations, but back-end validations related to your user base (e.g. username taken, duplicate accounts) should be handled on your end
  • When a user has gone through the registration, the full set of collected user data will be available as a structure called data which will be pre-configured to fit your current backend in terms of labels, formats and expected values

Data flow Control

There are two main types of Data Events:

  • Complete Event: The user has gone through the full registration and the account should be created
  • Update Events: The user has entered new data, or changed previously entered data

Complete Event

  • Handled with the setOnComplete method
  • The user has gone through the full registration and you should create the user account
  • Here you can run your last round of validations based on the full user data
  • Always include a generic error in case something goes wrong while you are trying to save the user account
  • Re-direct or log the user in when the account has been successfully created

Update Events (can be used for)

  • Handled with the setOnUpdate method
  • Validations during the registration (e.g. duplicate accounts on email address)
  • Re-targeting (for customers who drop-off)
  • Internal tracking (e.g Google Analytics)

Updated about 1 year ago