CAKE vs Numok

CAKE is performance marketing software for affiliate campaign management and lead distribution. Advertisers, networks and publishers can use it to manage partner activity, measure results and optimize campaigns. Its affiliate tools provide real-time campaign and partner insights, customizable alerts, detailed data and commission structures. Campaign targeting can use location, device, browser, traffic caps and redirects; tracking includes pixel and postback management, event tracking, click and conversion caps, and mobile measurement. CAKE Leads+ validates and routes leads in real time using rules such as buyer rank, round-robin allocation, weighted prices, volumes, schedules, bids and budgets. Reports can be viewed live, exported to CSV or S3, or accessed through an API. Lead delivery methods include HTTP Post, JSON, XML, SOAP and email. Mobile campaigns can use postback integrations or the iOS and Android SDKs. CAKE lists fraud-prevention tools including pixel whitelisting and alerts for abnormal campaign behavior. Pricing is on request, and prospective customers can request a demo.

Numok is an open-source affiliate platform that connects to Stripe to track sales, calculate commissions, and queue payouts. Its reporting includes conversion rates, revenue by affiliate, and click-to-sale timelines. Affiliates get tracking links, an earnings dashboard, and payout history. The site says an affiliate program can be launched in under 15 minutes, and an admin dashboard and affiliate portal demo can be viewed without signup using live data. The free plan is self-hosted and includes the full source code for customization; the listed Open Source plan has unlimited affiliates and no per-seat fees, though no plan price is stated. Numok runs on the web or on your own servers. Installation calls for PHP 8.1 or higher, MySQL 5.7 or higher, Apache or Nginx, Composer, an SSL certificate, and a Stripe account. Setup also requires configuring Stripe webhook events. Its security checklist recommends HTTPS, secure file permissions, changing default database credentials, and using a server firewall. Bug reports and feature requests go through GitHub Issues.