Every lost conversion costs you twice
Once in the sale you never made. Again in the ad spend you cannot attribute. Ad blockers, ITP restrictions, and consent fragmentation are silently erasing your analytics data — and inflating your cost per acquisition. Datafly Signal recovers what client-side tags lose.
20-40%
Blocked by ad blockers
Desktop visitors using ad-blocking software that hides your best customers from analytics
7 days
Safari cookie limit
ITP caps client-side cookies at 7 days — wiping attribution for returning shoppers
800KB+
Typical tag payload
Average weight of vendor tags on an e-commerce product page before any content loads
3-5%
Conversion rate impact
Revenue lost for every additional second of page load caused by third-party scripts
The hidden cost of client-side tags
Every vendor tag you add to your storefront introduces another point of failure — for performance, privacy, and measurement accuracy.
Ad blockers hide your best customers
20-40% of desktop visitors block analytics tags entirely. These are typically your most tech-savvy, highest-value shoppers — the exact audience you need to measure and retarget. Their conversions vanish from your reports.
Safari users vanish after 7 days
ITP caps client-side cookies at 7 days. A shopper who browses on Monday and buys on Saturday the following week is a brand new visitor in your analytics. Attribution, audiences, and retargeting all break.
Slow pages kill conversions
800KB+ of vendor JavaScript competes with your product images and checkout flow for bandwidth. Every additional second of load time costs 3-5% in conversions. On mobile networks, the impact is even worse.
How Datafly Signal fixes it
Replace every vendor tag with a single 4.2KB collector. Events are delivered server-to-server — invisible to ad blockers, exempt from ITP, and orders of magnitude faster.
Conversion recovery
Events flow through your own subdomain via first-party DNS A records, then server-to-server to vendor APIs. Ad blockers that target third-party domains never see the request. Your conversion data arrives complete.
- First-party delivery bypasses ad blockers
- Server-generated vendor IDs (
_ga,_fbp,_ttp) - Recovers 20-40% of previously invisible conversions
400-day attribution
Server-set cookies from your own subdomain are fully exempt from Safari's ITP restrictions. User identity persists for 400 days — not 7. Returning shoppers are recognised across their entire purchase journey.
- Server-set cookies survive ITP, not capped at 7 days
- DNS A record — not CNAME cloaking Safari can detect
- IndexedDB fallback for resilient vendor ID storage
Faster pages, more sales
Replace 800KB+ of vendor JavaScript with a single 4.2KB collector. Your product pages load faster, your Core Web Vitals improve, and your conversion rate recovers the 3-5% lost to slow load times.
- 4.2KB gzipped replaces all vendor tags
- Zero third-party JavaScript on your pages
- Measurable Core Web Vitals improvement
One event. Every vendor.
A single Purchase event from your checkout is simultaneously transformed and delivered to GA4, Meta Conversions API, TikTok Events API, Google Ads, and any other vendor — each receiving exactly the payload format they expect.
Pipeline configs are version-controlled YAML. Every change is audited with before/after diffs. Roll back any deployment in seconds.
- GA4 purchase event with full item arrays
- Meta CAPI with SHA-256 hashed PII and deduplication
- TikTok Events API with content parameters
- Google Ads enhanced conversions with hashed customer data
- Pinterest tag with line item details
# E-Commerce Purchase Pipeline
# Single event → multiple vendor deliveries
event: Purchase
source: web
org_data_layer:
schema: ecommerce/purchase-v2
pii:
email: sha256
phone: sha256
ip_address: mask
consent:
required: [analytics, marketing]
pipelines:
- vendor: google_analytics_4
event_name: purchase
mapping:
transaction_id: properties.order_id
value: properties.revenue
currency: properties.currency
items: properties.products | map(
item_id: sku,
item_name: name,
price: price,
quantity: quantity
)
- vendor: meta_conversions_api
event_name: Purchase
mapping:
event_id: properties.order_id
value: properties.revenue
currency: properties.currency
content_ids: properties.products[].sku
content_type: product
num_items: properties.products | lengthGDPR and CCPA. Built in, not bolted on.
Consent is enforced twice — first in the browser by Datafly.js, then again at delivery by the server. Even if a misconfiguration allows an event through collection, the second layer blocks delivery to any vendor the user has not consented to.
PII handling is configured at the organisation level and applied before any vendor pipeline sees the data. Hash, mask, strip, or pseudonymise — per field, per regulation.
Privacy & Consent
- Double consent enforcement — client-side and server-side
- Per-vendor consent category mapping (analytics, marketing, personalisation)
- CMP compatibility — OneTrust, CookieBot, TrustArc, Didomi, and custom
- SHA-256 hashing of email and phone before vendor delivery
- Full audit trail with before/after diffs on every configuration change
- Data residency control — your data never leaves your infrastructure
- Consent status changes between collection and delivery are caught and blocked
See what your analytics are missing
Book a technical walkthrough and we will show you exactly how much conversion data your current setup is losing — and how Datafly Signal recovers it.