Campaings and Users Raw data Export

Created: 21.02.2023

Updated: 13.10.2023

Author: Alexander Sugakov

Data Retrieval

Data is exported uon request for a specific period to a folder with web authentication access. Separate files are created for each day within the folder. The export is done in CSV format (comma-separated).

One-time exports are stored in a subfolder /raw_data/.

Additionally, all clients have the option to enable automatic daily exports. Daily exports are stored in a subfolder /daily/. The data retention period for daily exports is 7 days, meaning that each day the data file from 8 days ago is deleted.

General Description

The exported files contain a stream of data obtained from integrations. All data is structured in the form of a flat table, where various types of events are listed, each of events has its own set of properties.

There are 7 types of events in the data, identified by the numbers in the 'type' column:

0 - Page View,

1 - Event Hit - an event sent to the platform,

2 - Variation Impression - impression of a variation,

3 - Variation Click - click on a variation (only for campaign types that track clicks),

4 - Widget Impression - impression of a recommendation widget,

5 - Product Impression - impression of a product in a recommendation widget,

6 - Product Click - click on a product in a recommendation widget.

7 - Visible Impression - campaign appearing in the user's viewport

Data Processing Recommendations

Since all user interactions with customers’ entities (website, application, etc.) are stored as separate rows, to obtain a complete list of events for a client, it is necessary to filter events based on the 'uid' column. To obtain a full list of a client's events within one session, you additionally need filter by the 'sessionId' column.

Therefore, to obtain customer purchases attributed to a campaign, it is necessary to select all unique customer’s purchases (to avoid duplicates) made after the Variation Impression event with the corresponding 'variationId' within the same session as the Variation Impression. You can use columns with campaigns, experiences, versions, and variations IDs and names to ideintify specific versions of specific campaigns.

It is recommended to analyze campaigns only within the scope of versions/tests. When changing experience settings or the distribution of users among variations (without adding/removing variations), all campaign IDs, experiences, and variations will remain unchanged. Only the version/test ID will change, but the distribution of variations among users will start anew, and the test concept itself may undergo significant changes.

We aslo typically recommend excluding outliers from calculations.

Data Structure

Field	Type	Value (default)	Description
type	Enum8	0 - Page View, 1 - Event Hit, 2 - Variation Impression 3 - Variation Click 4 - Widget Impression 5 - Product Impression 6 - Product Click 7 - Visible Impression	User interaction type
contextType	Enum8		Type of the page from which the event was sent, in accordance with the Page Context
contextData	Array(String)		The contents of the array with context data
uid	FixedString(32)		Internal customer identifier (slid)
sec	FixedString(24)		Section ID
moscowTime	DateTime		Date and time of the event (by default in UTC+3)
sessionId	FixedString(32)	1234567890	Internal session identifier
url	String	"https://www.example.com/?url_params=123"	URL from which the event was sent
audiences	Array(FixedString(24))	[1234567, 9876543]	List of audience ID’s where user belonged at the moment the event was triggered
browser	LowCardinality(String)	"Safari”	User's browser type
device	LowCardinality(String)	"Tablet”	User's device type
os	LowCardinality(String)	"Mac OS X”	User's operating system type
cuid	String		Client’s customer ID
hashedEmail	FixedString(64)		SHA256 or MD5 hashed email from Login / Signup events (hash type can be different)
eventId	FixedString(32)	12345	Unique event ID for the purpose of deduplication
eventType	LowCardinality(String)	“add-to-cart-v1”	Preset event type (for OOTB events)
eventName	LowCardinality(String)	"Purchase"	Event name (human-readable)
eventProperties	String		Event properties
eventValue	Uint32		Event value in cents, pence etc.
eventCurrency	LowCardinality(String)		Currency
uniqueTransactionId	String		Unique transaction identifier
eventCart	Array(Tuple[String, UInt32, UInt32])		Cart array
campaignId	FixedString(24)	123456	Campaign ID
experienceId	FixedString(24)	123456	Experience ID
versionId	FixedString(24)	123456	Test/version ID
variationId	Array(FixedString(24))	123456	Variation ID
campaignName	String	Campaign 1	Campaign name
experienceName	String	Experience 1	Experience name
versionName	String	Test 1	Test/version name
variationName	String	Variation 1	Variation name
control	Nullable	true	Indication that the current variation is a control group (baseline)
sku	Array(String)	[”12345”,”4567”]	Product SKU for view/click events in recommendations
strategyId	Array(FixedString(24))	[”126651”,”426356”]	Strategy ID (can be more than 1)
strategyName	String	Strategy 1	Strategy name (first in the list in case there are several)