Menu
Menu Sheet Overlay
Search
Search Sheet

Tracking Pixel

Note: For projects using [Analytics Integrations](../../../progressive-web/latest/analytics/analytics-integrations-overview/) or its predecessor, the [Analytics Manager](../../../progressive-web/latest/analytics/legacy-analytics-manager/), this is handled by the Engagement Engine Connector.

Clients can send events to the Engagement Engine by embedded a tracking pixel with valid parameters representing required fields.

The tracking pixel expects the following parameters:

Field Type Description
slug String Unique project slug
channel String Which channel this data is arriving on
dimensions String URL-encoded JSON payload of key/values metadata
timestamp_local String The unix/epoch timestamp in milliseconds of the client when this request was sent
data String URL-encoded JSON payload containing action, category, and value keys

Calls to the tracking pixel are made with a GET request, similar to:

https://engagement-collector.mobify.net/s.gif?slug=exampleProject&timestamp_local=1455060799000&channel=web&dimension=%7B%22testDimension2%22%3A21.41%2C%22testDimension1%22%3A%22testValue%22%7D&data=%7B%22action%22%3A%22pageview%22%2C%22category%22%3A%22test%22%2C%22value%22%3Atrue%7D

For more details, please see the Tracking Pixel reference documentation

What's Next?

Review what events can be sent

Feedback

Was this page helpful?