Upload custom Events and Web Tracking

Updated by Ole Dallerup

Custom Upload is available to Enterprise customers.
Before uploading custom event data, it is recommended to check out the Google Sheet integration or Servcer-Side tracking. That is typically easier and faster to implement, while also being available to all paid plans.

You can read more about fileformat and how to upload customer data to Dreamdata here.

Below, you'll find the schema expected for a events and web tracking upload.

Events

Uploading custom events are typically custom events coming from a service you are using, that Dreamdata does not yet support or is from your own build service, such as your product.

Fields

Type

Nullable?

Data Examples

Comment

id

STRING

FALSE

Id of the event

event

STRING

FALSE

task, demo_request, activity

Event name, as such this is free text. However if you use the typical event examples it will be easier to Dreamdata to guess what kind of an event this is.

timestamp

TIMESTAMP

FALSE

2020-11-21T12:23:00.563Z

Timestamp of the event

email

STRING

TRUE*

friends@dreamdata.io

The email address of the user.

*Either email or domain has to be set

domain

STRING

TRUE*

dreamdata.com

The domain of the company from visiting the site.

*Either email or domain has to be set

is_single_session

BOOLEAN

TRUE

Set to true if event should be its own session. Default: false

properties

JSON

TRUE

{"name":"John", "age":30, "car":null}

Additional properties attached from your solution.

Web Tracking Events

Uploading custom web-tracking is typically used when uploading data from tracking solutions Dreamdata does not yet support out of the box such as Snowplow, a home build or open-source tracking solution.

Fields

Type

Nullable?

Data Examples

Comment

id

STRING

FALSE

Id of the event

event

STRING

FALSE

page_view, demo_request

Event name, as such this is free text. However if you use the typical event examples it will be easier to Dreamdata to guess what kind of an event this is.

timestamp

TIMESTAMP

FALSE

2020-11-21T12:23:00.563Z

Timestamp of the event

user_id

STRING

TRUE*

The id of the user, this could example be the cookie id.

*Either user_id, email or domain has to be set

email

STRING

TRUE*

friends@dreamdata.io

The email address of the user.

*Either user_id, email or domain has to be set

domain

STRING

TRUE*

dreamdata.com

The domain of the company from visiting the site.

*Either user_id, email or domain has to be set

url

STRING

TRUE

https://dreamdata.io/data-platform

Mostly relevant when the event is from web

referrer

STRING

TRUE

https://google.com/

Mostly relevant when the event is from web

utm_source

STRING

TRUE

google

utm_medium

STRING

TRUE

cpc

utm_campaign

STRING

TRUE

revenue_attribution

utm_term

STRING

TRUE

b2b attribution

properties

JSON

TRUE

{"name":"John", "age":30, "car":null}

Additional properties attached from your tracking solution.

How did we do?