---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/segment/connections/sources/catalog/libraries/server/pixel-tracking-api#article
headline: Tracking Pixel API
description: Use Segment's Tracking Pixel API to track email opens, ad impressions, and checkout pages where JavaScript and POST requests aren't allowed.
url: https://www.twilio.com/docs/segment/connections/sources/catalog/libraries/server/pixel-tracking-api
inLanguage: en
dateModified: 2026-06-25T22:35:15.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Tracking Pixel API

Tracking pixels (also called a beacon, 1×1 gif, or clear gif) allow for tracking email opens, advertising impressions, and checkout pages where JavaScript and `POST` requests are disallowed, but where you *can* embed an image.

Follow Segment's [HTTP Tracking API](/docs/segment/connections/sources/catalog/libraries/server/http-api) to use the `/pixel` API endpoint, which accepts a base64 encoded URL `?data` parameter and returns a 1×1 transparent gif.

## Pixel API endpoint signature

```text title="Pixel API endpoint signature"
https://api.segment.io/v1/pixel/<METHOD ENDPOINT>?data=<base64-ENCODED-JSON>
```

> \[!NOTE]
>
> The base64 encoding is optional, however it prevents special character interpretation or muxing by browsers, or other tools that might interpret URLs. For example, the URL `https://www.example.com/` might be altered to `http%3A%2F%2Fwww.example.com` when appended to another URL, but the base64 version, `aHR0cHM6Ly93d3cuZXhhbXBsZS5jb20`, remains unchanged.

### Pixel Routes

```text
/v1/pixel/identify
/v1/pixel/group
/v1/pixel/alias
/v1/pixel/page
/v1/pixel/screen
/v1/pixel/track
```

Each endpoint *always* responds with a `200 <empty-gif>`, even if an error occurs.

### Example Email Opened event

#### Create the payload

```json title="Email Opened event payload"
{
  "writeKey": "YOUR_WRITE_KEY",
  "userId": "user_123",
  "event": "Email Opened",
  "properties": {
    "subject": "The Electric Daily",
    "email": "jane.kim@example.com"
  }
}
```

**Note:** you must include either a `userId` or `anonymousId` with every API call.

#### Encode it using base64 and make sure it's URL safe

You can accomplish this with [WindowBase64 methods](https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64/btoa):

```text title="base64-encoded payload"
eyJ3cml0ZUtleSI6ICJZT1VSX1dSSVRFX0tFWSIsICJ1c2VySWQiOiAiMDI1cGlrYWNodTAyNSIsICJldmVudCI6ICJFbWFpbCBPcGVuZWQiLCAicHJvcGVydGllcyI6IHsgICAic3ViamVjdCI6ICJUaGUgRWxlY3RyaWMgRGFpbHkiLCAgICJlbWFpbCI6ICJwZWVrQXRNZUBlbWFpbC5wb2tlIiB9fQ
```

#### If you choose not to encode your payload, send it like this instead

```text title="Unencoded pixel request"
https://api.segment.io/v1/pixel/track?userId=user_123&event=Email Opened&properties.subject=The Electric Daily&properties.email=jane.kim@example.com&writeKey=<YOUR_WRITE_KEY>
```

#### Add an image tag to your email newsletter with `src` pointing to a Pixel API route

```html title="Tracking pixel image tag"
<img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6ICJZT1VSX1dSSVRFX0tFWSIsICJ1c2VySWQiOiAiMDI1cGlrYWNodTAyNSIsICJldmVudCI6ICJFbWFpbCBPcGVuZWQiLCAicHJvcGVydGllcyI6IHsgICAic3ViamVjdCI6ICJUaGUgRWxlY3RyaWMgRGFpbHkiLCAgICJlbWFpbCI6ICJwZWVrQXRNZUBlbWFpbC5wb2tlIiB9fQ">
```