Tracking Event

Overview

This page groups the metadata that wraps every tracking event sent to the Mapp Intelligence platform: the request identifiers and timestamps captured on the wire (Basic), server-side ingestion details added by the tracking server (Meta), and the account identification used to route the event (Account).

Together they form the envelope around the business payload of every tracked Page, Event, Media, Form, Order, or Campaign record.

Field Definitions

Basic

Name / Object	Key on Record	Description	Format	Comment
Tracking Request Id	`id`	Unique identifier of the tracking event.	`String`	This ID always refers to the current event, so the ID depends on what kind of event it is (for example, if it is a form event, then form_request_id is displayed here).
Tracking Timestamp	`timestamp`	The instant when our pixel/ SDK tracked the event.	`String` (ISO 8601 Date Time with Offset : YYYY-MM-ddTHH:mm:ssZ)	The time is for the respective action/event.
Referrer URL	`referrerUrl`	The referrer URL of the tracked event.	`String`	Contains the information provided by the Pixel Tracking script. In general, it contains the complete URL, for example " http://www.example.com/path?param1=xx&param2=yy" Referrer values: "0" = page without referrer; "1" = referrer domain equals current domain; "2" = referrer sent for this page; null = no referrer provided (e.g. Heatmap request).

Name / Object	Key on Record	Description	Format
Ingestion timestamp	`eventMetadata.ingestionTimestamp`	The UTC timestamp when the event was accepted by the tracking server.	`Long`
Tracking server ID	`eventMetadata.source`	Server ID on which the request was initially received.	`Text`
Version of the event schema	`eventMetadata.version`	The version of the event schema.	`Text`
Detected tracking context	`processingMetadata.detectedContext`	Detected type of event. Values: Page, Action, Heatmap or Unknown.	`Text`

Account

Name / Object	Key on Record	Description	Format	Comment
Track ID	`account.id`	You customer account identification.	`String`

Stream and Export Mapping

The same fields, mapped to their availability in the Root Stream, Custom Streams, the current Raw Data Export, and the Classic Raw Data Export. Use the Name / Object column to cross-reference rows with Field Definitions above.

Basic

Name / Object	Field in Custom Stream	File in the Raw Data Export	Field in the Raw Data Export
Tracking Request Id	`id`	Depends on the event type.	DEPENDS (for example, request_id, form_request_id)
Tracking Timestamp	`timestamp`	Most files	`times`
Referrer URL	`referrerUrl`

Account

Name / Object	Available in Root Stream	Field in Custom Stream	Available in Custom Stream	File in the Raw Data Export	Field in the Raw Data Export	Available in Classic Raw Data Export
Track ID		`account_id`

Contents of Raw Data Tables

Name / Object	Available in Root Stream	Field in Custom Stream	Available in Custom Stream	File in the Raw Data Export	Field in the Raw Data Export	Available in Classic Raw Data Export
Ingestion timestamp		`eventMetadata_ingestionTimestamp`
Tracking server ID		`eventMetadata_source`
Version of the event schema		`eventMetadata_version`
Detected tracking context		`processingMetadata_detectedContext`

Tracking Event

Overview

Field Definitions

Basic

Meta

Account

Stream and Export Mapping

Basic

Meta

Account

Related