COMPLI3D vs Stape
Stape hosts server-side Google Tag Manager. COMPLI3D is a consent gateway and a conversion relay with a fixed, minimal payload. Here is how they differ.
Facts about Stape are marked [VERIFY] until confirmed against Stape's current documentation. Last reviewed [DATE].
Short version
Stape hosts server-side tagging that you configure yourself. [VERIFY] COMPLI3D holds every script until opt-in and sends each ad network only a click ID and an opaque code, with no tags to write.
Feature by feature.
| Capability | COMPLI3D | Stape |
|---|---|---|
| Main job | Consent control and PHI-free ad conversions | Hosting for server-side Google Tag Manager [VERIFY] |
| Business associate agreement | Available [VERIFY PLAN SCOPE] | [VERIFY] |
| Holds scripts until opt-in | Yes, every script | Depends on your consent tool and tags [VERIFY] |
| Removes page URLs before data leaves | Yes | Depends on how each tag is set up [VERIFY] |
| Sends ad conversions server-side | Click ID and opaque code only | Server-side tags for many networks [VERIFY] |
| Tag management | Through the gateway | Server-side Google Tag Manager containers [VERIFY] |
| Visit and page reports | Coming soon | Not its main focus [VERIFY] |
| Where data is processed | [REGION] | Several hosting regions [VERIFY] |
| Price | [PRICE] | Published plans by request volume [VERIFY] |
What actually differs.
Who decides the payload
With server-side tagging, your team decides what each tag sends, field by field. [VERIFY] With COMPLI3D the payload is fixed: a click ID, an opaque code and a time.
Server-side is not the same as private
Moving a tag to a server changes where it runs, not what it sends. A server tag can still pass the page URL or form fields if it is set up to. COMPLI3D removes them before anything leaves.
Consent
Consent Gateway holds every script in the browser until opt-in. With server-side tagging, consent is handled by the tools you pair it with. [VERIFY]
When Stape may be the better fit.
You have a tagging specialist
If your team builds and maintains Google Tag Manager containers, server-side hosting gives you full control. [VERIFY]
You send data beyond ad networks
If server-side tags feed analytics, CRM or warehouse tools, a general tagging setup covers more ground.
Your pages say nothing about health
If no page, form or URL could reveal a visitor's care, a fixed minimal payload may be more than you need.
Run both safely, then switch.
- Run the free scan.See every script that loads before consent today, and where it sends data.
- List what your server tags send.Note which fields reach each ad network today.
- Map conversions to opaque codes.Each conversion gets a code that means nothing outside your account.
- Pause the matching server tags.Once the relay reports a conversion, turn off the duplicate tag so nothing is counted twice.
Is server-side tagging enough on its own?
It depends on what each tag sends. A server-side tag can still pass page URLs or form data unless it is set up not to. Review it with your counsel.
Can I keep Stape for other tags?
Yes. Keep server-side tags for tools that never receive health information, and send ad conversions through the relay.
Does Stape sign a business associate agreement?
We have not confirmed this. Ask Stape and your counsel. [VERIFY]
Who wrote this comparison?
The COMPLI3D team. We mark anything we have not confirmed about another product, and we update the page when it changes.
See what your tags send today.
A report of every script that loads before consent and where it sends data.