PingadoPingado and Stape
Stape hosts server-side Google Tag Manager and adds tools around it, such as a custom loader, Cookie Keeper, a data store and request logs. It also runs Meta's Conversions API Gateway as a hosted service.
Checked against Stape's pricing page and help center, and a production Stape setup we traced, 29 September 2026.
Where they differ
- Hosting or setup. Stape takes the servers off your hands. The containers are still yours to build: a web container that sends events, a server container, and a tag, trigger and consent rule for each platform and each event. Pingado is one snippet, plus connecting your payment provider and ad accounts.
- Where conversions come from. On Stape, as on any server-side GTM, a purchase is what your thank-you page pushes to the dataLayer. Pingado takes trials and purchases from your payment provider, including the charge after a free trial, which happens when no page is open.
- Deduplication. Browser and server copies of an event are counted once when the web and server tags share an event ID. On Stape that pairing is part of the container you build. Pingado sends both copies with one ID it controls.
- Keeping ad cookies. Stape's Cookie Keeper restores ad cookies Safari deleted, keyed by a master cookie your server sets. Pingado does the same from its tracking domain: every response sets the visitor ID and ad cookies again, and carries them across your domains when a visitor moves between them. For both, Safari keeps the full lifetime when the tracking domain shares your site's IP address.
- Meta Conversions API Gateway. Stape's hosted Gateway copies the events your Meta pixel already sends to Meta's server API, for Meta alone, with no tagging. The events are whatever your pixel sends. Pingado covers Meta, Google, TikTok, Reddit and OpenAI, and takes trials and purchases from your payments.
- Reporting. Stape moves events, its plans do not include a report of ad spend against attributed revenue. Pingado shows spend and attributed revenue per campaign.
- Pricing. Stape's hosting is priced by requests, with a free plan up to 10,000 requests a month, and Cookie Keeper and the data store from its Pro plan. Pingado is free up to $500 of monthly ad spend, and then priced by ad spend.
When Stape is the better fit
- You run GTM with a specialist and want server-side tagging without managing Google Cloud.
- You want GA4 and many destinations server-side, including platforms Pingado does not connect.
- Your Meta pixel already sends the right events and you want Meta's server API for it within minutes.
When Pingado is the better fit
- You want conversions from your payments sent to every ad platform you use, without building 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: Stape for GA4 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
- Pricing, Stape
- Cookie Keeper power-up, Stape documentation
- Choosing the user identifier in Cookie Keeper, Stape help center
- Signals Gateway and Meta Conversions API Gateway, Stape help center
- Meta Conversions API Gateway cost, Stape help center