# Website and app event tracking for a sovereign CDP: SDKs, identity stitching and real-time profiles

> AI360 captures behavioural signals from websites, mobile apps and servers with first-party event SDKs and an HTTP API, stitches anonymous and known activity into one customer profile, transforms events in flight, and lands them in the governed lakehouse within seconds through StreamHouse. Because collection runs on your own domain and platform, the clickstream stays in your jurisdiction instead of flowing to a foreign tag vendor.

Source: https://datanature.ai/blog/website-app-event-tracking-sdk-cdp-identity-stitching
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-05

Transactions tell you what a customer did. Website and app behaviour tells you what they are about to do: comparing loan rates, abandoning an application, reading the cancellation page. A customer data platform that cannot see those signals is always late. This guide explains how AI360 collects behavioural events with first-party SDKs, and why that collection should run on your own platform.

## What does AI360 event collection capture?

| Source | How events are sent | Typical events |
|---|---|---|
| Websites | JavaScript SDK or tag on your own domain | Page views, clicks, form steps, calculator use, search |
| Mobile apps | Mobile SDKs | Screens, feature use, onboarding steps, push opens |
| Servers and back ends | Server SDKs and an HTTP API | Orders, application status changes, logins, payments |
| Existing instrumentation | A Segment-compatible API | Events from apps already instrumented for Segment-style `track`, `identify` and `page` calls |

Every event has a type, a timestamp, an anonymous ID, a user ID when known, and properties. Schemas are created and extended automatically, so a new property does not break the pipeline.

## Why collect first-party, on your own domain?

- **Data residency**: the clickstream is personal data. Collecting on your own platform keeps it in the country where you run DataNature, instead of sending it to a third-party tag vendor abroad.
- **Completeness**: collection on your own hostname is not treated as third-party tracking, so fewer events are lost to browser restrictions and blockers.
- **One copy**: events land straight in the lakehouse that already holds core and CRM data, so there is no second customer database to reconcile.
- **Control**: you decide which fields are kept, masked or dropped before anything is stored.

## How does identity stitching work?

A visitor is anonymous until they log in, apply or click an email link. AI360 links the two:

1. Every device gets an **anonymous ID** from the SDK.
2. When the visitor identifies themselves, an **identify** call links the anonymous ID to a known user ID.
3. Earlier anonymous events are **stitched** to that user, so the profile shows the full journey, including the browsing before login.
4. The user ID joins the **identity resolution** crosswalk in Silver, which links it to the customer key used across core, card, CRM and call data.

Stitching uses deterministic links (an identify call) for profile decisions. Probabilistic device matching can enrich analytics, but it is not used to contact anyone.

## What happens to events in flight?

Before events are stored, functions can run on each one:

- **Filter** bots, internal traffic and test events.
- **Enrich** with geography from IP, device and campaign attributes.
- **Mask or drop** fields that should never be stored, such as free-text inputs.
- **Deduplicate** retries so each event counts once.
- **Route** an event to several destinations: the lakehouse, a real-time scoring topic, or an analytics tool.

Failed events go to a dead-letter store for inspection, and a live event view shows payloads as they arrive while you instrument a new page.

## How do events reach real-time profiles?

Events flow through StreamHouse into Bronze Iceberg tables with exactly-once writes, and short-window features update within seconds: pages viewed in the last hour, applications started today, days since last login. AI360 Studio uses those features for intent scores and triggers, and Lakebase serves the current profile to apps and agents with fast reads. Batch models use the same events in Silver and Gold.

## How is consent handled?

- The SDK reads the visitor's consent choice and collects only the categories they allowed.
- Consent state is stored as an event and on the profile, so every later use can be checked.
- [DataNature Atlas](/platform/atlas) applies purpose policies: behavioural events used for analytics may not be used for marketing activation unless the customer consented to that purpose.
- Retention rules delete or anonymise raw events after the period your policy sets.

## What can you do with the signals?

- Call back customers who abandon a loan or insurance application, if they consented to contact.
- Help new users at the exact onboarding step where they stopped.
- Detect churn intent from visits to cancellation or porting pages.
- Feed fraud models with device and session behaviour.
- Personalize app content and offers in real time.

See the [AI360 use cases](/use-cases) for worked examples.

## Frequently asked questions

### Is this a replacement for Segment or another tag manager?

For collection into your own platform, yes: the SDKs and the Segment-compatible API cover the common `track`, `identify` and `page` patterns, and events land in your lakehouse instead of a vendor cloud. You can keep sending selected events on to analytics tools if you need them.

### Does server-side tracking still need a browser SDK?

Usually both: server events are reliable for transactions and status changes, and the browser or app SDK captures behaviour that never reaches a server.

### How fast are events available?

Seconds for streaming features and triggers through StreamHouse; batch tables refresh on the schedule you set.

## Sources

- [DataNature: what is a customer data platform](/blog/what-is-a-customer-data-platform-cdp-composable-sovereign)
- [DataNature: StreamHouse, the real-time hot path](/blog/streamhouse-real-time-hot-path-lakehouse)
- [DataNature product: AI360 Studio](/products/ai360-studio)

## How does DataNature Atlas keep this secure and compliant?

Governance is part of the architecture, not a separate tool bolted on later. [DataNature Atlas](/platform/atlas) is the platform's governance module:

- **Knows your data**: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
- **Controls access**: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
- **Governs AI**: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
- **Proves it**: lineage from source to metric to decision, and an audit log of who or what accessed which data.
- **Stays local**: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.

These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read [DataNature Atlas in depth](/blog/datanature-atlas-governance-rbac-abac-pii-masking) or see [security and compliance](/security).
