Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Event Action

Type

Proprieties

Description

Note

Sign Up Submitted

custom_event

  • name: Sign Up Submitted

A sign up request was submitted.

Sign Up Complete

custom_event

  • name: Sign Up Complete

  • Method: OTP , SMS OTP, Biometrics, Social, Auto Sign Up

  • Social Service: Apple, Facebook, Google

  • Biometrics: Face ID, Touch ID, Face, Fingerprint

  • hasInvitationCodeOnSignUp will be a boolean with options TRUE or FALSE (set to True if user signs up with Invitation Code)

  • invitationCodeOnSignupReferralCode will have the code the user inputted into the Invitation Code Field

  • Response Type Success

  • A sign up request was completed, i.e. the sign up form has been processed successfully by the server.

Face ID and Touch ID (iOS)

Face and Fingerprint (Android)

Sign In Submitted

custom_event

  • Name: Sign In Submitted

  • Method: OTP SMS OTP, Biometrics, Social, Auto Sign Up

A user started the signs in flow.

Sign In Complete

custom_event

  • Name: Sign In Complete

  • Method: OTP SMS OTP, Biometrics, Social, Auto Sign In

  • Social Service: Apple, Facebook, Google

  • Biometrics: Face ID, Touch ID, Face, Fingerprint

A sign in request was completed, i.e. the sign in form has been processed successfully by the server. IF a user successfully signs in as a registered user the event attribute Response will be marked as Success and if not as Failure with the reason recorded in event attribute response description

  • Face ID and Touch ID (iOS)

  • Face and Fingerprint (Android)

Error

custom_event

  • Name: Sign Up Failed | Sign In Failed | Error

  • Response Description: the message that gets displayed to the user, for example: “The code you entered doesn't match the code we sent. Check your messages and try typing it in again.“

  • Response: Failure

The sign up or sign in failed for some reason. The reason will be available in the “Root cause” attribute.

Sign Out Complete

custom_event

name: Sign Out Complete

A user successfully signs out of the website/mobile app

Sign In With OTP Request

custom_event

name:Sign in with OTP Request

signUpType:'Email' | 'Phone Number'

Everytime a user signs in with an OTP request

User Sign In

custom_event

name: User Sign In

signInType: SMS | Email

User Account Created

custom_event

name: User Account Created

signUpType: SMS | Email

BE event triggered every time a user is created in cognito

Sign Up Flow Successful

custom_event

name: Sign Up Flow Successful

signUpType: Email

triggers after signup and after being logged in

We should add SMS? Currently the system is set to support Email | Phone Number

Sign Up Successful

custom_event

name: Sign Up Successful

signUpType: Email

triggers after signup and after being logged in

We should add SMS? Currently the system is set to support Email | Phone Number

User Sign In

custom_event

name: User Sign In

signInType: SMS | Email

BE event triggered every time a user is created in cognito and taken further in the sign in process(autoSignIn)

Screen View

screen_view

screenName: /signup | /signin

Page View

custom_event

path: signup | /signin

when the user reaches sign in sign up page

Sign In Modal after Sign Up

custom event

Message: "Phone number | Email exists sign in prompt modal"

Page View

custom_event

path: /confirm-otp

the otp confirmation page

  • No labels