RedTrack vs Binom: cloud tracking, self-hosting, and cost

Choose RedTrack when you want managed tracking with published ad-spend sync and provider-specific conversion feedback. Choose self-hosted Binom v2 when controlling the tracker server matters and someone owns its operation. Compare Binom Cloud if you want Binom without supplying that server. RedTrack meters events; Binom advertises licensing independent of click volume. Neither the license price nor an “unlimited” label establishes total operating cost or capacity.

This is a Tracked-authored comparison of two competitors, not an independent ranking. We selected infrastructure responsibility, billing units, routing, conversion delivery, domains, permissions, and migration as buying criteria. We read first-party sources on October 28, 2026. We did not purchase plans, operate competitor campaigns, or measure speed, accuracy, match rates, or uptime. Vendor performance claims are not our test results.

RedTrack vs Binom at a glance

Sources checked October 28, 2026. RedTrack figures below are its affiliate and lead-generation plans, not its separate ecommerce products. Binom documentation is for v2 unless noted.

Buying criterion	RedTrack	Binom v2 self-hosted / Binom Cloud
Infrastructure responsibility	Managed tracker service; you still configure campaigns, domains, and integrations	Self-hosted: supply a suitable server. Cloud: server, monitoring, and optimization included (pricing FAQ)
Entry price	Solo: $169 monthly, 5M events, 1 user (pricing)	Self-hosted: $149 monthly license plus infrastructure. Cloud card: $299, with billing cadence requiring confirmation (pricing)
Larger team packaging	Team: $399 monthly, 20M events, 5 users. Enterprise: $999 monthly, 75M events, 15 users (pricing)	Pricing advertises unlimited users and domains for v2 and Cloud; extra installations can require additional licenses (pricing)
Volume boundary	Clicks, conversions, and processed postbacks count toward the event allowance; overages apply (pricing)	No per-click license charge advertised. Self-hosted card says up to 260M/day; Cloud says up to 2M/day. These are vendor statements, not measured capacity (pricing)
Domains and retention	Solo: 10 SSL domains / 12 months; Team: 50 / 24 months; Enterprise: 100 / 36 months (pricing)	Unlimited domains and lifetime retention advertised; self-hosted storage still needs funding and management (pricing)
Routing mechanism	Funnel smart distribution adjusts path weights from conversion history; Solo entitlement conflicts across pricing and help (help)	Normal Rotation uses weights. Smart Rotation considers a visitor's prior paths, pages, offers, and conversions (campaigns, rotation)
Outbound conversion feedback	Pricing publishes native CAPI for named platforms and separate S2S/JSON forwarding routes (pricing)	Campaign S2S forwarding documented; Facebook CAPI added as Beta in v2.36.00 (campaigns, changelog)
Landing-page ownership	Reviewed setup registers your page URL and requires page-code changes; built-in file hosting was not established (setup)	Integrated landers accept an index file or ZIP; Files supports code editing and download (landers, Files)

“Not established” means the reviewed documentation did not prove that workflow, not that the vendor cannot support it. Confirm account-specific terms before purchasing.

Who runs the tracker when something breaks?

The useful distinction is not simply “RedTrack is cloud; Binom is self-hosted.” Binom offers both self-hosted and Cloud deployment. Separate the software you want from the server responsibility you can accept.

With RedTrack, buying the managed service removes the need to provision a tracker VPS. It does not remove your responsibility for DNS, permitted data collection, network callback mappings, account credentials, or the pages you operate.

With self-hosted Binom v2, name an owner for hosting, capacity, backups, recovery, credentials, and update coordination. Binom offers installation assistance and one-click tracker updates on its pricing page. Those reduce setup work; they do not make a customer-supplied server disappear.

The v2 installation guide requires a clean dedicated/VPS server, Ubuntu 24.04 or 26.04, 4 GB RAM, two CPU cores/threads, at least 50 GB free disk, and KVM virtualization. These are minimum requirements, not a promise about a particular traffic load. The older installation guide lists different specifications; do not use it to size a new v2 deployment.

Binom Cloud includes the server, monitoring, and optimization according to its pricing FAQ. Ask who handles backups, restore requests, region selection, burst capacity, and incidents. We did not establish a contractual recovery or response SLA from that page. Cloud shifts operating work to the vendor; it does not establish identical service terms to RedTrack.

How do RedTrack and Binom costs compare?

Keep monthly prices separate from annual offers

RedTrack's affiliate monthly plans list Solo $169, Team $399, and Enterprise $999. Its annual Black Friday offer displays monthly equivalents of $118, $279, and $699, alongside yearly invoices of $1,420, $3,352, and $8,392. The monthly equivalents are rounded. Those annual invoices are not monthly commitments.

Binom's pricing-page markup explicitly separates $149 monthly from $104 under yearly pricing for self-hosted v2. Do not treat $104 as a monthly-billed license. The Cloud card displays $299 without the same separate monthly/yearly price labels, so we do not present it as a verified monthly total. Confirm cadence, renewal, and included service with Binom.

The same Binom page contains conflicting trial terms: the v2 card says 30 days, Cloud says seven days, and its generic FAQ says 14 days with possible extension. Ask for the trial applicable to your deployment rather than assuming one duration covers all products. RedTrack advertises a 14-day trial.

Price the funnel, not just incoming visitors

RedTrack defines tracked events as clicks, conversions, and postbacks processed per month. Published overages are $0.04 per 1,000 events on Solo, $0.035 on Team, and $0.025 on Enterprise. Ask how your actual funnel, repeat callbacks, and custom event handling map to this definition.

For illustration, if RedTrack confirms a workload produces 6M billable events, Solo's listed arithmetic is $169 plus $40 for 1M excess events: $209 before taxes and add-ons. That is a conditional calculation, not an observed invoice. It says nothing about whether Solo meets your seats or automation needs.

Binom's licensing FAQ says click volume does not change its licensing fee. That is different from an event allowance. A fixed license can coexist with growing server, storage, and operator costs. Cloud's advertised daily traffic figure also needs clarification for bursts; it is not an interchangeable monthly event budget.

Use these cost models:

• RedTrack: required affiliate plan + event overages + relevant seats, domains, or sync-frequency add-ons + external page hosting/editor costs where needed.
• Binom self-hosted: software licenses + server + storage/backups + operating work + optional services you actually use.
• Binom Cloud: confirmed subscription cadence and service scope + any extra licenses or capacity costs + optional services.

Binom lists an additional self-hosted license at $75 on monthly pricing, versus $52 under yearly pricing; Cloud lists an additional license at $149. Those are not charges per human user. Binom Protect is a separate product, not a mandatory component of every campaign.

No hosting quote or operator labor rate was verified here, so there is no honest universal break-even traffic number. A team with existing infrastructure and an operator has a different cost model from a solo buyer hiring server help.

Do not substitute RedTrack's ecommerce prices

RedTrack separately prices ecommerce and DTC products by tracked-revenue tiers. Relay, Brand, and Agency are not lower-priced equivalents of affiliate Solo. If you run a store, compare order sync, refunds, revenue tiers, and attribution requirements separately. This article addresses affiliate traffic, offer handoffs, and network callbacks.

Do RedTrack and Binom route traffic the same way?

No. Similar feature names conceal different decisions.

RedTrack's smart-distribution help describes reallocating traffic among funnel paths using accumulated conversion history. It exposes historical sample requirements, recalculation intervals, a goal, thresholds, and a share reserved for learning traffic. This is distinct from pausing an ad or changing its budget.

The plan entitlement is unresolved: that help article says smart distribution starts at Team, while current pricing-page comparison copy says Solo includes Smart Distribution. Get written plan-specific confirmation if that feature determines your purchase. RedTrack separately lists spend sync every 60 minutes on Solo and 30 minutes on Team, Stop Rules on all affiliate plans, and Scale Rules in Enterprise.

Binom's campaign guide defines Normal Rotation as random distribution according to path, landing-page, and offer weights. Its Smart Rotation guide describes showing a returning visitor combinations they have not seen, while considering offers where that visitor already converted. Fix On and Top to Bottom provide additional repeat-visit behavior.

That is not the same documented mechanism as RedTrack's conversion-history-based path allocation. Do not infer automatic profit-based winner selection from the word “Smart.” Equally, do not infer Binom lacks other automation merely because this rotation guide describes a different job.

For a vendor walkthrough, request the same scenario: two pages, one offer, owner-set weights, a repeat visit, and a completed conversion. Ask what changes the next route, where that change is visible, and how to undo it. Equal weights do not guarantee equal totals in every sample.

Can both send conversion feedback to ad platforms?

Both document outbound conversion paths, but the reviewed evidence does not establish equal provider coverage or release status. Separate three steps: saving the tracker click ID, receiving the affiliate conversion, and sending an eligible event onward.

RedTrack's conversion setup describes network templates and manual mapping of click and payout macros. Its pricing page names native CAPI for Meta, Google, TikTok, Snapchat, Microsoft/Bing, X, Pinterest, and OpenAI Ads. It separately describes S2S postbacks or JSON forwarding for networks without native CAPI, including Taboola, Outbrain, Revcontent, and NewsBreak. These are vendor-published connection categories, not independently tested parity across providers.

Binom's postback guide passes {clickid} to the network and receives that saved ID through cnv_id, with payout and optional statuses. Its campaign settings document outbound S2S postbacks and a configurable Postback percentage. That percentage matters: a campaign need not forward every recorded conversion.

Binom's changelog explicitly added Facebook CAPI Beta in v2.36.00 on October 6, 2026. The latest listed release when checked was v2.36.02, October 22, 2026. We found no basis in those release notes to relabel the Facebook path as generally available or universal CAPI. Nor does a beta label prove the workflow is unusable; ask about eligibility and supported production use.

For either vendor, obtain provider-specific answers on event names, identifiers, consent, revenue/currency, deduplication, delivery errors, retries, and late events. A conversion visible in the tracker is not proof that Meta or Google accepted it. A delivery receipt is not proof of attribution or improved ad performance. The integration, postback, and conversion API guide explains these distinctions.

What changes for domains, colleagues, and page files?

RedTrack Solo includes one user and ten SSL domains, with extra seats unavailable on Solo. Team includes five users and fifty domains, with additional seats listed at $29 monthly. A second operator can change your plan even if the event count stays low.

Binom advertises unlimited users and domains. Its v2 permissions guide distinguishes superadmin, admin, and user, with read or read/write access to individual elements and separate Files, Facebook integration, and Conversion Log access. An unlimited user count does not by itself prove a client's required isolation or approval process. Map real responsibilities before buying.

Landing-page ownership also changes the budget. RedTrack's setup guide asks you to register a page URL, add scripts, and replace CTA links. Keep page hosting and publishing responsibility in your plan; a lander record is not proof of uploaded-file hosting.

Binom documents integrated landers uploaded as an index file or ZIP. The archive must contain one root index.html or index.php, with a documented 20 MB limit. Its Files page supports editing code and downloading files. This does not establish a visual page-builder equivalent, but it does mean Binom is not limited to redirecting visitors to externally hosted pages.

How should you plan a RedTrack–Binom migration?

Treat a switch as a campaign rebuild unless the destination confirms an importer for your exact source, version, and objects. Binom's current changelog mentions Keitaro import improvements; that is not evidence of a RedTrack importer. No complete RedTrack–Binom history migration was established in the reviewed sources.

Preserve these separately:

1. Configuration: campaign URLs, domains, traffic-source parameters, page files, offer URLs, weights, rules, and team permissions.
2. Conversion meaning: saved click field, primary sale, approved/rejected statuses, refunds, upsells, payout currency, and duplicate handling. Binom's postback guide distinguishes replacing payout from summing it with Upsell enabled; do not assume the destination behaves identically.
3. Outbound feedback: provider credentials, event mapping, filters, and browser/server deduplication. Decide which system owns delivery during overlap so one sale is not forwarded twice.
4. Historical evidence: exports and continued access to reports needed for financial reconciliation. Downloaded reports are not a compatible click-ID database.

Keep the old callback endpoint reachable for conversions tied to old click IDs. Point new traffic to new campaign links only after the handoffs are confirmed within your separately approved migration process. Preserve rollback URLs and agree an old-click conversion window with the network. Moving DNS alone does not translate stored IDs, statuses, or attribution history.

Which tracker fits your operating model?

Shortlist RedTrack when managed infrastructure, named provider feedback routes, and published spend-sync cadence match your daily work. Budget the required event allowance and seats, and resolve Solo's smart-distribution entitlement before buying for that feature.

Shortlist self-hosted Binom v2 when server control and licensing independent of click volume matter, with a named operator and funded infrastructure. Unlimited users, domains, and integrated page files may fit the workflow; none proves zero operating cost.

Shortlist Binom Cloud when Binom's campaign model fits but you do not want to supply its server. Confirm the $299 card's billing cadence, traffic boundary, support scope, and recovery responsibilities. Do not choose self-hosting merely because an older comparison describes it as Binom's only option.

Do not switch yet when the unresolved issue is an event mapping, permission, or renewal term the vendor can clarify. A lower license figure does not repay migration work automatically. For broader selection criteria, use the affiliate tracking software buying guide.

Where Tracked is today

Tracked publishes this comparison and has a commercial interest in the category. Its available core combines hosted HTML/ZIP pages, visual editing, owner-configured routing, click and conversion tracking, postbacks, reports, journeys, and teams. For that separate buying decision, see Tracked vs Binom; this page's main decision remains RedTrack versus Binom.

Universal CAPI, automatic winner selection, and governed cross-device attribution are in development in Tracked. Meta handling is partial: it accepts supplied event data, not automatic forwarding of every recorded postback to Meta. Signup does not make these complete workflows available.

A displayed Tracked price does not establish purchase availability. Paid checkout depends on matching live Stripe Prices being configured. Catalog limits are display-only, not verified enforced capacity or a basis for savings claims against either competitor. Evaluate the available free core without assuming a paid upgrade or provider parity.

Frequently asked questions

Is Binom cheaper than RedTrack?

The self-hosted v2 license lists $149 monthly versus RedTrack Solo at $169 monthly. Binom still needs infrastructure and an operator; RedTrack adds event overages and relevant add-ons. Binom Cloud is separate and displays $299 with cadence requiring confirmation. Those headline figures do not establish equal workload cost.

Does Binom require my own server?

Self-hosted Binom v2 does. Binom Cloud does not: its pricing FAQ says the server, monitoring, and optimization are included. Ask about backup, restore, region, and capacity terms for the specific Cloud offer.

Does Binom support Facebook CAPI?

Its official changelog added Facebook CAPI as Beta in v2.36.00 on October 6, 2026. Do not equate that with universal provider coverage or confirmed general availability. Check your version, account eligibility, event inputs, and supported use with Binom.

Are RedTrack events the same as Binom clicks?

No. RedTrack's allowance covers clicks, conversions, and processed postbacks. Binom advertises a license fee independent of click volume, while server capacity and Cloud traffic terms remain separate concerns. Ask each vendor to map the same funnel rather than comparing visitor totals directly.

Is Binom Smart Rotation the same as RedTrack Smart Distribution?

The reviewed mechanisms differ. Binom documents routing around a visitor's previously seen combinations and conversions. RedTrack documents adjusting path weights from conversion history and configured goals. RedTrack's Solo entitlement also conflicts between pricing copy and its help article.

Can old click IDs move with the tracking domain?

A DNS change does not move the click database or translate IDs. Keep old callbacks attached to the original system while rebuilding and confirming new campaign handoffs. No complete RedTrack–Binom click-history importer was established here.

Sources and update history

October 28, 2026: first publication. Reviewed first-party pricing, help, v2 documentation, and current release notes. No purchases, benchmark runs, or live campaign experiments. Open questions remain RedTrack Solo smart-distribution entitlement, Binom Cloud billing cadence, and Binom's deployment-specific trial terms.

• RedTrack pricing: affiliate plans, annual promotion, event definition, overages, seats, domains, spend sync, and named provider paths.
• RedTrack smart distribution, landing-page setup, and conversion methods: routing mechanics and campaign handoffs. We use the conversion guide for setup instructions, not its dated browser-policy commentary.
• Binom product, pricing, and v2 installation: deployment choices, price labels, infrastructure inclusion, and minimum requirements.
• Binom campaigns, Smart Rotation, postbacks, and users: routing, conversion statuses, outbound controls, and permissions.
• Binom integrated landers, Files, and changelog: file workflow and version-specific CAPI Beta status.

To evaluate Tracked's available core separately, Start free. Begin with one page and one offer: connect the route, preserve the offer-click ID, and review the resulting conversion journey before considering a migration.