Pixel

Also known as: Tracking pixel, Marketing pixel, 1x1 pixel, Web beacon

What is a pixel?

A pixel is a tiny piece of tracking code, usually combined with a 1x1 transparent image, that fires when a user loads a webpage or opens an email.

The fire signal does two things. It loads the invisible image from the ad platform's server. It sends back data: page URL, user ID (if known), browser fingerprint, and any custom event you defined.

That signal is the foundation of every conversion report, retargeting audience, and lookalike segment in modern digital advertising.

How a pixel works

The mechanics are simple. The implications are not.

The page-load sequence

1. A user visits example.com/checkout-success.
2. The browser parses the HTML. It hits a <script> tag from connect.facebook.net/en_US/fbevents.js.
3. The script runs. It sends a Purchase event to Meta's servers. The payload includes the Pixel ID, event name, value, currency, and any custom parameters.
4. Meta receives the event. It looks up the user via cookie or browser ID. If found, it records the conversion against any ad the user clicked recently.
5. Meta also adds the user to retargeting and lookalike audiences for that pixel.

The whole exchange takes 50 to 200 milliseconds.

Standard events vs custom events

Every major pixel supports two layers of data:

• Standard events. Pre-defined by the platform. Examples: PageView, ViewContent, AddToCart, Purchase, Lead. These get special treatment in reporting and optimization. Use them whenever possible.
• Custom events. Anything else. A B2B SaaS might fire a Demo Booked event, a Pricing Page Viewed event, or a Trial Activated event. Custom events still optimize delivery but don't get pre-built reports.

Pixel vs Conversions API (CAPI)

Browser pixels are increasingly unreliable. Apple's iOS 14 App Tracking Transparency, Safari ITP, third-party cookie restrictions, and ad blockers all degrade pixel accuracy. Chrome stepped back from full cookie deprecation in 2024, but the long arc of browser-side tracking is still down and to the right.

The companion technology is server-to-server tracking. Meta calls theirs Conversions API. Google calls it Enhanced Conversions. TikTok calls it Events API. The pattern is identical: your backend sends conversion events to the ad platform via an authenticated API call, bypassing the browser entirely.

Modern ad accounts run both: pixel on the browser, server-side on the backend. The platform deduplicates by event ID. Per Meta's own CAPI documentation, accounts that pair the pixel with CAPI typically recover meaningful share of otherwise-lost conversions, with reported match-rate improvements ranging from 10 to 30 percentage points.

Why pixels matter

Without a pixel, an ad platform sees the click but not the outcome. With a pixel:

• Conversion attribution becomes possible. The platform knows which ad drove the sale.
• The delivery algorithm gets smarter. Meta and Google use pixel data to find the audience most likely to convert.
• Retargeting unlocks. Anyone who fired the pixel can be re-served ads later.
• Lookalike audiences become possible. The platform finds new users who behave like your existing converters.

A campaign without a pixel installed leaves significant budget on the table. The platform has no signal to optimize against, no way to retarget warm visitors, and no audience seed for lookalikes. In practice, performance teams treat pixel installation as the non-negotiable first step before any spend goes live.

Real-world example: a pixel-driven funnel

A direct-to-consumer mattress brand installs the Meta Pixel on five pages:

Page	Event fired	Custom data
Home	PageView	none
Product detail	ViewContent	content_id, value
Add to cart	AddToCart	content_ids[], value, currency
Checkout start	InitiateCheckout	cart total
Order confirmation	Purchase	value, currency, content_ids[]

After two weeks, the pixel has fired 180,000 events. The brand can now:

• Build a retargeting audience of "AddToCart but not Purchase" users (8,400 people). Spend $20 daily, recover 11 percent of abandoned carts.
• Train a Purchase-optimized campaign on the 1,200 buyers. Cost per acquisition drops from $89 to $54 over 30 days.
• Generate a 1 percent lookalike from the buyer audience. Use it for cold prospecting. Conversion rates beat broad targeting by 2.3x.

None of those campaigns work without the pixel. All of them start with five lines of installed code.

Common pixel mistakes (and how to catch them)

Most underperforming ad accounts fail because of pixel hygiene, not budget or creative.

The five mistakes that ruin pixel data:

1. Installing the same pixel ID on every page, but never firing standard events. A PageView everywhere is not enough. Without Purchase, AddToCart, or Lead events, the delivery algorithm has no goal to optimize toward. Audit by running the Meta Pixel Helper on every key page and confirming the right event fires.
2. Firing the conversion event on the wrong page. A Purchase event that fires on the cart page (not the order-confirmation page) inflates conversions and trains the algorithm on garbage. Symptom: ROAS that looks great in the dashboard but doesn't match Stripe or Shopify revenue.
3. Double-firing. A pixel installed via Google Tag Manager and directly in the site theme will fire every event twice. Check the network tab on a test purchase. If you see two Purchase POSTs to facebook.com/tr, deduplicate.
4. Missing event_id for CAPI deduplication. When you pair browser pixel with server-side CAPI, both must send the same event_id for the same conversion. Without it, Meta counts one purchase twice. Result: inflated reported conversions, bad CPA targets, runaway spend.
5. Stale pixel from a closed campaign. Old pixels left on landing pages keep building stale audiences for ad accounts you no longer use. Audit twice a year. Remove anything that hasn't been touched in six months.

A 30-minute pixel audit recovers more conversion accuracy than a $5,000 creative refresh. Do it before you blame the algorithm.

Pixels in an AI ad platform

In a connected ad-creation-and-launch platform like Coinis, pixel management is automated.

When you connect your Meta ad account, the platform reads your existing pixel ID and event configuration. Generated ad creatives auto-tag with UTM parameters that match your standard events. Retargeting audiences pre-populate from existing pixel data the moment a campaign launches. The marketer never opens Events Manager to debug.

The pixel still fires the same way. The setup work disappears.

Related terms

• Meta Pixel Events
• Conversion Tracking
• Cookies
• Server Side Tracking
• Retargeting
• Attribution Window Meta

Frequently asked questions

What is the difference between a pixel and a cookie?

A pixel is the trigger. A cookie is the storage. The pixel fires when a page loads. It tells the ad platform 'this user just visited.' The cookie stores an ID for that user so the platform can recognize them next time. Pixels need cookies (or a similar identifier) to be useful for retargeting.

What is the Meta Pixel?

The Meta Pixel (formerly Facebook Pixel) is a JavaScript snippet you install on your website. It tracks every page view and every standard event (Purchase, Add to Cart, Lead, View Content). Meta uses that data to attribute conversions to ad spend, build retargeting audiences, and train its delivery algorithm. One Pixel ID per ad account.

Are pixels still working in 2026?

Yes, but with caveats. Browser-side pixels lose accuracy from iOS 14+ App Tracking Transparency, Safari ITP, and ad blockers. Chrome reversed its full third-party cookie deprecation plan in 2024 but still ships user-controlled restrictions. Most ad accounts now undercount browser-only conversions by 15 to 40 percent. The standard fix: pair the pixel with server-side tracking via Meta Conversions API or Google Enhanced Conversions.

How do you install a pixel?

Three options. Manual: paste the code into your site's <head> tag. Tag manager: add it as a custom HTML tag in Google Tag Manager. Plugin: install the platform-specific WordPress, Shopify, or Wix plugin. Tag managers are the standard because they support multiple pixels without code edits.

Can a pixel slow down your site?

Each pixel adds 30 to 80 KB of JavaScript and one network request. Five or six pixels noticeably slow down a slow site. Best practice: load pixels asynchronously, defer non-critical ones, and audit twice a year. If a pixel hasn't been used to track a campaign in six months, remove it.