Create and map the website data stream
A data stream carries the events your website connector captures into Data 360. This page creates that stream, maps its fields to the Data Model Objects (DMOs) Personalization reads from, and confirms records are arriving.
- 1 Website events captured by the SDK
- 2 Data stream Engagement or Profile category
- 3 Data Lake Object DLO — raw landing object
- 4 Data Model Object DMO — mapped fields
Create the data stream
- In Data 360, open the Data Streams tab and click New.
- Under Connected Sources, choose Website, then click Next.
- From the Website dropdown, select the website connector you configured.
- Select the events you want to capture, then click Next.
- Review the selected events and their fields, then click Next.
- Select the data space this stream belongs to.
- For each profile event, set Refresh Mode (see the callout below), then click Next.
- Click Deploy.
Map fields to DMOs
A data stream lands raw data in a Data Lake Object (DLO) — a landing table for externally ingested data. Personalization reads from Data Model Objects (DMOs) instead, so you map each DLO’s fields to the matching DMO fields; the exact mapping varies by organization. The connector typically needs these DMOs mapped:
- Behavioral Events — the on-site actions the SDK captures.
- Contact Point Address / Email / Phone — optional profile identifiers.
- Party Identification — the primary key used for identity resolution; any unique value works (for example a subscriber key or IP address).
Confirm data is arriving
- Open the deployed stream and check that it shows an active, successful run.
- Open the mapped DMO and confirm new records appear after a test site visit.
Discussion
Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).