Addingwell vs Cloudflare Zaraz

Addingwell provides server-side tagging built on Google Tag Manager Server-Side, designed to recover advertising signals affected by ad blockers, browser restrictions, and cookie deprecation. Its monitoring tools track tag events, alert users to problems, and provide insights into sent-data quality and cookie integrity across browsers. Infrastructure includes multiple regions, CDN, JavaScript asset proxying, and reverse-proxy capabilities for managing data flows. Documentation describes server-side event delivery to Google Analytics 4, Google Ads, and Meta, plus a separate Microsoft UET Conversion API tag. Didomi-backed consent monitoring can display consent attached to each request in real time. Addingwell offers a free plan with 100,000 requests and one-region infrastructure. Pay as you go costs €90 a month and includes 2,000,000 requests and multi-region infrastructure. Unused requests do not roll over; additional requests are calculated at the end of the billing cycle and added to the invoice. Setup requires DNS records for a tagging subdomain, with propagation taking five minutes to one hour. The service is available through the web and API for websites and Google Tag Manager Server containers.

Cloudflare Zaraz lets website owners manage third-party tools and run them through Cloudflare’s edge, with the stated aim of improving site speed and security. Its supported categories include analytics, advertising, marketing automation, recruiting, embeds, and customer data platforms. For other tools, custom integrations include Custom HTML, Custom Image, and HTTP Request. A client-side Web API can send events and data used to create triggers and launch tools. Zaraz also provides a configurable consent modal that can load tools according to purposes users have agreed to; users remain responsible for assigning tools to purposes when needed for GDPR compliance. The free plan includes 1,000,000 Zaraz Events per Cloudflare account each month. Additional usage costs $5 a month for each additional 1,000,000 events, and all features and tools are available on all accounts. Without paid usage billing, Zaraz is disabled until the next billing cycle if monthly events exceed 1,000,000. It can serve its script on a domain not proxied through Cloudflare if a separate proxied domain or subdomain is set up for the script. Zaraz is available through web and API platforms.