Perspection vs Zaraz: Conversion Depth vs Edge Speed

What is the core difference between Perspection and Cloudflare Zaraz?

Cloudflare Zaraz intercepts tracking requests at the CDN edge and forwards events to ad platforms from Cloudflare's infrastructure, eliminating third-party browser scripts and improving page load times. Perspection processes events through a 5-stage pipeline (validate, deduplicate, normalize, enrich, dispatch) with platform-specific formatting, EMQ coaching, click-ID vault storage, and dead-letter queue retry — focusing on conversion delivery accuracy rather than page performance.

Zaraz takes a unique architectural approach to server-side tracking. Rather than running a separate server-side container (like sGTM on GCP), Zaraz embeds tag execution directly into Cloudflare's edge workers. When a visitor loads a page behind Cloudflare, Zaraz intercepts tracking calls at the CDN level and processes tags without any third-party JavaScript reaching the browser.

Perspection takes a pipeline-first approach. Events enter Perspection through a tracking endpoint and pass through validation, deduplication, normalization, enrichment, and dispatch stages before reaching ad platforms. The pipeline architecture enables features that edge-based tag execution cannot provide: cross-event deduplication, click-ID enrichment from a 90-day vault, and dead-letter queue retry for failed deliveries.

How do Zaraz and Perspection compare on features?

Zaraz optimizes for performance and privacy by executing tags at the CDN edge without browser-side JavaScript. Perspection optimizes for conversion accuracy by processing events through a multi-stage pipeline with platform-specific formatting, EMQ scoring, click-ID enrichment, and delivery retry. The two platforms solve different problems in the conversion tracking stack.

Does Zaraz improve conversion tracking accuracy?

Zaraz improves event collection reliability by eliminating browser-side script blocking, ad blockers, and third-party cookie restrictions — more events reach ad platforms compared to client-side tagging. However, Zaraz does not score Event Match Quality, store click IDs for cross-session enrichment, retry failed deliveries, or reconcile conversion counts against platform APIs. Perspection addresses all four of those conversion accuracy gaps.

Zaraz solves the "event collection" problem: ensuring tracking events fire reliably without browser interference. Perspection solves the "event delivery" problem: ensuring collected events reach ad platforms with maximum match quality and delivery reliability.

Collection and delivery are sequential problems in the conversion tracking pipeline. An event must first be collected (where Zaraz excels) and then delivered with high quality (where Perspection excels).

How does each platform handle identity and attribution?

Zaraz does not provide identity stitching or cross-device attribution capabilities. Zaraz forwards events from the edge to ad platforms without linking anonymous sessions to known users. Perspection provides server-side identity stitching with a device graph that connects anonymous browsing sessions across devices and browsers to known user identities, improving conversion match rates for ad platforms.

Perspection's 90-day click-ID vault stores click identifiers (fbclid, gclid, ttclid, and others) in a two-tier architecture: Redis for 7-day hot lookups and PostgreSQL for 90-day persistent storage. When a visitor clicks an ad but converts days or weeks later, Perspection can enrich the conversion event with the original click ID — a capability that Zaraz's stateless edge architecture cannot provide.

The combination of identity stitching and click-ID enrichment is particularly valuable for e-commerce businesses with longer consideration periods. A visitor who clicks a Meta ad on Monday and purchases on Friday benefits from Perspection's ability to link both sessions and attach the original fbclid to the purchase event.

Does Zaraz require Cloudflare as DNS provider?

Yes, Zaraz requires the website to use Cloudflare as the DNS provider and CDN. Websites not using Cloudflare cannot use Zaraz. Perspection works with any DNS provider and offers auto DNS provisioning for 5 major DNS providers with automatic TLS certificate management, removing DNS vendor lock-in from the tracking infrastructure decision.

The Cloudflare requirement is Zaraz's most significant limitation for teams evaluating server-side tracking options. Teams already using Cloudflare get Zaraz as a built-in feature. Teams using AWS Route 53, Google Cloud DNS, or other providers would need to migrate DNS to Cloudflare to use Zaraz.

Perspection supports auto DNS provisioning across 5 DNS providers — including providers commonly used by e-commerce businesses — with automatic TLS certificate management. Teams configure first-party tracking domains through the Perspection dashboard without manual DNS record creation or certificate provisioning.

How does each platform handle consent?

Zaraz provides basic Google Consent Mode integration and can block specific tools based on consent state configured in the Cloudflare dashboard. Perspection enforces consent at the processing-pipeline level with 3 enforcement modes — Strict (block unless explicit consent), Standard (honor consent signals), Permissive (collect with opt-out) — and forwards Google Consent Mode v2 signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) to all downstream destinations with automatic SHA-256 PII hashing.

Perspection's consent enforcement applies uniformly across all 9 ad destinations — a single configuration choice determines how consent rules apply to Meta CAPI, Google Ads, TikTok Events API, and every other connected destination. Zaraz requires consent configuration per tool in the Cloudflare dashboard, adding configuration overhead as the number of tracked destinations increases.

Perspection also applies automatic SHA-256 hashing to all PII fields (email, phone, name) before events leave the pipeline. Ad platforms require hashed PII for identity matching, and Perspection handles the hashing without manual configuration — ensuring both privacy compliance and ad-platform API requirements are met simultaneously.

When should a team choose Cloudflare Zaraz?

Teams should choose Zaraz when page performance is the primary tracking concern. Zaraz excels at:

• Page speed optimization: Teams where Core Web Vitals scores and page load times directly impact conversion rates benefit from Zaraz's elimination of third-party tracking scripts.

• Existing Cloudflare infrastructure: Teams already using Cloudflare for DNS and CDN get Zaraz as a built-in feature with no additional infrastructure to manage.

• Simple tracking setups: Teams with straightforward tracking needs (GA4 + one or two ad platforms) benefit from Zaraz's simple dashboard configuration.

• Ad blocker bypass: Teams losing significant event volume to browser ad blockers benefit from Zaraz's edge-based execution that avoids ad blocker detection.

When should a team choose Perspection?

Teams should choose Perspection when conversion delivery accuracy and reliability matter more than page load performance. Perspection excels at:

• E-commerce conversion accuracy: Online stores running paid campaigns across 9 ad platforms need EMQ coaching, click-ID enrichment, and platform-specific event formatting to maximize Return on Ad Spend.

• Delivery reliability: Teams that cannot afford lost conversions benefit from Perspection's DLQ with 4 retry strategies and revenue-impact tracking — features Zaraz does not provide.

• Multi-platform campaigns: Teams advertising across Meta, Google, TikTok, Pinterest, Snapchat, LinkedIn, Reddit, and Bing get all destinations pre-configured with optimized formatting.

• APAC marketplace operations: Teams selling on Shopee and Lazada need COD confirmation tracking and marketplace-specific integrations.

• DNS provider flexibility: Teams not using Cloudflare — or teams unwilling to lock DNS infrastructure to a single vendor — need a tracking solution that works with any DNS provider.

• Complementary deployment with Zaraz: Teams already using Zaraz for page performance can add Perspection for conversion delivery quality, using Zaraz for event collection and Perspection for event processing and dispatch.

• Offline conversion upload: Teams uploading offline sales data (CSV, up to 10,000 records per batch) to ad platforms benefit from Perspection's offline conversion pipeline — a use case entirely outside Zaraz's edge-based architecture.

• BigQuery export: Teams needing event data in a data warehouse benefit from Perspection's BigQuery export — a use case outside Zaraz's edge-based architecture.

Sources and References

• Cloudflare Zaraz documentation: developers.cloudflare.com/zaraz

• Cloudflare Zaraz pricing: cloudflare.com/plans

• Core Web Vitals: web.dev/vitals

• Meta Conversions API: developers.facebook.com

• Google Enhanced Conversions: support.google.com

Related Articles

• Best Server-Side Tagging Platforms

• First-Party Domain Setup Guide

Feature comparisons verified through the Perspection product dashboard and published documentation, cross-referenced with Cloudflare Zaraz's publicly available documentation and product pages as of February 2026.

"Zaraz solves the collection problem — getting events out of the browser reliably. Perspection solves the delivery problem — getting events to ad platforms with maximum match quality. Teams running serious e-commerce ad spend benefit from solving both problems, and the two platforms work well as complementary layers." — Senior Ad Tech Consultant