Users, Events & Tracking

Twinalyze organizes your analytics data into three main parts: users, events, and properties.

Users

People who interact with your website or application.

Events

Actions performed by users, such as viewing a page or submitting a form.

Properties

Additional details about users, devices, pages, screens, and events.

How tracking works

A user visits your product

A user opens your website or application.

Twinalyze identifies the user

The SDK connects the activity with the available user, device, and session information.

An action is captured

Common actions are captured automatically. Business-specific actions can be sent as custom events.

Properties add context

Properties describe the page, screen, device, source, user, or action.

Insights appear in the dashboard

Twinalyze uses the collected data to generate reports and user behavior insights.

Understand the data model

A user opens a product page and adds a product to the cart.

{
  "userId": "user_1025",
  "eventName": "add_to_cart",
  "properties": {
    "productName": "Hair Clip",
    "price": 299,
    "pageUrl": "/products/hair-clip",
    "device": "Chrome Browser",
    "country": "India"
  }
}

Data type	Example	What it tells you
User	`user_1025`	Who performed the action
Event	`add_to_cart`	What action was performed
Properties	`productName`, `price`, `pageUrl`	Additional information about the action

An event tells you what happened. Properties explain where, how, and under what conditions it happened.

Users

A user represents a person interacting with your website or application. Twinalyze can associate user activity with:

User ID
Device ID
Session ID
Browser or device
Operating system
Country and city
First and last activity
User properties

Find users in the dashboard

Dashboard → Users

Page Insights

Understand how users interact with individual pages.

User Engagement

Analyze how actively users interact with your product.

User Retention

Measure how many users return over time.

User Growth

Track new, active, and returning user trends.

Events and properties

An event represents an action performed by a user. A property provides additional information about that action.

Event	Example properties
`page_view`	`page_url`, `page_title`, `referrer`
`elementClick`	`element_text`, `element_tag`
`formSubmit`	`form_id`, `form_name`, `page_url`
`add_to_cart`	`product_name`, `price`, `quantity`
`purchase_completed`	`order_id`, `revenue`, `currency`

Event vs property

Event	Property
Describes the action	Describes the action in more detail
`page_view`	`page_url`, `page_title`
`elementClick`	`element_text`, `element_id`
`add_to_cart`	`product_name`, `price`

How events are collected

Twinalyze supports two event collection methods.

Auto Capture

Automatically collects supported website and application activity.

Custom Events

Tracks important product or business actions defined by your team.

Type	Best used for	Examples
Auto Capture	Common user interactions	`page_view`, `elementClick`, `screenViewed`
Custom Event	Business-specific actions	`checkout_started`, `purchase_completed`

Auto Capture Events

Auto Capture Events are common actions tracked automatically by the Twinalyze SDK. They help you start collecting analytics data without manually adding tracking code for every basic interaction.

Install the SDK

Add the Twinalyze SDK to your website or application.

SDK detects supported activity

Twinalyze detects supported page, screen, lifecycle, form, and interaction events.

Events are sent to Twinalyze

Each event is sent with its source, timestamp, session information, and properties.

Manage events in the dashboard

View and control collected events from the Data section.

Available auto-captured events depend on the platform, SDK version, and enabled SDK configuration.

Auto-captured events by platform

Web
Android

Web auto capture tracks common actions performed on a website.

Event	What it tracks
`page_view`	When a user visits or navigates to a page
`elementClick`	When a user clicks a button, link, or element
`scrollDepth`	How far a user scrolls on a page
`formStart`	When a user starts interacting with a form
`formSubmit`	When a user submits a form
`searchResultsView`	When website search results are viewed

Common Web properties

Property	Example
`page_url`	`/pricing`
`page_title`	`Pricing`
`element_text`	`Start Free`
`element_tag`	`button`
`referrer`	`google.com`
`utm_source`	`google`

Explore Web SDK

Install the Web SDK and start collecting website activity.

Android auto capture tracks app screens, lifecycle activity, language, permissions, and app startup performance.

Event	What it tracks
App Language	The language currently used in the application
Splash Time	Time taken by the splash screen before the next screen opens
Screen Viewed	When a user views an activity or application screen
Fragment Viewed	When a user views a fragment
App in Background	When the application moves to the background
App in Foreground	When the application returns to the foreground
Permission	Permission request and permission response activity

Common Android properties

Property	Example
`appLanguage`	`English`
`splashTime`	`1.8 seconds`
`screenName`	`HomeActivity`
`screenClass`	`HomeActivity`
`fragmentName`	`ProductFragment`
`permissionName`	`POST_NOTIFICATIONS`
`permissionStatus`	`granted`
`appVersion`	`1.0.8`
`deviceModel`	`Samsung SM-A525F`

Explore Android SDK

Install the Android SDK and start collecting application activity.

Manage events

View and manage all tracked events from:

Dashboard → Data → Events

Twinalyze Data Events screen showing event names, sources, statuses, and visibility controls

Event controls

Control	Purpose
Event Name	Shows the system name of the event
Custom Event Name	Adds a readable dashboard name
Source	Shows whether the event came from Web, Android, or iOS
Auto Status	Controls automatic event collection
Manual Status	Controls manual event collection
Status	Activates or deactivates the event
Visible	Shows or hides the event in dashboard views
Search	Finds an event quickly

Disabling an important event can affect reports that use that event.

Manage properties

View collected properties from:

Dashboard → Data → Properties

Properties help you understand the context connected with each event. Common property categories include:

Event Properties

Information related to a specific user action.

User Properties

Information that describes an identified user.

Device Properties

Information about the user’s browser, device, or operating system.

When to use custom events

Use custom events for important actions that cannot be fully understood through auto capture.

Custom event	Meaning
`signup_completed`	User completed signup
`add_to_cart`	User added a product to the cart
`checkout_started`	User started checkout
`purchase_completed`	User completed a purchase
`payment_failed`	A payment attempt failed
`subscription_started`	User started a subscription

Let auto capture handle common interactions. Use custom events for important product, conversion, and revenue actions.

Best practices

Keep important auto events active

Page views, screen views, foreground, background, and session-related events are required for accurate basic analytics.

Use clear event names

Use readable names such as checkout_started, purchase_completed, and payment_failed.

Keep naming consistent

Follow the same naming format across Web, Android, iOS, and other platforms.

Add only useful properties

Add properties that help your team filter, segment, compare, or understand an event.

Do not send sensitive data

Never send passwords, access tokens, payment card information, or confidential personal information.

Test before production

Verify users, events, properties, sources, and sessions in a test project before releasing the integration.

Web SDK

Set up tracking for your website.

Android SDK

Set up tracking for your Android application.

‹Previous Learn how to maintain accurate and reliable analytics data.Next›

GETTING STARTED

ORGANIZATION & PROJECT

DATA

ADMINSTRATION

Users, Events & Tracking

Users

Events

Properties

How tracking works

Understand the data model

Users

Find users in the dashboard

Page Insights

User Engagement

User Retention

User Growth

Events and properties

Event vs property

How events are collected

Auto Capture

Custom Events

Auto Capture Events

Auto-captured events by platform

Common Web properties

Explore Web SDK

Common Android properties

Explore Android SDK

Manage events

Event controls

Manage properties

Event Properties

User Properties

Device Properties

When to use custom events

Best practices

Web SDK

Android SDK

Users

Events

Properties

​How tracking works

​Understand the data model

​Users

​Find users in the dashboard

Page Insights

User Engagement

User Retention

User Growth

​Events and properties

​Event vs property

​How events are collected

Auto Capture

Custom Events

​Auto Capture Events

​Auto-captured events by platform

​Common Web properties

Explore Web SDK

​Common Android properties

Explore Android SDK

​Manage events

​Event controls

​Manage properties

Event Properties

User Properties

Device Properties

​When to use custom events

​Best practices

Web SDK

Android SDK

How tracking works

Understand the data model

Users

Find users in the dashboard

Events and properties

Event vs property

How events are collected

Auto Capture Events

Auto-captured events by platform

Common Web properties

Common Android properties

Manage events

Event controls

Manage properties

When to use custom events

Best practices