Tracking users and events accurately is fundamental for understanding customer behavior, optimizing marketing strategies, and driving business growth. NVECTA offers multiple methods to capture user data through different channels and integrations.
This guide helps you select the most suitable tracking method based on your architecture, data needs, and infrastructure.
| Method | What It Does | Latency |
|---|---|---|
| Client-Side SDKs | Captures user interactions directly from the browser or mobile app | Real-time |
| Server-Side SDKs | Sends events from your backend servers to NVECTA | Real-time |
| Integrations | Imports data from third-party services or file uploads | Batch |
| Warehouse Connectors | Syncs data from your existing data warehouse | Batch / Scheduled |
| Direct API Ingestion | Sends events via raw HTTP requests without using an SDK | Real-time |
| Streaming | Ingests events from a real-time event stream (Kafka, Kinesis) | Real-time |
Client-side SDKs are libraries you install in your website or mobile app code. They run on the user's device (browser or the phone) and capture interactions as they happen.
The SDK automatically captures device-level context, such as device type, OS, browser, screen resolution, location, and UTM parameters, along with any custom events you define.
Ecommerce: Track product views and cart additions to trigger abandoned cart emails.
nvecta.track("add_to_cart", {
product_name: "AirStride Pro",
sku: "SN-001",
price: 99.95
});
BFSI: Track loan application funnel steps to identify drop-off points.
nvecta.track("loan_application_started", {
loan_type: "personal",
requested_amount: 500000
});