Once the analytics scripts are connected to your project and the web link is created or updated, the following events will be automatically transmitted to your analytics system:
Onboarding Starts (Web2App onboarding is viewed):
Event name in analytics | Event parameters in analytics |
StartOnboarding | // projectName //versionId //urlAlias
If web Onboarding from AB test, thet next additional parameters will be sent: //abTestVariantId //abTestVariantName //abTestName //abTestId |
If onboarding from AB test:
Event name in analytics | Event parameters in analytics |
AbTestLoaded | //abTestVariantId //abTestVariantName //abTestName //abTestId |
Each Onboarding Screen Appears to the User:
Event name in analytics | Event parameters in analytics |
ScreenDidAppear | // screenID // screenName |
Different Button Presses on Each Screen:
The Header Screen (top panel) may contain 2 buttons:
Event name in analytics | Event parameters in analytics | Image with button as an example |
LefttNavbarButtonPressed | // screenID // screenName |
|
RightNavbarButtonPressed | // screenID // screenName |
|
Footer Screen (bottom panel) may also contain 2 buttons:
Event name in analytics | Event parameters in analytics | Image with button as an example |
FirstFooterButtonPressed | // screenID // screenName |
|
SecondFooterButtonPressed | // screenID // screenName |
|
For Screens Where Users Input Data or Select from a List (table cells):
Events about the user's input or selection will be sent. The following screens will send events about entered data:
Table Multiple Selection
Table Single Selection
Title/Subtitle/Field
2 Column/Multiple Selection
2 Column/Single Selection
Title/Subtitle/Calendar
Image/Title/Subtitle/Picker
Image/Title/Subtitle/Selection
The data entry parameter is sent when moving to the next screen:
Event name in analytics | Event parameters in analytics |
UserUpdatedValue | // screenID // screenName // userInputValue* // buttonTitle** |
* // userInputValue - This parameter contains a list of values entered by the user.
**//buttonTitle - This parameter includes the name of the table cell pressed by the user, transmitted for the following screens: Table Multiple Selection, Table Single Selection, 2-column Multiple Selection, 2-column Single Selection, Image Title Subtitle Selection.
After the User Presses a Button and moves to the Next Screen:
Event name in analytics | Event parameters in analytics |
ScreenDisappeared | // screenID // screenName // userInputValue // nextScreenId |
If the User Moves to the Next Screen Automatically Using the Timer Setting
(enabled by default for the following screens: Slider, Progress Bar/Title and can be enabled on any screen with the Timer option):
Event name in analytics | Event parameters in analytics |
SwitchedToNewScreenOnTimer | // screenID // screenName |
If Onboarding is Completed by the User
(user moves forward from the last screen of onboarding):
Event name in analytics | Event parameters in analytics |
OnboardingFinished | // userInputValues* |
* // userInputValues - This parameter contains a list of values entered by the user on all screens during onboarding.
Paywall events:
Paywall appears with selected product or user changes the selection(clicks on buttons with products):
Event name in analytics | Event parameters in analytics | Image with button as an example |
ProductSelected | //screenId //screenName //productId |  |
The users clicks on X button on the paywall
Event name in analytics | Event parameters in analytics | Image with button as an example |
CloseNavbarButtonPressed | //screenId //screenName |  |
The users clicks on Purchasre button on the paywall
Event name in analytics | Event parameters in analytics | Image with button as an example |
PurchaseFooterButtonPressed | //screenId //screenName | 
|
The users clicks on Restore button on the paywall
Event name in analytics | Event parameters in analytics |
RestoreFooterLabelPressed | //screenId //screenName |
Stripe user events
Those events will send of Stripe is connected to your project in Onboarding online and the Web onboarding was updated
The user has clicked on Purchase button on the paywall and stripe page is opened:
Event name in analytics | Event parameters in analytics | Image of Stripe page an example |
StripeCheckoutSessionCreated | //screenId //screenName //sessionId | 
|
The Stripe session was canceled by the user (for instance, he has clicked on back and goes to the paywall )
Event name in analytics | Event parameters in analytics |
StripeCheckoutSessionCancel | //screenId //screenName //sessionId |
The the user has purchased successfuly (for instance, he has clicked on back and goes to the paywall )
Event name in analytics | Event parameters in analytics |
StripeCheckoutSessionSuccess | //screenId //screenName //sessionId |
Cookies widges user events
If the users clicks on Accept on the Cookie policies widget
Event name in analytics | Event parameters in analytics | Image with button as an example |
AcceptCookiesPressed | //screenId //screenName |
 |
If the users clicks on Decline on the Cookie policies widget
Event name in analytics | Event parameters in analytics | Image with button as an example |
DeclineCookiesPressed | //screenId //screenName | 
|
WebHook events
Once webhook is sent on your Web2App onboarding screen
Event name in analytics | Event parameters in analytics |
HookEvent | //hook* |
*hook - parameter contains all hook data (for instance, {"input":"https://d....","init":{"method":"GET","headers":[],"body": }}} )
When webhook data is received:
Event name in analytics | Event parameters in analytics |
HookEventResult | //hook* |
*hook - contains data about hook response