Auto Capture Events are events that Twinalyze tracks automatically from your website or app. This helps you start analytics faster without manually writing tracking code for every basic user action.Documentation Index
Fetch the complete documentation index at: https://docs.paraminternationalltd.com/llms.txt
Use this file to discover all available pages before exploring further.
Auto capture is useful for common actions like page views, screen views, clicks, sessions, app foreground/background, and basic navigation events.
How auto capture works
Events are sent to Twinalyze
Auto captured events are sent with event name, source, timestamp, and properties.
Auto captured events by platform
- Web
- Android
- iOS
Web auto capture
Web auto capture helps track common website activity.| Event | What it tracks |
|---|---|
page_view | When a user visits a page |
click | When a user clicks a button, link, or element |
scroll | When a user scrolls a page |
form_start | When a user starts filling a form |
form_submit | When a user submits a form |
session_start | When a website session starts |
session_end | When a website session ends |
Common Web properties
| Property | Example |
|---|---|
page_url | /pricing |
page_title | Pricing |
element_text | Start Free |
element_tag | button |
referrer | google.com |
utm_source | google |
Continue with Web SDK
Learn how to install Web SDK and start collecting website events.
Where to manage auto capture events
Auto captured events are managed from:Event controls in dashboard
| Control | Meaning |
|---|---|
| Event Name | System event name tracked by Twinalyze |
| Custom Event Name | Display name used in dashboard |
| Source | Platform where event comes from, such as Android, Web, or iOS |
| Auto Status | Controls auto capture for that event |
| Manual Status | Controls manual tracking for that event |
| Status | Enables or disables the event |
| Visible | Shows or hides the event in dashboard views |
| Search | Helps find events quickly |
Auto capture vs custom event
| Type | Use when | Example |
|---|---|---|
| Auto Capture | Twinalyze can track the action automatically | page_view, screenInfo, appForeground |
| Custom Event | You want to track business-specific actions | purchase_completed, trial_started, payment_failed |
Auto capture tracks common behavior. Custom events track actions that are unique to your business.
Example auto captured event
Example of an auto captured screen event:When to use custom events
Use custom events when the action is important for your business and cannot be fully understood through auto capture. Common custom event examples:| Custom event | Meaning |
|---|---|
signup_completed | User completed signup |
add_to_cart | User added product to cart |
checkout_started | User started checkout |
purchase_completed | User completed purchase |
payment_failed | Payment failed |
subscription_started | User started subscription |
Best practices
Keep important auto events active
Keep important auto events active
Events like page views, screen views, app foreground, app background, and sessions are important for basic analytics.
Use clear custom event names
Use clear custom event names
Use readable names like
purchase_completed, payment_failed, or signup_completed.Do not track every small action manually
Do not track every small action manually
Let auto capture handle common actions. Use custom events only for important business actions.
Check event visibility
Check event visibility
Keep important events visible so your team can use them in reports and dashboards.
Quick summary
| Question | Answer |
|---|---|
| What is auto capture? | Events tracked automatically by Twinalyze SDK |
| Where to manage events? | Data → Events |
| Which platforms support it? | Web, Android, and iOS |
| When to use manual events? | For business-specific actions |
| Can events be hidden? | Yes, using the Visible control |
| Can auto capture be disabled? | Yes, using Auto Status |