X conversions, sent from your server
ROASaurus sends purchases, adds to cart, checkouts and page views to the X Ads API conversions endpoint. There is no browser pixel for X in ROASaurus: it receives server events only.
| X (Twitter) at a glance | |
|---|---|
| Connection | X Ads API web conversions, signed with OAuth 1.0a |
| Events | Purchase (required), add to cart, checkout initiated, page view, each as an Events Manager event id |
| Identifiers | twclid, hashed email, hashed phone (E.164); IP and user agent only with one of those |
| Credentials | Pixel ID, API key and secret, access token and secret |
| Browser pixel | No, server events only |
| Spend sync | Yes: campaign spend, impressions and clicks per day, after you connect the ad account under Setup › Ad spend |
What ROASaurus sends to X
X has no standard event names. Each event type is an event id you create in X Events Manager, such as tw-o1abc-o1def, and paste into ROASaurus. The purchase event id is required. Add to cart, checkout initiated and page view are optional; an event type without an id is not sent. Product views are not sent to X.
Each conversion lists identifiers: the twclid click id, the email hashed with SHA-256, and the phone in E.164 format, hashed. The IP address and user agent are added only next to one of those, because X counts them only in combination. ROASaurus also sends a conversion id, value, currency, number of items and the products. A conversion with no twclid, email or phone is skipped.
ROASaurus treats a delivery as sent only when X reports at least one processed conversion.
How to connect
- Get an X developer app with Ads API access.
- Generate OAuth 1.0a user tokens for a user with Ad Manager access to the ad account: you need the API key and secret plus the access token and secret.
- In X Events Manager, create an event per type you want and copy the event ids.
- In ROASaurus, go to Tracking & platforms, click Add pixel on the X card and enter the Pixel ID, the event ids and the four keys.
Limits
- No browser pixel: X receives server events only.
- X campaign spend syncs after you connect the ad account under Setup › Ad spend.
- A twclid alone does not create an attribution touch. Tag your X ads with UTM parameters so the visits show up in attribution by source and campaign.
Related
Questions, answered
Why does X need four keys?
The X Ads API requires OAuth 1.0a for custom integrations. Every request is signed with your app's API key and secret and the access token and secret of a user who can manage the ad account.
Does ROASaurus load the X pixel?
No. X receives server events only. Conversions match on the twclid click id or the hashed email or phone of the shopper.
Which X events can I send?
Purchase, add to cart, checkout initiated and page view. Create each one in X Events Manager and paste its event id. Only purchase is required.
Every sale, traced to the ad that earned it
Server-side tracking, profit and lifetime value in one app. 14-day free trial, no credit card.
Start your free trial →