Skip to main content
OpenAIAnthropicGooglePerplexityMetaMicrosoft
X Pixel native, marketing-gated
X (Twitter) PixelX (Twitter) Pixel·Ad pixel

x pixel on every wordpress site, native.

paste an X (Twitter) Pixel ID, save, and the snippet renders gated against marketing consent. PageView fires automatically. tailored audiences + conversion attribution for X Ads — no plugin tax.

free trial. no credit card. all 30 integrations included on every plan.

includedYovale WordPress Hosting — X Pixel
yovale.com/en/integrations/x-pixel
X (Twitter) Pixel · marketing consent

X Pixel layers inside every wordpress site.

X (formerly Twitter) renamed and redesigned ads.twitter.com to ads.x.com. Snippets and pixel IDs work the same, but old WordPress plugins that hardcoded twitter.com URLs broke silently.

01
save-time validation
regex `^[a-z0-9]{5,8}$` enforced in dashboard
02
render-time mirror
same regex re-checked in PHP
03
marketing consent gate
fires only after marketing_storage granted
04
head injection
snippet emitted in `wp_head` priority 1
01
X (Twitter) Pixel injector
02
tailored audiences ready
03
marketing-consent gated
04
no X plugin needed
status panel
X Ads
conversion + audiences
0 plugins
no X plugin needed
consent
fires after marketing consent
what you get

X Pixel that survives the next rebrand.

platform-level injection, marketing consent gated, no plugin to maintain.

Native injection

snippet renders from the platform, current X endpoints. no broken twitter.com URLs from a stale plugin.

capabilityX (Twitter) Pixel injector
Marketing-consent gated

fires only after marketing_storage = granted. EU traffic stays compliant.

capabilitytailored audiences ready
Pixel ID validated

5–8 lowercase alphanumeric enforced at save and at render. typos can't ship.

capabilitymarketing-consent gated
Tailored Audiences ready

PageView fires by default — start building tailored audiences for retargeting and lookalikes.

capabilityno X plugin needed
the problem

X (Twitter) Pixel installs are fragile — Twitter's three rebrands didn't help.

X (formerly Twitter) renamed and redesigned ads.twitter.com to ads.x.com. Snippets and pixel IDs work the same, but old WordPress plugins that hardcoded twitter.com URLs broke silently.

Yovale's injector is platform-rendered and uses the current X domain endpoints. No reliance on a community-maintained plugin to keep up with the rebrands.

platform layer

X Pixel below WordPress.

the snippet renders from Yovale's MU-plugin layer with current X endpoints.

X stays installed through theme switches, plugin audits, and X's next rebrand.

compliance

marketing consent enforced.

the X Pixel is gated behind marketing_storage — X's signal is for ad targeting.

EU traffic gets the right consent gate by default.

setup in the dashboard

paste your pixel ID. start attributing.

Yovale validates the 5–8 lowercase alphanumeric pixel ID at save. the snippet renders in `<head>` gated against marketing consent.

Pixel ID
o1z2xpixel_id

X issues this when you create a conversion event. format: 5–8 lowercase letters or digits.

where to find your pixel_id
1
Open Tracking → Ad Pixels

Find X (Twitter) Pixel in the dashboard's tracking panel.

2
Paste your pixel ID

Copy from ads.x.com → Tools → Conversion Tracking. format: 5–8 lowercase letters and digits.

3
Toggle on, save

Open your site. X Pixel Helper extension confirms the pixel fires.

X tailored audiences need ~100 unique users before they're targetable — ship the pixel early so audiences populate before campaign launch.

plugin tax vs platform-native

X Pixel plugin route vs yovale native injection.

included on every Yovale plan starting at $149/yr. no extra add-on, no per-tag charge.

what's included
  • X (Twitter) Pixel injector
  • tailored audiences ready
  • marketing-consent gated
  • no X plugin needed
  • edge-cache safe
X Pixel plugin route vs yovale native injection.
Pixel Plugin Route
Yovale Native
Where Pixel lives
WordPress plugin
platform MU-plugin
Rebrand handling
depends on plugin updates
platform-managed, current endpoints
ID validation
none
regex at save + render
Consent gating
depends on banner plugin
marketing consent class
Cache compatibility
varies
snippet baked into cached HTML
Annual cost
$0–$59/yr for X-aware plugin tier
$0 — included on every plan
faq

questions before you switch hosts for X (Twitter) Pixel.

Will X Pixel fire correctly with EU consent?

Yovale gates the Pixel behind marketing_storage. If the visitor declined marketing cookies, the Pixel doesn't render. Compliant under EU ePrivacy + GDPR.

Did the X rebrand break my old Twitter Pixel?

Pixel IDs and snippets work the same. What broke was plugins that hardcoded twitter.com URLs in their snippet output. Yovale's injector uses current X endpoints.

Does this support X server-side conversion API?

The browser-side Pixel ships from Yovale. Server-side conversion API runs from your application code, outside the WordPress page render.

Can I use X Pixel with GTM?

Yes. Manage X Pixel through your GTM container, or run direct through Yovale and skip GTM.

Will the page cache break the X Pixel?

No. The snippet is part of the cached HTML. Marketing consent state lives on a `<html>` class so the cache key stays page-level.

ready when you are

X Pixel on your WordPress site by day one.

free trial. no credit card. paste a pixel ID, save, and X Ads attribution starts.