Direct answer: test Keitaro first when your team deliberately wants a self-hosted tracker, can own the server, and values a licence model whose editions are separated mainly by domains, users and administrative capabilities. Test RedTrack first when managed infrastructure, ad-platform Conversion API integrations, spend sync and an event-based SaaS plan fit the buying workflow better. Neither is universally better: the decision changes who owns infrastructure and how cost grows.
This is an operational comparison, not a feature-score contest. Use one real campaign, one month of traffic and a pass/fail conversion test before moving material spend.
Commercial facts checked 20 August 2026. Prices, limits and included capabilities change. Recheck the linked first-party pages before purchase.
Keitaro vs RedTrack at a glance
| Decision | Keitaro | RedTrack |
|---|---|---|
| Hosting | Self-hosted tracker installed on customer-managed infrastructure | Vendor-managed cloud platform |
| Published entry model | Individual yearly plans currently display Starter €40/month, Advanced €72 and Expert €104 | Plans are metered by tracking events, users, ad accounts and domains; billing toggle and add-ons change displayed cost |
| Infrastructure owner | Customer owns sizing, monitoring, backups, security and recovery | Vendor owns tracker infrastructure; customer still owns campaign configuration and data QA |
| Routing | Flows, filters, rotations, Click API, landing and offer logic | Smart Distribution, rules and managed source integrations |
| Source feedback | S2S postbacks plus plan-dependent integrations and custom work | Conversion API support for Meta, TikTok, Google and other published platforms |
| Team scale | Editions define domains, users and Admin API entitlement | Plans define users, event allowance, domains, ad accounts, API and retention |
| Best first fit | Team that already operates production servers and wants self-hosted control | Team that wants managed infrastructure and source-signal workflows |
Sources: Keitaro pricing, Keitaro editions, RedTrack pricing.
The largest difference is infrastructure ownership
Keitaro runs on a server you provide. The licence is therefore only one component of total cost:
Keitaro total operating cost
= licence + VPS/storage + monitoring + backups + patching + incident timeThat can be an advantage when the team already has a reliable server standard, recovery drills and an owner on call. It can be a liability when “self-hosted” means an unmanaged VPS known to one buyer.
RedTrack sells a managed platform. Its pricing is shaped by monthly tracking events, seats, domains, ad accounts, retention and optional capabilities such as faster spend synchronization or expanded management tooling.
RedTrack total operating cost
= plan + overage/add-ons + domains + integration QA + the surrounding stackManaged cloud removes tracker-server work, not operational responsibility. The team still owns macros, domains, postbacks, status mapping, access and reconciliation.
Read self-hosted vs cloud tracking before treating hosting as a simple feature row.
Pricing: compare the same 30-day workload
Keitaro’s live pricing currently shows yearly individual plans at €40, €72 and €104 per month. Its edition documentation distinguishes domain and user limits and identifies capabilities such as Admin API access. The required VPS is separate. Keitaro pricing and edition matrix
RedTrack’s live pricing page presents plans through a billing selector and lists plan-specific event, user, custom-domain, ad-account, retention and API allowances. It also publishes add-ons whose cost or cadence can depend on the plan or ad spend. RedTrack pricing
Build two models:
- normal month: actual visits, clicks, conversions, impressions and secondary events;
- launch month: expected peak plus 30% headroom;
- users, domains and ad accounts needed on day one;
- 12–24 month reporting retention;
- server labour for Keitaro versus event overage and add-ons for RedTrack.
Do not compare a licence card with a SaaS card until the server and event ledger are included.
Routing and visitor continuity
Keitaro documents campaigns with flows, filters, paths, landing pages, offers and Click API. RedTrack documents campaign routing, rules and Smart Distribution. Both can route serious performance traffic; the question is whether they reproduce your hardest rules.
Test three cases:
- GEO and device routing with a documented fallback.
- Weighted lander/offer rotation with the required visitor consistency.
- Missing macro, capped offer or unavailable destination.
For every click, store the source URL, resolved tokens, tracker click ID, chosen path and final URL. A destination returning HTTP 200 does not prove the intended rule fired.
For PWA traffic, also test install/open continuity and Direct Link parameter preservation. Click ID vs Sub ID explains which identifier should survive the handoff.
Postbacks, CAPI and source feedback
Keitaro’s normal postback flow requires subid and status and supports optional payout, currency and transaction fields. Keitaro postback documentation
RedTrack publishes Conversion API support and source integrations alongside ordinary conversion tracking. This can reduce custom work for a supported ad platform, but “CAPI included” is not the final test. Confirm the exact source, event name, identifier, value, currency, deduplication field and delivery diagnostics.
The required loop is:
ad click → tracker ID → route → conversion callback
→ duplicate/status handling → source feedback → reporting and financeUse postback troubleshooting to test missing IDs, duplicate callbacks and status changes.
Users, domains, API and retention
Keitaro editions make domains, users and administrative capabilities part of the licence choice. RedTrack plans package seats, domains, ad accounts, API access and retention differently. A solo buyer can waste money on unused team controls; a multi-buyer operation can create real risk by underbuying access boundaries.
Before signing, create a role matrix for buyer, team lead, analyst and client/read-only access. Confirm which campaigns, revenue fields and settings each role can see or change. Then prove export and restore procedures instead of assuming either product is the permanent system of record.
Where DarkCore fits
DarkCore is not an automatic replacement for Keitaro or RedTrack. If the requirement is a particular tracker routing model or vendor integration, evaluate the specialist products directly.
DarkCore becomes relevant when the expensive problem continues after attribution: Streams own traffic routing, PWA Tracker connects PWA and Direct Link delivery, conversion statuses define the lifecycle, and Finance keeps campaign economics near operations. A specialist tracker can remain part of that architecture.
Migration pass/fail table
| Test | Expected result | Pass? |
|---|---|---|
| Macro map | Every source token reaches the intended field. | ☐ |
| Route and fallback | Every rule resolves to its documented destination. | ☐ |
| First conversion | Correct click ID, status and value appear once. | ☐ |
| Duplicate callback | Revenue and counts are not duplicated. | ☐ |
| Status change | Pending, approved and rejected history remains correct. | ☐ |
| Source feedback | Correct event, value and dedupe key reach the platform. | ☐ |
| Cost | Source, tracker and finance reconcile within the declared delay. | ☐ |
| Access | Each role sees only assigned data. | ☐ |
| Recovery | Export, backup and rollback owners are documented. | ☐ |
FAQ
Is Keitaro cheaper than RedTrack?
Not automatically. Keitaro separates the licence from the server and operating labour. RedTrack meters a managed service by plan and events, with possible overages or add-ons. Compare the same 12-month workload.
Which is better for Meta or TikTok traffic?
RedTrack publishes native Conversion API support for major ad platforms. Keitaro can track and return conversions through postbacks and integrations. Test the exact event and source configuration rather than choosing from the label alone.
Can I keep Keitaro or RedTrack with DarkCore?
Yes. Keep the tracker where it adds value and use DarkCore only where routing, PWA delivery, status ownership and finance need a connected workflow.