Cloudflare Zaraz vs PipelineOn for Contractors
Cloudflare Zaraz and PipelineOn open source offer two different architectures for server-side tracking. Zaraz runs configured third-party tools through Cloudflare’s edge service. PipelineOn’s open-source software is an application you operate for source capture, business outcomes, attribution reports and optional Meta delivery.
Both can be relevant to a contractor. Choose based on whether the immediate problem is routing website events through your Cloudflare stack or connecting an inquiry with later business outcomes in a dedicated application.
PipelineOn publishes this documentation-based comparison. Product and price information was reviewed on October 14, 2026. We have not run a comparative speed, recovery or ROAS benchmark.
On this page
- What does Zaraz do?
- Compare the operating model
- Pricing uses different units
- An electrician’s website example
- What does a migration need to preserve?
- How should you verify either option?
What does Zaraz do?
Cloudflare’s getting-started guide describes configuring tools and events through Zaraz. Its HTTP Events API also provides a server-origin event route. Check the supported tools and their current actions before designing a destination workflow.
Zaraz is not a host for your server GTM container. A move from server GTM to Zaraz therefore requires an event and destination mapping exercise, rather than simply changing the container’s hosting address.
The PipelineOn software has its own collector and outcome contract. Your backend, CRM automation or trusted relay supplies normalized records. It can report linked touch credit and optionally queue eligible Meta events. The open-source overview provides the public download and describes the planned hosted option.
Compare the operating model
| Requirement | Cloudflare Zaraz | PipelineOn open source |
|---|---|---|
| Runtime | Cloudflare edge service | Your single-process software deployment |
| Website event setup | Configure Zaraz tools, actions and triggers | Install the software collector and consent handoff |
| Server-origin events | HTTP Events API with your mapped source | Authenticated outcome API with your mapped source |
| Job and payment attribution | Supply the business model and reporting layer | Supported touch reports for linked outcomes |
| Meta verification | Inspect your configured route and destination | Inspect stored attempts/receipts and Meta Test Events |
Treat this table as an architecture comparison. It does not assert that every tool action or custom setup is interchangeable. Ask the operator to walk through one actual contractor workflow.
Pricing uses different units
Cloudflare’s Zaraz pricing documentation lists one million free Zaraz Events per account each month. Additional usage on the paid plan costs US$5 per additional million events. Without paid usage enabled, exceeding the free allocation disables Zaraz until the next cycle.
PipelineOn’s open-source software is free to self-host. The operator pays any infrastructure and maintenance costs. PipelineOn-hosted is planned at around $20/month; final pricing, included usage and availability are still being finalized.
A Zaraz Event is not necessarily the same billable unit as a request at a GTM host. Nor is either one a booked job. Estimate the events your design sends and compare all operating costs in the server-side tracking cost guide.
An electrician’s website example
An electrician already using Cloudflare wants to route website analytics and marketing events through the same platform. Zaraz belongs on that shortlist if its supported tools and event controls fit the required setup.
Now extend the example. A homeowner submits an inquiry, a dispatcher qualifies it and a technician completes paid work days later. The website event cannot supply those later facts. A backend or CRM connection must send them, preserve the original occurrence time and use appropriate identifiers.
The PipelineOn software is relevant when the operator wants to store those outcomes and inspect their source attribution in one focused application. Its session reference must travel through the inquiry and later records. A missing reference remains an attribution gap; installing a server does not reconstruct it.
What does a migration need to preserve?
Inventory each event, source system, destination, ID rule and owner. Distinguish browser actions from accepted source outcomes. A click on a quote button is not evidence that the server accepted the form.
Choose one server sender for each logical conversion. If a CRM integration already sends a booking to Meta, decide whether it remains the owner. Adding Zaraz or the software without reviewing existing senders can create overlapping events.
Coordinate browser and server copies with the same event name and ID where they describe one action. Use the Pixel versus CAPI guide and the first-party data strategy during that mapping.
How should you verify either option?
Test a consented tagged visit, a successful form and one later outcome. Verify the source handoff and actual business value. Then inspect the corresponding destination event rather than stopping at a configuration toggle.
Repeat the source event, introduce a temporary failure and check the operator’s recovery process. Keep queued, accepted, unmatched and excluded records distinguishable. Provider receipt, person matching and advertising attribution each need their own evidence.
Choose Zaraz when its edge-based tool configuration fits your stack. Evaluate the software when you want the standalone attribution and outcome application and have an operator for it. Compare both with server GTM hosts and the ten-option tracking shortlist.
View the open source and compare the self-hosted and PipelineOn-hosted options.
Written by
PipelineOn Research Team