Skip to main content
Referly Atlas sends your store’s events to X from its servers, through X’s Conversions API. X works a little differently from the other platforms: every conversion event has its own event ID in Events Manager, and every request has to be signed with the four keys of an X developer app. This guide walks you through collecting those values, adding the pixel in Atlas, and checking that events arrive.

​
Before you start

You need:
  • A store in Atlas that is set up and live. Only stores that are Running or Awaiting data send events. See Store statuses.
  • An X Ads account with a pixel (event source) and at least one conversion event in Events Manager. Atlas sends only events that have an event ID, so create the events you want to count first.
  • An X developer app with Ads API access approved. Atlas signs every request with the app’s API key, API key secret, access token and access token secret. Without approved Ads API access, X rejects the requests.
If this is your first pixel, read Pixels and destinations first: it explains what a pixel is in Atlas and what every pixel row shows.

​
Step 1: Find your Pixel ID

1

Open Events Manager

At ads.x.com, go to Tools, then Events Manager.
2

Open your event source

Select the event source (pixel) you advertise with.
3

Copy the Pixel ID

Copy the Pixel ID. It is short, for example abc12.
X’s own article: Web conversions. The same steps sit in the Where to find it tooltip beside the field in Atlas, and the How to find it link under the field opens X’s article.

​
Step 2: Find your event IDs and API keys

​
Event IDs

X creates one event ID per conversion event in Events Manager. Atlas sends an event only when it has an ID for it, so collect one for every event you want to send. You need at least one.
1

Open an event

In Events Manager, open the conversion event, for example your purchase event.
2

Copy the Event ID

Copy the Event ID. It looks like tw-abc12-abcd0.
3

Repeat for every event

Atlas has a row for each of these nine events: Page view, View content, Add to cart, Initiate checkout, Purchase, Lead, Sign up, Start trial and Subscribe.

​
API keys

The four keys live on one tab of your developer app.
1

Open your app's keys

In the X Developer portal, go to Apps, open your app, then Keys and tokens.
2

Copy the API key and API key secret

Copy both halves of the pair. X’s article: API key and secret.
3

Generate the access token and access token secret

Under Authentication Tokens, select Generate and copy both values. X’s article: OAuth 1.0a overview.
The four X developer app keys in the Add pixel dialog: API key, API key secret, Access token and Access token secret

​
Step 3: Add the pixel in Atlas

1

Open Pixels and destinations

In the left sidebar of Atlas, open Pixels and destinations for the store, then select + Add pixel.
2

Choose X

In the Add your tracking pixel dialog, select the X chip. Leave Method on Add a new pixel. If another store of your business already sends to this pixel, choose Use an existing pixel instead and Atlas copies its ids and keys to this store. See Use an existing pixel.
3

Paste the Pixel ID

Fill in Pixel ID. Name (optional) helps you tell pixels apart.
4

Add your event IDs

Under Event IDs, select Add event, pick the event and paste its ID. Repeat for every event you collected. There are no Events sent chips for X: the event ID rows are the event selection, and Atlas saves only when at least one row is filled in.
5

Paste the four keys

Fill in API key, API key secret, Access token and Access token secret. All four are required.
6

Save

Select Add pixel. Atlas shows the Pixel saved screen with a Data flowing badge.
Add pixel dialog with X selected, showing the Pixel ID, Event IDs rows and the API key fields On the Pixel saved screen, use You can verify that here to send a test event straight away. Atlas answers Test event accepted with the HTTP status X returned, or shows X’s own error message so you can correct an ID or a key.

​
Events Atlas sends to X

Each row in the table is one event ID row in Atlas. Add payment info and Search are not sent to X. Events without an event ID are skipped.

​
Verify that events arrive

  1. Send a test event. On the pixel row, open the row’s menu and choose Send test event. A toast confirms that X accepted the event, or shows X’s error. Test events time out after 10 seconds.
  2. Read the delivery line. The line under the pixel reads how many events reached X in the last 24 hours, for example 8 sent in 24 h, or 8 sent, 2 failed in 24 h when some were rejected. A green dot means Live: events are being sent. See Pixel states.
  3. Watch Live activity. Open Live activity in the left sidebar and filter by destination to see each event’s status and X’s response. See Live activity.
More pixel actions menu on a pixel row with Send test event and Event filters

​
X settings in Atlas

  • Events without an ID are skipped. The event ID rows decide what Atlas sends. To start sending a new event, select Edit on the pixel row, add a row for it under Event IDs and paste the ID from Events Manager. To stop sending one, remove its row.
  • The four developer keys sign every request. X’s Conversions API accepts only signed requests, so Atlas needs the API key, API key secret, access token and access token secret of one developer app with approved Ads API access. Atlas never shows a saved key again: to replace one, select Edit on the pixel row and paste the new value. A blank field keeps the saved value.

​
Troubleshooting

Atlas shows X’s error next to the test. Check the Pixel ID and the event IDs first, then the four keys: Atlas never shows a saved key again, so select Edit on the row and paste fresh values (a blank field keeps the saved value). Make sure all four keys come from the same developer app. Test events time out after 10 seconds, so a slow answer also counts as a failure: try once more.
Atlas sends only from stores that are Running or Awaiting data, only events that have an event ID row, and never test-mode orders. Check that the platform switch at the top of the X row is on, then open Live activity and read the Status column: Skipped means no consent, no identifiers X can match, or no event ID for that event, Filtered means an event filter stopped it, Deduped means the same event was already sent within 48 hours. See Delivery statuses.
The developer app needs approved Ads API access: without it, X refuses signed requests from that app. Make sure the app has been approved for Ads API access in the X Developer portal. Then confirm the access token and access token secret were generated under Authentication Tokens of that same app.

Pixels and destinations

Add, edit, test and detach pixels on any store.

Events

What each event means and which platform calls it what.

Conversions

Leads, sign ups, trials and subscriptions, and where they come from.

Live activity

Watch every event and X’s response as they happen.
Last modified on October 23, 2026