BigQuery data specification
Data specification of Optimizely Experimentation data included in the BigQuery data export.
NoteThis is a third-party integration and is not an Optimizely subprocessor. See Optimizely's Third-Party Add-Ons & Platform Integration Terms.
This page describes the data schemas for Optimizely Experimentation data in BigQuery.
Decisions
Field | Type | Description |
|---|---|---|
| String | Event UUID generated by the client. Used to deduplicate events. |
| Integer | Event timestamp (in UTC). |
| String | Account identifier. |
| String | A unique identifier for the visitor. |
| String | Optimizely no longer automatically generates the |
| String | The ID of the campaign containing this experiment. |
| String | The ID of the experiment the visitor was assigned to. For Personalization campaigns, explicitly send |
| Integer | Integer-range partitioning column. Use |
| String | The ID of the variation the visitor was assigned to. For Personalization campaigns, explicitly send |
| String | User IP address. |
| String | User-agent. |
| Boolean | When set to This flag is independent of the IP anonymization setting in Account and Project settings. If this flag is |
| String | HTTP referer (the page from which the event was sent). |
| Boolean | A boolean indicating if the visitor is bucketed into the experiment based on the traffic allocation settings. If set to |
| String | Client engine string (for example, 'js' or 'node-sdk'). |
| String | Client version. |
| String | Client snippet revision. |
| array <id:String, type:String, value:String> | An array of user attributes (also known as segments). |
| Integer | Timestamp set by the server. Indicates when the event was processed by the server (in UTC). |
** Optimizely no longer automatically generates the session_id as of October 9, 2023, but you can add it manually. See the Experimentation Analytics October 2023 release notes.
Conversion
Field | Type | Description |
|---|---|---|
| String | Event UUID generated by the client. Used to deduplicate events. |
| Timestamp | Event timestamp in UTC. |
| String | Account identifier. |
| String | A unique identifier for the visitor. |
| String | Unique session ID. Optimizely no longer automatically generates the |
| String | Event entity identifier. |
| String | Event type (click, pageview, custom, or client_activation). |
| String | Human-readable event name from the client, or |
| String | (Optional) Only pass |
| Integer | Revenue (in cents). |
| Float | The value used to compute value or numeric metrics. |
| Integer | Quantity metric value. |
| String | User IP address. |
| String | User-agent. |
| Boolean | When set to This flag is independent of the IP anonymization setting in Account and Project settings. If this flag is |
| String | HTTP Referer (the page from which the event was sent). |
| String | Client engine string (for example, 'node-sdk'). |
| String | Client version. |
| String | Client snippet revision. |
| Array <id:String, name:String, type:String, value:String> | An array of user attributes (also known as segments). |
| Map <key:String, value:String> | Key-value pairs of event tags. |
| Map <key:String, value:String> | Key-value pairs defining properties of the event. The value must be a string. |
| Array <campaign_id:String, experiment_id:String, variation_id:string, is_holdback:Boolean> | An array of the campaigns, experiments, and variations the event is attributed to. Optimizely no longer automatically generates the |
| Integer | Timestamp set by the server. Indicates when the event was processed by the server (in UTC). |
** Optimizely no longer automatically generates the session_id and experiments fields as of October 9, 2023. See the Experimentation Analytics October 2023 release notes.
Updated 3 days ago
