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

# Clickstream Event Parameters

## Description

* Auxiliary table containing additional parameters captured on each event tracked by the Rockerbox on-site pixel.
* Includes ecommerce context (e.g., product, revenue, order\_id) and marketing parameters parsed from landing page URLs (e.g., gclid, UTM values), passed through exactly as received from the pixel without additional processing.

***

## Table Creation

* This table is automatically created upon activation of the clickstream feature.
* Once the Clickstream dataset has been enabled by Rockerbox, the table will appear in your data warehouse as `ON_SITE_EVENTS_ALL_PAGES`.

***

## Partition Keys

* `date`

💡 **Note:** Leverage partition keys when querying the table to improve query efficiency.

***

## Logical Primary Key

While data warehouses do not enforce primary key constraints, the combination of `event_id` and `query_param_name` functions as the logical primary key for the table.

***

## Field Reference

| #  | Name               | Description                                                                                                                                                   | Type      |
| -- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- |
| 1  | event\_id          | A unique identifier for each action. Each event\_id from the Clickstream dataset will have multiple corresponding records in the Event Parameters table.      | str       |
| 2  | timestamp\_action  | Timestamp of when the action occurred                                                                                                                         | timestamp |
| 3  | action             | Name of the raw pixel event. This includes events for all conversion segments configured in Rockerbox + a page view.                                          | str       |
| 4  | category           | Categorization of query\_param\_name based on common variables required for Rockerbox implementation. Possible Values: conversion, marketing, tracking        | str       |
| 5  | query\_param\_name | The name of the parameter passed on the Rockerbox pixel (ex product, utm\_medium). Each event\_id will have multiple rows with query\_param\_names and values | str       |
| 6  | value              | The specific value passed on the query\_param\_name. For example, the query\_param\_name = order\_id will have values = each specific order\_id.              | str       |
| 7  | advertiser         | Rockerbox Account ID                                                                                                                                          | str       |
| 8  | date               | Date when the action occurred                                                                                                                                 | date      |
| 9  | identifier         | Advertiser-specific identifier                                                                                                                                | str       |
| 10 | report             | The name of the report                                                                                                                                        | str       |
| 11 | rb\_sync\_id       | Identifier used by Rockerbox to sync dataset to your warehouse                                                                                                | int       |
| 12 | updated\_at        | Time the cache record was updated most recently                                                                                                               | timestamp |

***

## Event categorization

Rockerbox categorizes query parameters based on common variables required for your Rockerbox implementation. This looks for an exact match of the query\_param\_name passed on your event to the below. Further customization of categories is not supported.

* **conversion:** action, email, external\_id, hash\_email, hash\_phone\_number, order\_id, phone\_number, referrer, revenue, script\_version, sessionid, source, uid, url
* **marketing:** contains 'utm', contains 'clid', query string parameter used for Rockerbox's standard integrations
* **tracking:** all other