---
title: "Intelligence Data Streams - Record Contents"
slug: "intelligence-data-streams-record-contents"
status: "new"
updated: 2026-05-21T15:32:50Z
published: 2026-05-21T15:32:50Z
canonical: "docs.mapp.com/intelligence-data-streams-record-contents"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Record Contents

## Overview

**Records** are the structured data units that Data Streams emits for every tracked interaction. Each record type captures one facet of the visitor's session: the page or event they triggered, the entities involved (product, user, campaign), and the environmental context (device, browser, location).

Records are delivered via the **Root Stream**, **Custom Streams**, the current **Raw Data Export**, and — for legacy field sets — the **Classic Raw Data Export**. This section documents the contents of each record type, the schema paths used on the record, the corresponding stream and export field names, and which channels each field is available in.

---

## Record Types

### Activity Records

*Capture user-triggered actions in real time.*

- [Pages](https://docs.mapp.com/docs/en/record-contents-page) — page view events with URL, title, and page-level metadata
- [Events](https://docs.mapp.com/docs/en/record-contents-action) — generic interaction events (clicks, custom actions)
- [Form](https://docs.mapp.com/docs/en/record-contents-form) — form interactions (submit, focus, field-level events)
- [Tracking Event](https://docs.mapp.com/docs/en/record-contents-tracking-event) — server-side / pixel-tracked events

### Aggregation Records

*Roll up multiple activity records over time or scope.*

- [Sessions](https://docs.mapp.com/docs/en/record-contents-session) — visitor session aggregates (start, end, page count, duration)
- [Orders](https://docs.mapp.com/docs/en/record-contents-order) — transaction records with order-line items, totals, status
- [Customer Journey](https://docs.mapp.com/docs/en/record-contents-customer-journey) — touchpoint sequence across sessions

### Entity Records

*Describe the business objects referenced by activity records.*

- [Product](https://docs.mapp.com/docs/en/record-contents-product) — product catalog data (SKU, name, category, price)
- [Users](https://docs.mapp.com/docs/en/record-contents-user) — visitor / customer identification and CRM attributes
- [Campaigns](https://docs.mapp.com/docs/en/record-contents-campaign) — campaign attribution (source, medium, campaign ID)
- [Media](https://docs.mapp.com/docs/en/record-contents-media) — media-asset interactions (video, audio, file)

### Environment Records

*Provide technical context for the visitor's device and connection.*

- [Visitor Environment](https://docs.mapp.com/docs/en/record-contents-visitor-environment) — device, browser, OS, platform, location, connection, visitor capabilities

---

## Common Conventions

Every Record Contents subpage follows the same layout and uses the same column conventions. Read this section once; the subpages assume you know it.

### Page Layout

Each record type has two parallel sections:

1. **Field Definitions** — semantic description of each field: name, schema path on the record, description, format, and notes. This is the canonical reference for what each field *means*.
2. **Stream and Export Mapping** — the same fields, mapped to their delivery channels. This is the reference for *where* each field is delivered.

The **Name / Object** column is shared between both tables and acts as the cross-reference anchor.

### Schema Paths vs. Stream Field Names

Records on the wire use **dot notation** (`hardware.deviceClass`, `browser.fullName`, `location.countryCode`). The **Custom Stream** and **Raw Data Export** flatten the same paths to **underscore notation** (`hardware_deviceClass`, `browser_fullName`, `location_countryCode`). Both refer to the same data.

### Mapping Table Columns

| Column | What it means |
| --- | --- |
| Name / Object | Human-readable field name, same as in Field Definitions. |
| Available in Root Stream | Tick = the field flows through the Root Stream as-is. |
| Field in Custom Stream | Underscore-notation field name in the Custom Stream output. |
| Available in Custom Stream | Tick = field is selectable in Custom Stream config. |
| File in the Raw Data Export | Which RDE file the field appears in (e.g. `pages`, `orders`). |
| Field in the Raw Data Export | Field name in the current RDE. |
| Available in Classic Raw Data Export | Tick = field is also exported in the Classic RDE. |

### Deprecated Fields

> Note
> 
> Some record types carry a legacy field set that is **only available in the Classic Raw Data Export**. These appear in a separate, callout-marked table after the modern field set. They are kept for backwards compatibility but should not be used for new integrations — use the modern fields above them instead.

Two record types currently carry deprecated subsets:

- [Visitor Environment](https://docs.mapp.com/docs/en/record-contents-visitor-environment) — legacy `device.*` fields and the entire Operating System (`os.*`) field set

---

## Related

- [Data Streams](https://docs.mapp.com/docs/data-streams)
- [Consuming Data Streams](https://docs.mapp.com/docs/consuming-data-streams)
- [Contents of Raw Data Tables](https://docs.mapp.com/docs/contents-of-raw-data-tables)