Pingado and server-side GTM

Server-side Google Tag Manager is Google's tag server: a container you host that receives events from your site and forwards them to ad platforms through tags you configure. It is a toolkit. What reaches each platform depends on how the containers are built.

Checked against Google's documentation and a production server-side GTM setup we traced, 29 September 2026.

Where they differ

What you build. Server-side GTM needs a web container that sends events, a server container with a client to receive them, and a tag, trigger and consent rule for each platform and each event, plus the hosting and a domain for it. Pingado is one snippet, plus connecting your payment provider and ad accounts.
Where conversions come from. Server-side GTM forwards what your pages push to the dataLayer, so a purchase is what the thank-you page reports. Pingado takes trials and purchases from your payment provider, including the charge after a free trial, which happens when no page is open.
Deduplication. For a platform to count a browser event and its server copy once, every web tag and server tag has to share an event ID. A tag that fires twice with two IDs, or a server tag that sends a different ID from the pixel, gets counted twice. Pingado sends both copies with one ID it controls.
Google Ads. In the setup we traced, the server-side Google Ads tag sent a conversion when the visitor had arrived with a click ID, and customer data for Enhanced Conversions needed a separate user-provided data tag. Pingado uploads each conversion through the Google Ads API with the click ID, or with the hashed email when there is none.
Reporting. Server-side GTM moves events, it does not report. Pingado shows spend and attributed revenue per campaign, from the same data it sends to the platforms.
Hosting cost. Google estimates about $45 a month per server on Cloud Run and recommends at least two for production. Pingado is free up to $500 of monthly ad spend, and then priced by ad spend.
Flexibility. Server-side GTM can send any event to any destination, including GA4 and platforms Pingado does not connect, and can reshape the data on the way. Pingado sends leads, trials, purchases and booked calls to the ad platforms you connect.
Cookies in Safari. Served from your site's own origin, a server container can set first-party cookies that Safari keeps for their full lifetime. Pingado sets its cookies from a tracking domain you point at it; Safari keeps those for 7 days unless that domain shares your site's IP address.

When server-side GTM is the better fit

You have a GTM specialist and want full control over every event and destination, including GA4.
You need the longest cookie lifetimes in Safari and can serve the container from your site's own origin.

When Pingado is the better fit

You want conversions from your payments sent to the ad platforms without building and maintaining containers.
You want spend and attributed revenue per campaign in one report.
You want browser and server tracking without owning the deduplication.

They can run side by side: server-side GTM for analytics and custom events, Pingado for leads, trials and purchases. Send each conversion from one of them, not both, or the platform counts it twice.

Sources

Cloud Run setup guide, Google Tag Manager documentation
Custom domain for server-side tagging, Google Tag Manager documentation

All comparisons

Request access Back to the homepage