Events from Pixel Tracking

See the Overview for details about setting up the Datacoral Collect Events Slice.

For tracking web pages, see Browser JS Tracking. We also support instrumentation in pure html environments like email using tracking pixels with static parameters that are pre-determined at the time of constructing the content (like email).

In the content include an image tag as given below:

<img style="display: none;" src="https://URL_ENDPOINT/i?&env=ENVIRONMENT&apiKey=API_KEY&e=pv&page=EMAIL&" />


<img style="display: none;" src="" />

In the above img tag, use the values corresponding to each environment for the query parameters where:

URL_ENDPOINT : The URL of your Datacoral Events API gateway. Ex.

API_KEY : The Datacoral API key to authorize the events invocations. Ex. 1js9q5Gqmk2VDv2omx2WI3yUGV0K7b464fWUJXDX

ENVIRONMENT : Set the environment as dev or prod, based on the emitter of the events

NAMESPACE : The name of this Tracker instance to include with events sent to the collector. The namespace argument attached to every event fired by the new tracker. This allows you to later identify which tracker fired which event if you have multiple trackers running. Ex. landing_pages

APP_ID : Name of application to include with events sent to the collector. The application ID is used to distinguish different applications that are being tracked by the same Snowplow stack. Ex. "finance" or "hr"

When sending unstructured event and custom contexts as part of pixel tracking, a URL-safe Base64 encoded values should be used for query parameters ue_px and cx respectively. Format the unstructured event as below:

"data": {
"name": "test event",
"data": {
"someProp": "someValue",
"otherProp": "otherValue"

Note: there is a wrapper data element which is not present in the window.datacoral('trackUnstructEvent', ...) call in the Browser JS Tracking example.

Base64 encoding the above value will result in


This value should be passed as ue_px query parameter.

Format the custom context(s) as below

"data": [ {
"name": "experiment",
"data": {
"fb_uid": '9999xyz'

Base64 encoding the above value will result in


This value should be passed as cx_query parameter.

So the final URL will look like

By default, dvce_created_tstamp column in Redshift will not be populated for pixel events. Instead collector_tstamp column can be used to sort the pixel events.

Optionally, you may include dtm query parameter to the pixel url to identify when the url itself is generated. This will be mapped to dvce_created_tstamp column.