Skip to main content

Scheduled exports of raw analytics data

O
Written by Optimize Team
Updated today

This article describes how we handle scheduled exports of our raw analytics data to your systems.

What data can I schedule an export of?

You are able to export all of the reporting data we have access to, including Visitor IDs, Event Names, assigned Experiment IDs, Device lookup values like Browser and Device, Geo-lookup values like Country and City, Custom Data columns, etc.

A good place to visualise available data is in your experiment report:

Click download, and then select all the columns.

This will create a zipped CSV export, where you can see all columns.

Data schema

  • DID

    • Type: Number

    • Description: Your account ID reference

    • Example: 2000001

  • TID

    • Type: Number

    • Description: A grouped long number, with project ID + test ID.

    • Example: 28000012800002

  • ExperimentID

    • Type: Number

    • Description: Control/Variation ID

    • Example: 2800004

  • VID

    • Type: Number

    • Description: Visitor ID

    • Example: 4837610132999191134

  • SessionID

    • Type: Number

    • Description: Session ID

    • Example: 17098060654937991

  • EventName

    • Type: String

    • Description: Event name, or blank string if "view"

    • Example: "click_cta"

  • Browser

    • Type: String

    • Description: Browser name

    • Example: Firefox

  • Device

    • Type: String

    • Description: Computed device type

    • Example: desktop

  • UserAgent

    • Type: String

    • Description: Full user agent string

    • Example: "mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/122.0.0.0 safari/537.36"

  • Country

    • Type: String

    • Description: Geo-ip lookup for country

    • Example: United Kingdom

  • Region

    • Type: String

    • Description: Geo-up lookup for the State/Region

    • Example: Scotland

  • City

    • Type: String

    • Description: Geo-ip lookup for city

    • Example: London

  • IPAddress

    • Type: String

    • Description: User's IP Address, if captured.

    • Example: 123.123.123.1

  • DateString

    • Type: Date

    • Description: The date of the event

    • Example: 2024-03-07

  • TimeString

    • Type: DateTime

    • Description: Full datetime string of the event

    • Example: 2024-03-07 10:12:11

  • TimeZoneOffset

    • Type: Number

    • Description: Offset for the user's timezone

    • Example: 0

  • PropertiesJSON

    • Type: JSON

    • Description: Custom data columns for the event, or blank object if empty.

    • Example: {'1089550':'Chrome','1089557':'Windows 10'}

Available Destinations

This is a growing list for us, but current destinations include:

SFTP

For this, we will need the following:

  • Host / IP address

  • Port number, usually 22

  • Username

  • Password

  • Folder, if not /

Azure Blob Storage, AWS S3

For this, we will need the following:

  • Account name

  • Container name

  • Connection strings, if appropriate

  • Access keys, if appropriate

Snowflake (coming soon)

Soon, we will be able to upload your data into Snowflake in a shared Table.

Data will retain for a week, and we expect you to copy it out into your own tables using scheduled copy jobs in services like Snowpipe.

To do this, we will create a Direct Share, and just need to know which account to share data with.

How do I request a scheduled export

Create a support request for us, with a ticket in the support portal or an email to [email protected].

Did this answer your question?