The Problem with Pixels
Traditional browser-based tracking (pixels, JavaScript tags) is increasingly unreliable. Here's why:
Ad Blockers
- 26-40% of users run ad blockers that prevent tracking pixels from firing
- This means a significant chunk of your conversions simply disappear from your ad platform reports
- You're optimizing campaigns on incomplete data
Browser Privacy Restrictions
- Safari ITP (Intelligent Tracking Prevention) limits cookie lifetime to 7 days for third-party and 24 hours for some first-party cookies
- Firefox ETP (Enhanced Tracking Protection) blocks known tracking domains entirely
- Chrome is phasing out third-party cookies
- Result: attribution windows shrink and cross-session tracking breaks
iOS App Tracking Transparency (ATT)
- iOS 14.5+ requires users to opt in to tracking
- 75-85% of users decline, severely limiting Facebook and other platforms' ability to track conversions from mobile ads
Cross-Device Gaps
- A user clicks your ad on their phone but converts on their laptop
- Browser pixels can't connect these sessions
- The conversion goes unattributed
The Bottom Line
You're likely losing 20-40% of your conversion data with browser-only tracking. This means your ad platforms can't optimize properly, your ROAS looks worse than it actually is, and you're making budget decisions on bad data.
The Server-Side Solution
DealOracle sends conversion events directly from server to ad platform API — completely bypassing the browser.
How It's Different
| Browser Pixels | DealOracle Server-Side | |
|---|---|---|
| Where it runs | User's browser | DealOracle's servers |
| Blocked by ad blockers? | Yes | No |
| Affected by ITP/ETP? | Yes | No |
| Affected by iOS ATT? | Yes | Minimal impact |
| Works for offline conversions? | No | Yes |
| Requires user to be on-site? | Yes | No |
| Deduplication | Manual/none | Automatic |
Supported Platforms
DealOracle sends server-side events to:
- Facebook / Meta — Conversions API (CAPI)
- Google Ads — Enhanced Conversions / Offline Conversion Import
- TikTok — Events API
- Snapchat — Conversions API
- LinkedIn — Conversions API
Each integration is configured independently with its own credentials, event mappings, and settings.
How It Works
The server-side tracking flow is straightforward:
Step-by-Step Process
- Lead enters the system — Via CSV import, webhook, manual entry, or any other method
- Lead data is enriched — DealOracle captures and stores: email, phone, name, click IDs (fbclid, gclid), IP address, user agent
- You assign a disposition — When your sales process reaches an outcome (e.g., "Sold"), you set the disposition on the lead
- DealOracle fires conversion events — Automatically sends the event to all connected ad platforms with:
- Hashed PII (email, phone, name) for user matching
- Click IDs for direct attribution
- Conversion value and event name
- Event timestamp and deduplication ID
- Platform matches to ad click — The ad platform uses the hashed data to match the conversion back to the original ad click
- Attribution is restored — The conversion shows up in your ad platform reports, fueling better optimization
No Code Required
You don't need to write any code or install any tags. Once you connect your ad accounts and map your dispositions, everything is automatic. Just work your leads normally and DealOracle handles the rest.
Data Flow
Here's how data moves through the system:
┌─────────────────┐ ┌─────────────────┐ ┌───────────────────┐
│ Lead Sources │───▶│ DealOracle │───▶│ Ad Platforms │
│ │ │ │ │ │
│ • Facebook Ads │ │ • Lead stored │ │ • Facebook CAPI │
│ • Google Ads │ │ • Disposition │ │ • Google EC │
│ • TikTok Ads │ │ assigned │ │ • TikTok Events │
│ • Website Forms │ │ • Conversion │ │ • Snapchat CAPI │
│ • Phone Calls │ │ event fired │ │ • LinkedIn CAPI │
│ • Walk-ins │ │ • Hashed PII │ │ │
└─────────────────┘ │ + click IDs │ │ → Attribution │
└─────────────────┘ │ → Optimization │
│ → Better ROAS │
└───────────────────┘
Key Points
- Any lead source works — Whether the lead came from an ad, a phone call, or a walk-in, DealOracle can send conversion events for it
- Multi-platform simultaneously — One disposition change fires events to ALL connected platforms at once
- Offline conversions supported — Phone sales, in-person deals, and other offline events can be attributed back to the original ad click
- Real-time processing — Events are sent within seconds of the disposition change
Benefits
Higher Match Rates
Server-side tracking typically achieves 80-95% match rates compared to 40-60% with browser pixels alone. This means the vast majority of your conversions are properly attributed.
Offline Conversion Support
Track conversions that happen outside the browser:
- Phone sales
- In-person visits
- Deals closed days or weeks after the initial click
- Back-office processes (credit approval, contract signing)
Automatic Deduplication
DealOracle uses event IDs and platform-side deduplication to ensure each conversion is counted only once, even if you're also running browser pixels alongside server-side tracking.
Full Funnel Visibility
See the complete picture:
- Top of funnel — Ad click (from platform)
- Middle of funnel — Lead created, contacted, qualified (from DealOracle)
- Bottom of funnel — Sold, with value (sent back to platform)
Better Ad Optimization
With more complete and accurate conversion data:
- Ad platforms can better optimize delivery
- Lookalike audiences are built from more accurate seed data
- ROAS calculations reflect reality
- Budget allocation is based on real performance
Privacy Compliant
- All PII is SHA-256 hashed before transmission
- No raw personal data is sent to ad platforms
- Compatible with GDPR, CCPA, and other privacy regulations
- You control exactly what data is shared