A separate tab, separate numbers
The X account lives on its own: the export is pulled by hand, it is stale by the time the month closes, and X's share of the result stays a guess.
X Ads in the same report as every other channel
Valkiria connects to X Ads over official OAuth 1.0a, reads your ad accounts and puts X spend next to Meta, Google and TikTok in one set of metrics. It is a read integration: campaigns in X are still created and changed by a person.
Why X keeps falling out of the spend picture
Spend is visible, payback is not
Impressions and clicks sit in the account, but until they are reconciled with site conversions and the other channels, keep-or-kill is decided on instinct.
Ads API access is not automatic
X grants Ads API access by application and allowlist. Until it lands, campaign data is collected from exports and the report always trails the actual spend.
Three steps from connection to one picture
Connect over OAuth 1.0a
Official X Ads API authorisation. The token and token secret are stored encrypted, and access is revocable from Valkiria settings in one click.
Read the ad accounts
Valkiria requests your X ad accounts through the Ads API. While Ads API access is still pending, metrics arrive through an external data connector, CSV or manual entry.
Line X up with the rest
X spend, clicks and conversions land in the shared reports next to Meta, Google and TikTok. Not one change is written back to the X account.
What you get on the X channel
An official connection
OAuth 1.0a for the X Ads API: tokens are encrypted and access is revocable from Valkiria or from the connected-apps settings of your X account.
X accounts in the same list
X ad accounts, their currency and their status sit exactly where your Meta, Google and other platform accounts already are.
Campaigns and spend in one table
Date, campaign, impressions, clicks, CTR, CPC, spend and conversions — in the same shape as every other channel you run.
Data even without Ads API
While the X Ads API allowlist is pending, metrics come through an external data connector, a CSV export from the account, or manual entry.
X's honest share of the result
X is compared with the other platforms on identical metrics, so you see what the channel returns, not only what it spends.
Read-only by design
Valkiria never creates or edits X campaigns: after connecting, nothing inside your ad account changes.
In numbers
- 13
- ad platforms in one control room, X included
- 0
- changes made in your X account — the integration only reads
- 5
- languages for the interface and reports: ru, en, es, de, fr
Questions about the X Ads integration
Can Valkiria launch campaigns in X?
No. The X Ads integration is read-only: Valkiria reads ad accounts and performance, but does not create, edit or stop campaigns. Every action inside the X account is still taken by a person.
Do I need X Ads API access?
To read accounts directly, yes — X grants Ads API access by application and allowlist for both the app and the ad account. Until that is granted, X spend and campaign results can be loaded through an external data connector, a CSV export or manual entry.
Does this use OAuth 1.0a or OAuth 2.0?
The advertising side runs on OAuth 1.0a, because that is the token type the X Ads API accepts. OAuth 2.0 is used in Valkiria only for non-advertising X surfaces. Both token types are stored encrypted and can be revoked from settings.
What happens to the token if I disconnect X?
The token is deleted from Valkiria and syncing stops, while the performance data already loaded stays in your project reports. You can also revoke access on X's side, in the connected-apps settings of your account.
How many X accounts can I connect?
There is no fixed limit. Ad accounts attach to projects and clients, and reports can be read per account or across the whole portfolio at once, alongside every other platform.
Put X next to your other channels
Connecting takes a couple of minutes and only reads. Nothing inside your X ad account changes.