Migrate from Stape or Cometly to server-track-lab
By Marc Stevens · Comparison as of Oct 2026 · Prices checked Oct 13, 2026 on each vendor's official pricing page
This page is for small B2B SaaS growth teams that send conversions (signups, demos, qualified leads, closed-won deals) to ad platforms from their server. Stape and Cometly are both good products. They solve different problems from server-track-lab, so here is an honest side-by-side to help you decide whether switching makes sense.
Stape and Cometly are trademarks of their respective owners. server-track-lab is an independent product by Marc Stevens and is not affiliated with or endorsed by either company. Details below come from their public pages; check them yourself before deciding.
Comparison (as of Oct 2026)
| Stape | Cometly | server-track-lab | |
|---|---|---|---|
| What it is | Hosting and tooling for server-side Google Tag Manager, plus a hosted Meta Conversions API Gateway | Marketing attribution platform built for B2B SaaS, with its own pixel and server-side tracking | One API endpoint that forwards server-side conversion events to ad platforms |
| Pricing model | sGTM: by requests per month (Pro US$20/mo for 500K, Business US$100/mo for 5M, Enterprise US$200/mo for 20M; about 20% off annually). Meta CAPI Gateway: US$10/mo per Pixel (up to 10M events/mo per Pixel) | By monthly pageviews. No prices published: quote on request (sales call). Monthly or annual billing | Per conversion event: CA$2 per 1,000 events after the free tier. Self-serve |
| Free tier / trial | sGTM Free plan: 10K requests/mo, no credit card. Meta CAPI Gateway: 7-day free trial | No free plan; Cometly states it doesn't run a free trial | 1,000 events/mo free |
| Setup | Set up and maintain a server-side GTM container (tags, clients, triggers); the CAPI Gateway connects a Pixel without GTM | Sales call, then onboarding; install the Comet Pixel and connect CRM and ad accounts | Get a key, send one API call per conversion from your backend |
| B2B lifecycle events | CRM apps (HubSpot, Pipedrive, Zoho, HighLevel, Salesforce as a paid app) send lead status and offline conversions | Full funnel from first touch to closed-won, with account journeys | Built-in names: signup, trial_started, demo_booked, qualified, opportunity, closed_won, and more, mapped to Meta events |
| Dedup | Configured by you in your tags (Meta dedups on event_id + event_name) | Handled inside the platform | Dedups repeated event_id for 72h per workspace (not forwarded or billed twice); pass the same event_id to your pixel for Meta's dedup |
| Meta | Yes (sGTM tag or CAPI Gateway) | Yes, plus Google, LinkedIn, TikTok, Microsoft, Reddit and Snapchat | Live: Meta Conversions API |
| Yes, via sGTM tags and a Google Ads offline conversions connection | Yes | Coming soon: Google Enhanced Conversions (payload preview only today) | |
| Attribution dashboards | Request analytics and logs, not attribution | Yes: multi-touch attribution and customizable dashboards | No. Delivery log only (did the event arrive, what was sent) |
Where the others win. At very high volume, Stape is cheaper: US$10 a month covers up to 10 million Meta events per Pixel. If you want attribution reporting, Cometly offers dashboards and multi-touch models that server-track-lab does not. Cometly also connects to many more ad platforms today.
Where server-track-lab fits. You have plenty of traffic but only a few hundred or thousand real conversions a month, you have a developer who can make one HTTP call, and you don't want to run a tag manager or book a sales call. You pay per conversion, not per pageview or request.
Sources: Stape sGTM pricing, Stape Meta CAPI Gateway pricing, Cometly pricing (all checked Oct 13, 2026). Stape prices are in USD as published. Third-party reports of Cometly prices exist but aren't confirmed by Cometly, so we don't repeat them here. Meta dedup rules: Meta deduplication docs.
Migrate in five steps
1. Get a free key
Sign up and copy your API key. It's shown once. Then connect your Meta Pixel (Dataset) ID and Conversions API access token in the dashboard.
2. Map your existing events
List what your current setup sends today and pick the matching server-track-lab name. We map each name to a Meta event for you.
| What you track now | server-track-lab event_name | Sent to Meta as |
|---|---|---|
| Account created / sign-up / CompleteRegistration | signup | CompleteRegistration |
| Form fill / Lead | lead | Lead |
| Trial started / StartTrial | trial_started | StartTrial |
| Demo booked / Schedule | demo_booked | Schedule |
| Contact request | contact | Contact |
| MQL/SQL, lead status changed to qualified | qualified | Lead (event_stage: qualified) |
| Opportunity created | opportunity | qualified_opportunity (custom) |
| Subscription started | subscribed | Subscribe |
| Deal closed-won / Purchase (value required) | closed_won | Purchase |
Other names pass through to Meta unchanged, as custom events.
3. Send server events with the same event_id as the browser pixel
Generate one ID when the conversion happens. Pass it to the pixel as eventID and send the same value as event_id from your server:
// Browser (Meta Pixel), on the confirmation page
fbq('track', 'Schedule', {}, { eventID: 'demo_8f3a2c71' });
# Server
curl -X POST https://server-track-lab.pages.dev/api/v1/track \
-H "Authorization: Bearer $SERVER_TRACK_LAB_KEY" \
-H "Content-Type: application/json" \
-d '{
"event_name": "demo_booked",
"event_id": "demo_8f3a2c71",
"timestamp": "2026-10-13T15:04:05Z",
"user": {
"email": "jane@acme.example",
"ip": "203.0.113.7",
"user_agent": "Mozilla/5.0"
},
"event_source_url": "https://acme.example/book-a-demo"
}'
The email is normalized and hashed with SHA-256 before it leaves our API. Send the same request twice and the second returns "status": "deduplicated".
4. Verify in the playground and in Meta Test Events
Paste the event into the playground to see the exact hashed payload Meta would receive. Nothing is stored. Then add a Test Events code in the dashboard and confirm the event shows up in Meta Events Manager under Test Events.
5. Run both side by side, then retire the old path
Keep your Stape container or Cometly setup running for a week or two while server-track-lab sends the same conversions with the same event IDs. Compare counts in Events Manager and check that deduplicated events aren't counted twice. When the numbers line up, turn off the old server-side tags. Keep the browser pixel: pixel plus server, with dedup, gives the best coverage.
FAQ
Is server-track-lab cheaper than Stape?
Not at very high volume. Stape's sGTM Pro plan is US$20/month for 500K requests and its Meta CAPI Gateway is US$10/month per Pixel, so heavy-traffic sites will usually pay less with Stape. server-track-lab is aimed at small B2B teams sending a few hundred to a few thousand conversion events a month: the first 1,000 events each month are free, then CA$2 per 1,000 events.
Does server-track-lab replace Cometly's attribution dashboards?
No. Cometly offers multi-touch attribution, customizable dashboards and account journeys. server-track-lab does not. It is a focused pipe that sends server-side conversion events to ad platforms.
Does server-track-lab support Google Enhanced Conversions?
Not yet. Meta Conversions API forwarding is live. Google Enhanced Conversions is coming soon; today the API builds the Google payload and shows it as a preview without sending it.
Will I double count conversions while running both systems?
Not if you use one event_id per conversion. Meta deduplicates browser and server events that share the same event_name and event ID, and server-track-lab deduplicates repeated event_id values per workspace for 72 hours. If your old server-side path also sends to Meta with the same event_id, Meta should keep one, but check Events Manager during the overlap.
Do I need Google Tag Manager or a sales call?
No. You sign up for a free API key and send one HTTPS POST per conversion from your backend.