Ad blockers eat 30%
of your conversion data.
SerpWise fires conversion events server-side to 8 ad platforms — no client JavaScript, no GTM Server to manage, no GCP bill. First-party cookies survive Safari ITP. Consent management is built in. Setup takes minutes, not days.
8 platforms. One pipeline.
Add credentials, create a rule, events start firing. No GTM tags, no GCP projects, no JavaScript.
Conversions API
Events API
Enhanced Conversions
Measurement Protocol
Conversions API
Conversions API
Conversions API
Custom HTTP
Six stages. Fully automated.
Every conversion event passes through consent, transformation, deduplication, encryption, and quality scoring before reaching an ad platform.
Event Fires
A visitor triggers a conversion rule — purchase, lead, add to cart. The gateway extracts event data from the HTML response.
Consent Check
If consent management is enabled, the gateway reads OneTrust, Cookiebot, or custom consent cookies. Events without consent are logged but not forwarded.
Transform & Enrich
Transformation rules rename events, set fields, or route to specific platforms. Auto-enrichment fills missing data from page JSON-LD.
Deduplicate
Three-layer dedup: in-memory (instant), database (cross-instance), platform-side (event ID). No duplicate conversions reach your ad accounts.
Encrypt & Send
Credentials decrypted on-demand (AES-256-GCM). PII auto-hashed (SHA-256). Events batched per-platform and sent with rate limiting.
Log & Score
Every event is logged with delivery status, platform response, and match quality score. View in the Event Log or Live Debugger.
Everything you need. Nothing to manage.
First-party cookies, script proxy, consent management, live debugging, quality scoring, and event transformation — all built into the proxy layer.
400 days
Cookie expiry (vs 7-day ITP)
First-Party Cookies
Server-set cookies with 400-day expiry bypass Safari ITP's 7-day cap. Meta _fbp, TikTok _ttp, Google _gcl_aw, Snapchat _scid — all set as HttpOnly, Secure, SameSite=Lax.
15-30%
Analytics data recovered
Script Proxy
GTM and GA4 scripts served from your domain. Ad blockers can't distinguish them from first-party code. Recover 15-30% of lost analytics data.
6 signals
Quality dimensions tracked
Event Quality Scoring
Track match quality per integration — email coverage, phone coverage, cookie presence, IP/UA signals. Get actionable suggestions to improve ROAS.
< 100ms
Event stream latency
Live Event Debugger
Watch events flow in real-time during setup. See status, user data field coverage, custom data, and errors — without waiting for the Event Log.
3 CMPs
Supported out of the box
Consent Management
GDPR-ready. Events only fire when the user has granted consent. Supports OneTrust, Cookiebot, and custom consent cookies out of the box.
4 actions
Rename, drop, set, route
Event Transformation
Rename events, drop unwanted conversions, set default fields, or route events to specific platforms. No code changes — configure from the dashboard.
SerpWise vs Stape.io
Both fire server-side events. SerpWise does it at the proxy layer with zero infrastructure to manage.
| Feature | SerpWise | Stape.io |
|---|---|---|
| Supported platforms | 8 (Meta, TikTok, Google Ads, GA4, Snapchat, Pinterest, Twitter/X, Webhook) | 15+ via GTM Server |
| Setup complexity | Add credentials, create rule, done | GCP project, GTM Server container, custom tags |
| Infrastructure | Managed — runs at the proxy layer | Self-hosted GCP App Engine or Cloud Run |
| First-party cookies | Server-set, 400-day, automatic | Requires GTM cookie tag configuration |
| Script proxy | Built-in GTM/GA4 proxy | Built-in via server GTM |
| Consent management | Built-in (OneTrust, Cookiebot, custom) | Via GTM consent mode tags |
| Live event debugger | Built-in SSE stream | GTM Server preview mode |
| Event quality scoring | Built-in with suggestions | Not available |
| Auto-enrichment | From page JSON-LD/Open Graph | Not available |
| Event transformation | Built-in rule builder | Custom GTM Server tags |
| Credential encryption | AES-256-GCM at rest | GCP Secret Manager |
| Pricing | Included in SerpWise plan | $20-100+/mo for GCP + Stape |
Three-layer deduplication.
Zero duplicate conversions.
In-memory dedup catches duplicates instantly. A database unique constraint prevents cross-instance duplicates. Platform event IDs provide the final safety net. Your ad accounts only see real conversions — never inflated numbers.
Bank-grade credential security.
Every ad platform token is encrypted at rest with AES-256-GCM. PII (email, phone, name) is automatically SHA-256 hashed before it leaves the gateway. Raw values are never logged or stored.
See all security featuresAES-256-GCM encrypted at restSHA-256 hashed before sendHttpOnly, Secure, SameSite=LaxTLS 1.2+ to all platformsDecision support
Server-Side Tracking — Questions & Answers
How is this different from Stape.io?
Stape runs a GTM Server container on Google Cloud — you manage infrastructure, write custom tags, and pay for GCP compute. SerpWise runs at the proxy layer with zero infrastructure to manage. Add credentials, create a rule, and events start firing. You also get features Stape doesn't offer: event quality scoring, auto-enrichment from JSON-LD, and a built-in consent manager.
Do I still need Google Tag Manager?
No. SerpWise fires conversion events server-side based on rules you define in the dashboard — no GTM, no client-side tags, no JavaScript. However, you can use SerpWise's Script Proxy alongside GTM for a hybrid approach: GTM handles client-side tag management while SerpWise handles server-side event delivery.
How does the 400-day cookie work?
When SerpWise sets a tracking cookie (Meta _fbp, TikTok _ttp, Google _gcl_aw), it's set as a server-side Set-Cookie header with a 400-day Max-Age. Safari ITP only caps client-side cookies (set via JavaScript) to 7 days. Server-set cookies are exempt from this restriction, so your attribution windows stay intact.
What about GDPR compliance?
SerpWise has built-in consent management. Enable it per integration and specify which consent categories are required (Analytics, Marketing, Personalization). The gateway reads consent signals from OneTrust, Cookiebot, or a custom _sw_consent cookie. Events without consent are logged but never forwarded to ad platforms.
How does deduplication work?
Three layers: (1) In-memory dedup in the gateway catches duplicates instantly. (2) A database unique constraint prevents duplicates across gateway instances. (3) Each event includes a unique eventId that platforms use for their own dedup. No duplicate conversions reach your ad accounts.
Can I send events from my backend?
Yes. The Tracking Ingest API (POST /tracking/ingest) accepts events from any HTTP client — CRM webhooks, order processing systems, payment processors. Events go through the same pipeline: PII hashing, consent checks, dedup, and multi-platform forwarding.
What happens if an ad platform is down?
Events are retried with exponential backoff — up to 5 retries over 15 minutes. Per-platform rate limiting prevents hitting API quotas. Failed events are logged with full error details for debugging. The Live Debugger shows failures in real-time.
Ready to dominate the Agentic Web?
Join the forward-thinking teams using Serpwise to optimize, track, and secure their presence across AI agents and traditional search. Start your free trial today.