Conversion pixel
Count conversions once, on your own domain.
The search.co pixel records page views, leads and purchases as first-party data from your own site. It honors your visitors’ consent choices and feeds one set of conversion numbers to your ad networks, your budget optimizer and your attribution reports.
Ask Brigham.aiIs ZEO.co’s conversion tracking working on every form, and are any ad networks counting the same lead twice?Why it exists
Every tool counts conversions a little differently.
- Data
- First-party, your domain
- Consent
- Follows your banner
- Sends to
- Google Ads, Meta and other major networks
- Also uses
- GA4 and Search Console
Open your ad networks, your analytics and your CRM, and ask each one how many leads you got last month. You will likely get three different answers. Each network counts with its own rules and its own windows, and each one tends to give itself credit.
That makes every budget decision harder. If one network says a campaign produced 40 leads and your CRM shows 22, which number do you trust when you move money?
The search.co pixel, part of the ROI.me ad engine built in, gives you one count. It records conversions as first-party data on your own domain, removes duplicates, and shares the same events with your connected networks and with search.co’s optimizer and attribution reports.
Tracking health
Know your tracking works before you trust it.
Broken tracking is quiet. A redesigned form stops firing its event, a thank-you page moves, and weeks later the optimizer is making decisions on half the data.
The health check tests your conversion events and shows which ones fire, which ones stopped, and which ones are counted twice. Each problem comes with the page and the likely cause.
- Pixel on all pagesYes
- Lead form events3 of 4 firing
- Purchase values passedYes
- Duplicate events1 found
- Consent mode connectedYes
What you get
Tracking built for decisions, not just dashboards.
First-party collection
Events are collected under your own domain, which tends to be more resilient than relying only on third-party scripts.
Consent-aware
Works with your consent banner. If a visitor declines, the pixel follows that choice.
Deduplication
The same lead reported by the browser and your server is counted once.
Values and revenue
Pass order values or lead values so reports can show revenue, not just counts.
Simple setup
One snippet, or a tag manager template. Mark forms, buttons and pages as conversions without code.
Breakage alerts
Get an email or Slack alert when a conversion event stops firing or spikes unusually.
Where events go
One stream of events, many places to use it.
Browser events and server events from your site are joined into one stream. From there, the same conversions reach your ad networks, your synced audiences and every search.co report.
You decide which events each destination receives, and you can turn sharing off for any network at any time.
Event log
See every conversion event and where it came from.
The event log lists each conversion type, how many fired, which source reported it and whether it was shared with your networks.
| Event | Count · 7 days | Source | Shared with networks |
|---|---|---|---|
| Loan application started | 312 | Pixel | Yes |
| Application submitted | 96 | Pixel + server | Yes, deduplicated |
| Call from site | 41 | Pixel | Yes |
| Pre-qualification form | 0 | Pixel | Stopped firing Oct 24 |
| Newsletter signup | 58 | Pixel | Not shared |
01
Choose what counts
Mark which events are conversions and which are only for reporting.
02
Choose what is shared
Decide which events each network receives. Nothing is sent that you did not select.
03
Spot gaps fast
An event that drops to zero is flagged the same day.
How it works
Install it once. Check it any time.
- 01
Add the snippet
Place one script on your site, or use the tag manager template. It loads from your own domain setup.
- 02
Connect consent
Point the pixel at your consent banner so it follows each visitor’s choices.
- 03
Mark conversions
Pick the forms, buttons, calls and pages that count, and add values where you have them.
- 04
Share and verify
Choose which events go to each network, then run the health check to confirm everything fires once.
One count everywhere
The same numbers in every report.
Because the optimizer, audiences and attribution reports all read the pixel, a conversion means the same thing on every screen. When the optimizer says a campaign costs $38 per lead, that is the same lead your attribution report and your weekly email show.
You can still compare against each network’s own reporting, which is useful for spotting where a platform is claiming more than it delivered.
Leads · pixel
96
↑ +8%
Leads · networks claim
131
↑ +21%
Duplicates removed
35
Revenue tracked
$48.2k
↑ +6%
Privacy
Tracking that respects your visitors.
First-party tracking is not a way around privacy choices. It is a cleaner way to measure the visitors who agreed to be measured.
Consent
3 checks- Follows your consent banner’s choices
- No advertising use without permission
- Withdrawn consent is honored on the next visit
Data
3 checks- Collected on your own domain
- You choose which events are shared
- Sensitive form fields are never captured
Control
3 checks- Export or delete your data
- Turn off sharing per network
- Remove an event from sharing at any time
The difference
One source of truth instead of several opinions.
Network tags only
- Each network counts by its own rules
- The same lead can be claimed several times
- Broken events go unnoticed for weeks
- Third-party scripts are more easily lost
- No link to your organic or AI search results
search.co pixel
- One count, shared with every network
- Duplicates removed before reporting
- Same-day alerts when events stop
- First-party collection on your domain
- Paid, organic and AI on one revenue line
Ask Brigham
Ask whether your numbers can be trusted.
Brigham reads the event log, health check and network reports, then tells you what to fix first.
Most of the gap is double counting. Your application form fires a browser event and a server event, and two networks each take credit for the same lead. The pixel counted 96 unique submissions. Separately, the pre-qualification form stopped firing on October 24, after the form was redesigned.
Recommended fixes
Sorted by impact
- 1
Fix the pre-qualification event
5 minThe form’s submit button changed. Re-mark it in the pixel settings and the event will resume.
- 2
Use the pixel as the conversion source
5 minSet the optimizer and reports to read pixel conversions so each lead counts once.
- 3
Pass loan values with submissions
30 minAdding an estimated value per application lets reports show revenue, not just lead counts.
Does the pixel get around ad blockers or consent banners?
No, and it is not meant to. It follows your consent settings, and some visitors will block tracking. First-party collection on your own domain is generally more resilient than third-party tags alone, but no tracking method sees everyone.
Do I still need my network tags?
You can keep them. Many teams use the pixel as the shared source of truth and send its events to each network, so all of them work from the same conversions.
What does it collect?
The events you choose: page views, form submissions, clicks on calls or buttons, purchases and their values. It does not capture the contents of sensitive form fields.
Does it work with GA4?
Yes. You can connect GA4 alongside the pixel and compare the two, or use GA4 as a conversion source if you prefer.
Get one honest count of your conversions.
Install the pixel, run the health check, and see which events are missing or double counted. Free for 7 days.
Check my conversion tracking and list any events that stopped firing or are being counted twice.