Overview
Introduction
Servero is a server-side tracking platform that forwards conversion and behavioral events from your site to ad and analytics destinations without relying on browser-side pixels. Ad blockers and iOS tracking prevention strip those pixels — server-side tracking survives both.
Pick an integration path based on your stack. Most teams are live in under 30 minutes.
Choose your integration method
Containers
Drop-in tag containers managed inside Servero — no GTM required.
Custom Loader
A first-party loader script for full control over event firing.
Server-side API
POST events directly from your backend over HTTPS.
Cookie Keeper
Persist first-party identifiers across navigations and sessions.
Step 1
Installation
Create a container from the dashboard, then paste the generated snippet into the <head> of every page you want to track.
<script async src="https://cdn.servero.io/c/YOUR_CONTAINER_ID.js"></script>Reload the page and confirm the loader appears in your network tab. The first event is usually visible in your container's live view within seconds.
Step 2
Domain Setup
Connect a subdomain you own (for example m.example.com) so requests originate from your own domain. This makes tracking first-party and resilient to cross-site cookie restrictions.
- 1Open Domains in your dashboard and add the subdomain.
- 2Add the CNAME record shown by Servero at your DNS provider.
- 3Wait for verification — TLS is provisioned automatically via Let's Encrypt.
Want Cloudflare WAF and DDoS protection on top? See the Cloudflare setup guide.
Step 3
Platform Config
Connect the destinations you want events forwarded to. Each destination has its own credential format; Servero validates the configuration before you can publish a container.
| Destination | Credentials needed |
|---|---|
| Meta Conversions API | Pixel ID + Access Token |
| Google Analytics 4 | Measurement ID + API Secret |
| TikTok Events API | Pixel Code + Token |
| LinkedIn CAPI | Partner ID + Token |
See all integrations for the full list of supported destinations.
Integration
Containers
A container is the unit of configuration in Servero. It bundles the loader, your event mapping, and the destinations to forward to. You can run separate containers per environment (staging vs production) or per brand.
Each container gets its own container ID, snippet URL, and credential set. Changes to one container do not affect others.
Billing
Plans, coupons & pricing
The live catalog and checkout live in the dashboard. You can apply optional coupon codes at container creation, upgrade, or renewal. The public pricing page calculator loads the same request tiers as the product when the API is reachable.
Integration
Custom Loader
For teams that need finer control over when and how events fire, Servero exposes a programmatic loader. Push events from anywhere in your application — after consent is granted, on a button click, or from a custom hook.
window.servero = window.servero || [];
window.servero.push({
event: "purchase",
value: 49.0,
currency: "USD",
order_id: "1024",
});The queue is flushed as soon as the loader initialises. Events pushed before the script loads are buffered and replayed automatically.
Integration
Server-side API
Forward events directly from your backend — useful for purchases confirmed after the user has left the page: delayed payments, async fulfillment, refunds, or subscription renewals.
curl -X POST https://api.servero.io/v1/events \
-H "Authorization: Bearer $SERVERO_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"container_id": "ctn_abc123",
"event": "purchase",
"value": 49.0,
"currency": "USD",
"user": { "email_hash": "sha256_of_email_here" }
}'The email_hash field is hashed on your server before sending. Servero never receives raw PII.
Downloads
Templates & Snippets
Pre-built snippets for the most common stacks are available inside the container detail view in your dashboard. Open any container and copy the version pre-filled with your credentials.
Tools
Debugging
Every container has a live event stream. Open it while you trigger events on your site to confirm the payload, the destination response, and identifier resolution in real time.
Failed deliveries are retried with exponential backoff for up to 24 hours. Persistent failures surface as a notification on your dashboard so nothing goes silently missing.
Help
Contact Support
Stuck on an integration? Real engineers answer support tickets — not bots. Average reply under 47 minutes on business days, often from the person who wrote the feature.