Set up your first pixel for tracking
Wevion imports pixels from connected ad accounts automatically. Verify yours fires events at /pixels before launching.
Written By Salvatore Sinigaglia
Last updated About 5 hours ago
Wevion imports pixels from connected ad accounts automatically. Verify yours fires events at /pixels before launching.
Set up your first pixel for tracking
A pixel is the snippet that tracks conversions on your website. Wevion imports your existing pixels from connected ad accounts automatically. Open /pixels to verify yours is firing events before you launch.
Who is this for
Anyone launching a conversion-objective campaign (Sales, Leads, App Promotion). Awareness, Traffic, and Engagement objectives don't require a pixel.
What a pixel actually is
A pixel is a small JavaScript snippet you install once on your website. Every time a visitor does something you care about (page view, add to cart, purchase, signup), the pixel sends an event to the ad platform. The platform uses those events to:
- Attribute conversions back to the ad they came from
- Optimize delivery toward people likely to convert
- Build audiences based on behavior (retargeting, lookalikes)
Each ad platform has its own pixel: Meta Pixel, Google Tag, TikTok Pixel, Taboola Pixel, Snap Pixel. Wevion does not replace these — they remain installed and managed in your website / tag manager.
Before you start
You need at least one of:
- A pixel already installed on your site and firing events in the last 7 days, OR
- The ability to install a new pixel (access to your website code or your tag manager)
Pixel installation itself lives in your website CMS / GTM / developer code, not in Wevion. Wevion reads what already exists.
How Wevion finds your pixels
Pixels are read from the connected ad accounts during the initial sync (see Connect your first ad platform). Wevion pulls:
- Pixel ID and name
- Status (Active / Inactive)
- Last event timestamp
- Event types received (PageView, AddToCart, Purchase, etc.)
- Counts per event type for the last 7 days
This happens automatically. You don't import pixels manually.
How to verify a pixel is working
Step 1: Open the Pixels page
In the sidebar click Connect → Assets → Pixels or jump straight to /pixels. The page lists every pixel found across your connected ad accounts.
Step 2: Check the status badge
Step 3: Open a pixel to see event detail
Click any pixel row to open the detail drawer. You see:
- Last event time (should be within minutes if your site has traffic)
- Event types received with counts per day
- Top source domains (URLs the events came from)
- A Test events button that links to the native ad platform's test events tool
If you see at least 5+ events per day on the right event type (e.g. Purchase for an e-commerce campaign), your pixel is healthy.
How to set up a brand new pixel
Wevion does not create pixels on the platform side. To create a new pixel:
After creating, install the pixel on your site (via GTM, your CMS, or developer code). Within 15 minutes Wevion picks it up on the next platform sync.
For deeper platform-specific steps see the dedicated collections (e.g. Setting Up Meta Pixels).
Using your pixel in a campaign
When you launch a campaign in Campaign Creator, the pixel is one of the required fields for conversion-objective campaigns. Pick the pixel from a dropdown, then pick the conversion event (e.g. Purchase, Lead). Wevion validates the pixel is active before allowing publish.
What you'll see
A healthy pixel one day after setup:
- Active badge in green
- Last event timestamp within the last hour (assuming site traffic)
- Event types matching what your site sends
- Daily event counts trending stable or up
If you've installed a pixel and Wevion shows it Inactive after 24 hours, the most common causes are: pixel installed on wrong domain, GTM trigger not firing, ad blocker on your test browser. Test on a fresh browser session without ad blockers.
Common issues
- Pixel shown Inactive despite site traffic: install the pixel before the
</head>tag closes. Some templates inject it after analytics, causing race conditions. - Events arriving but with wrong values (e.g. all
Purchaseevents with $0): your e-commerce plugin is not passing the cart value to the pixel. Check your plugin / GTM dataLayer. - Pixel shows in Wevion but not in native Events Manager: cache. Force-sync from the pixel detail drawer.
- Duplicate events: your pixel is installed twice (often: once in CMS, once in GTM). Pick one and remove the other.
- Domain warning: pixel events are coming from a domain not verified on the platform side. Verify the domain in the platform's Business Manager / equivalent.
FAQ
Do I create pixels inside Wevion?
No. Wevion does not create pixels on the platform side — it imports your existing pixels from connected ad accounts automatically during the initial sync. You create a pixel in the platform's own tool (Meta Events Manager, Google Ads Conversions, TikTok Events Manager, Taboola Backstage, or Snapchat Events Manager), install it on your site, and Wevion reads what already exists.
Do I need a pixel for every campaign in Wevion?
No. You only need a pixel for conversion-objective campaigns — Sales, Leads, and App Promotion. Awareness, Traffic, and Engagement objectives don't require a pixel. When you launch a conversion campaign in Campaign Creator, Wevion makes the pixel a required field and validates it's active before allowing you to publish.
How do I check whether my pixel is working in Wevion?
Open the Pixels page (/pixels or Connect → Assets → Pixels) and check the status badge. Active (green) means it received events in the last 7 days; Inactive (gray) means no recent events; Error (red) flags a configuration problem. Click any pixel row to open the detail drawer with last event time, event types, and daily counts.
How long until Wevion picks up a new pixel?
Within 15 minutes, on the next platform sync. After you create the pixel in the platform's tool and install it on your site via GTM, your CMS, or developer code, Wevion picks it up automatically at /pixels. There's no manual import step — Wevion pulls pixel ID, status, last event timestamp, and event types from the connected ad account.
Why does Wevion show my pixel Inactive despite site traffic?
The most common causes are the pixel installed on the wrong domain, a GTM trigger not firing, or an ad blocker on your test browser. Install the pixel before the </head> tag closes to avoid race conditions, and test on a fresh browser session without ad blockers. Wevion marks a pixel Inactive when it receives no events in the last 7 days.