Table of contents

Introduction: What Problem Does Keitaro Solve and Why It’s Essential for Arbitrage

In 2026, traffic costs are rising, moderation is tightening, and attribution rules are becoming more complex. Many sources reduce referrer data, hide click identifiers, and impose redirect limits. At the same time, the share of mobile and in-app traffic is increasing, where correct tracking can prevent a loss of 20-40% of conversions. We are facing a fragmented infrastructure: ad accounts, anti-detect browsers, mobile proxies, affiliate networks, CDNs, and offer walls all need to be interconnected to ensure data integrity while each link undergoes testing and optimization. A professional tracker is required to manage click streams, accurately calculate metrics, and automate decisions.

Keitaro is a self-hosted tracker for affiliate marketing and arbitrage, installed on your VPS or server, providing full control over data. It addresses common tasks for arbitrageurs: traffic distribution based on rules, cloaking for moderation compliance, integration with affiliate networks, A/B testing of landing pages and offers, automatic rotations, and detailed real-time statistics. With deep integration for proxies and anti-detect tools, Keitaro helps safely test offers from target geos, mask the referrer, and manage content visibility for moderators and real users.

This article provides practical scenarios, step-by-step instructions, and real case studies with numbers. We will explore how to configure Keitaro, its features, its usefulness for platforms like Facebook, Google, TikTok, native networks, and push platforms, and why a self-hosted approach is cost-effective and resilient for advertising infrastructure.

Keitaro Service Overview: Key Features and Benefits

Deployment Format: Self-hosted. You set up Keitaro on your own VPS or dedicated server. This reduces the risk of tracker account blockages, simplifies compliance with data storage requirements, and provides flexibility in network settings, including use of your own proxies and domains.

Tracking and Routing: Keitaro accepts clicks from any source, assigns parameters and tags, routes according to rules, and logs conversions. Flexible rules allow traffic to be split based on geo, device, OS, browser, provider, language, time, connection type, and many custom parameters. You can build complex schemes: white and black traffic streams, multi-landing rotation, random and weighted distribution, and auto-optimization based on conversion and profit.

A/B Testing and Auto-Optimization: Launch multiple landing pages and offers within a single campaign. Keitaro distributes traffic, measures CR, EPC, ROI, time on page, and button clicks (if event code is implemented), gradually shifting traffic toward the winners. This saves budget on tests and provides transparent answers about which combination earns more.

Cloaking and Masking: Prevention of moderation issues with major traffic sources. Keitaro allows showing moderators a safe version of the page (white) while presenting the targeted offer (black) to real users. Filters based on traffic descriptors, providers, and behavioral signals reduce the likelihood of account bans. Additional features for masking the referrer and ensuring proper redirects minimize leaks and anti-fraud triggers.

Integrations with Affiliate Networks: Keitaro includes postback templates for over 300 affiliate programs. Just select the network, pull parameters, enter the secret, and get accurate conversions with payout, status, and IDs immediately. Supports several levels of postbacks — from leads to upsells and repeat purchases — as well as field mapping for desired KPIs.

Working with Proxies and Anti-Detect Solutions: Integration with mobile proxies for testing offers from target geos, IP rotation, and clean user profiles. Support for anti-detect browsers helps manage account farms and work safely with ad accounts. Within Keitaro, it is easy to assign test streams to specific IP pools and distinct domains for cloaking.

Real-Time Statistics: Access to key metrics — clicks, visits, conversions, CR, EPC, ROI, revenue, cost, profit — with detailed slices by sources, campaigns, geos, devices, landing pages, and offers. Flexible reports help address practical questions: who yields conversion below CPL, where CR is dropping, and what hinders scaling.

Cost: Pricing starts at $49 per month. Being a self-hosted solution, Keitaro does not take a commission on revenue, allowing you to optimize tracking costs as you scale.

Conclusion: Keitaro is a reliable workhorse for arbitrageurs and performance teams. It facilitates safe campaign management in sensitive sources, speeds up hypothesis testing, and ensures accurate profit attribution. Next, we’ll share seven scenarios where it excels.

Scenario 1: Facebook Ads and Nutra: Cloaking, Mobile Proxies, and Quick Optimization

Who It’s For and Why

Suitable for arbitrageurs running Facebook Ads targeting nutra offers with a risk of rejection. The goal is to pass moderation, maintain accounts, and quickly identify profitable combinations based on geo and devices.

How to Use Keitaro

  1. Deploy Keitaro on a VPS and connect domains: a main domain for white pages and an operational one for black. Separate by zones to simplify switching in case of complaints.
  2. Create a campaign. Within it, have two streams: white and black. In white, add white content with neutral themes and correct platform policies. In black, include landing pages for nutra offers.
  3. Set up cloaking: filters based on user agent, ASN of major data centers, suspicious IPs, and checking hosts. Connect mobile proxies based on target geos, so your team sees black as real users do.
  4. Add A/B rotation of landing pages and pre-landers in black. Assign equal weights at the start and enable auto-optimization based on EPC or ROI.
  5. Select an affiliate network from the postback templates, input the secret and parameters. Ensure that conversion status and payout are mapped correctly.
  6. Pass UTM and click ID attribution tags to Facebook, allowing you to analyze each ad down to the creative and adset level in Keitaro.
  7. Include slices in reports by geo, device, mobile IP provider, and source. Eliminate irrelevant landing pages based on actual EPC within the first 500-1000 clicks.

Case Study and Results

A team of three buyers launched nutra campaigns for Thailand and Vietnam. In 10 days: 36,240 clicks, CR 1.8%, 652 conversions, average payout $14.2, revenue $9,258.4. Traffic costs were $7,920, tracking and server costs $146. Net profit was $1,192.4, ROI 15.05%. In Keitaro, auto-optimization disabled two of five landing pages, raising EPC from $0.22 to $0.255 on the 4th day. The cloaking rules filtered 91% of moderation traffic, reducing account bans from three to one during this period.

Life Hacks and Best Practices

  • Use separate domains for each vertical and source to quickly replicate infrastructure in case of complaints.
  • Start auto-optimization only after 300-500 clicks per variant; early shifts can yield false winners.
  • In reports, maintain ASN and ISP slices. If the share of data centers is increasing, it indicates a weakness in the cloaking filter, requiring tighter thresholds for suspicious IPs.
  • Implement different event codes on pre-landers for analyzing scroll depth and button clicks. This helps filter out landing pages with high CTR and low CR.

Scenario 2: Google Ads for SaaS: A/B Testing and Server Attribution via Postbacks

Who It’s For and Why

Suitable for products and affiliates promoting SaaS with trial offers. The aim is to connect paid traffic with activations within the product, gain accurate CAC, and scale campaigns through automated optimization.

How to Use Keitaro

  1. Create a campaign for Google Ads and set up traffic sources with UTM templates. Add lander-split: options with different offer packages and fields, one without a credit card, two with a credit card but different text.
  2. On landing pages, implement event codes that send micro-conversions to Keitaro: scroll depth, CTA click, form start. This helps forecast final CR from small volumes.
  3. Within your SaaS, set up server postbacks in Keitaro for the events trial_started and paid. Tie the user click ID or email hash if permissible by your policy.
  4. Enable auto-optimization of rotations based on EPC, where payout changes according to status: $0 for trial, tiered payout for payment, and set average margin.
  5. In Keitaro reports, compare sources and creatives based on trial and paid CR. Highlight combinations with the worst trial-to-paid ratio for offer packaging review.

Case Study and Results

A performance team tested 3 landing pages and 2 pricing grids. Over 21 days: 18,900 clicks, 1,134 trials (6%), 218 payments (19.2% of trials), average check $39. Traffic expenditure was $12,285, revenue $8,502, with an overall negative test result. After auto-disabling the landing page with a credit card form, EPC rose from $0.29 to $0.37, while the payment share of trials increased from 16.1% to 21.4%. Over a 45-day horizon, LTV covered CAC, allowing campaigns to scale without deteriorating ROI.

Life Hacks and Common Mistakes

  • Do not optimize based solely on trials. In Keitaro, utilize a combined KPI of EPC for 14-30 days and weight for micro-events.
  • Launch white pages for brand searches and a separate pre-lander for cold audiences; analyze them separately by CR.
  • Check postback accuracy. Often, the click ID field is lost due to redirects between the landing and the application.

Scenario 3: Push and Pop Traffic for Sweepstakes: Rules by OS, Provider, and Connection Type

Who It’s For and Why

Ideal for push networks, pop-unders, and teaser networks where device and provider filters are crucial. The goal is to capture installs, subscriptions, and leads by geo with minimal debates over quality.

How to Use Keitaro

  1. Create a campaign and set device rules: separate Android, iOS, Windows. For Android, isolate versions below 10 into a separate stream.
  2. Set up filters by ISP and connection type. Use mobile-only for subscriptions, and reserve white pre-landers with explanations for Wi-Fi.
  3. Enable rotation of 4-6 pre-landers with varying motivations: giveaways, coupons, promo codes, quick tests. Start auto-optimization based on CR.
  4. Utilize provider filters to exclude operators with high anti-fraud percentages from the affiliate. This will reduce returns.
  5. Synchronize hold approved declined statuses in postback to view actual ROI without illusions.

Case Study and Results

An arbitrageur tested sweepstakes in Mexico. 52,400 clicks, 1,398 leads, CR 2.67%, average payout $2.8. Before filters, ROI was -11%. After separation by ISP and mobile-only type, ROI shifted to +8.5%. Excluding two operators reduced hold time by 3 days and decreased cancellations from 22% to 11%.

Tips and Mistakes

  • Do not route all Wi-Fi to the main subscription offer. Use a white pre-land or an alternative with a lower likelihood of chargebacks.
  • Handle old Android versions with separate landers without heavy scripts: speeding up loading times noticeably increases CR.

Scenario 4: TikTok Ads: Anti-Detect, Account Farms, and Safe Domains for Cloaking

Who It’s For and Why

Well-suited for teams working with TikTok Ads and short creatives. The goal is to pass moderation, maintain account grids, and scale white and gray cloaks with minimal bans.

How to Use Keitaro

  1. Organize an account farm in an anti-detect browser and distribute mobile proxies across geo clusters. Assign separate domains for white and black streams.
  2. Create a cloaking campaign in Keitaro. Rules: suspicious user agents, data center IPs, low activity based on behavioral metrics — in white. Real users — in black.
  3. Add multi-landing rotation in black with pre-landers optimized for short-video formats: quick tests, Telegram bots, quizzes. Enable auto-optimization based on EPC and pre-lander CTR.
  4. Integrate the affiliate network from the postback template and verify statuses. For three event levels, use a single postback chain in one stream.
  5. Monitor peaks of moderation traffic and the percentage of visits from suspicious ASNs in reports. If it exceeds 15-20%, tighten filters or change the domain.

Case Study and Results

A team with a grid of 15 accounts generated leads in the financial vertical across several APAC geos. In 14 days, 7,200 leads were generated at $3.9 each, with an average payout of $5.1, yielding a gross margin of 30.7%. Bans decreased by 2.3 times after implementing ASN filters and updating domains every 3-4 days. Auto-rotation disabled two pre-landers with low CTR, leading to a 12% decrease in CPC and a CR increase from 4.8% to 6.1%.

Life Hacks

  • Rotating domains every 3-7 days minimally impacts stability if you maintain a DNS pool and automate linkage to Keitaro.
  • Separate white and black streams by subnets; do not host them on the same server. This leaves fewer traces for moderation.
  • Limit click cookie lifespan so that moderators returning for a second time more often land in white.

Scenario 5: Scaling the Team: Roles, API, and Automated Optimization Rules

Who It’s For and Why

Ideal for agencies and large teams. The goal is to standardize link schemes, reduce manual operations, and speed up campaign rollouts in various markets.

How to Use Keitaro

  1. Describe campaign templates: source, UTM, parameters, set of pre-landers, offers, distribution rules, and events. Save as presets or via API.
  2. Implement roles: buyer, team lead, analyst, engineer. Restrict access to campaigns, domains, and reports.
  3. At the campaign level, enable auto-optimization: disable an option with EPC below the median by x percent after n clicks. Increase the weight of the winning lander by y percent based on Wald's simple rule.
  4. Create an API script for updating domains and replacing links when a ban trigger is activated. Reduce the TTR for restoring links to minutes.
  5. In Keitaro reports, utilize slices by buyers and sources. Compare actual ROI with targets and automatically pause campaigns when EPC falls below the threshold.

Case Study and Results

An agency with 9 buyers transitioned 78 campaigns to templates. The average time to launch a new link dropped from 2 hours to 18 minutes. Auto-rules disabled 11% of unprofitable options within 300 clicks, saving $6,200 per month. Downtime after a domain ban decreased from 4 hours to 11 minutes thanks to API scripts.

Life Hacks

  • Keep optimization threshold settings in one configuration. This simplifies KPI reviews during seasonal peaks.
  • Create a pre-flight checklist: domains, postback, UTM tags, test lead, source report. Keitaro allows you to run a test click and verify the entire chain.

Scenario 6: Mobile Subscriptions and Carrier Billing: Provider, Speed, and Conversion

Who It’s For and Why

Suitable for verticals using operator balance for payments. The goal is to improve CR through proper distribution among providers, accelerating landing pages, and adapting for older devices.

How to Use Keitaro

  1. Enable provider identification and connection type in Keitaro. Create separate streams for each major mobile operator and one general for Wi-Fi.
  2. Add versions of the landing page with stripped-down scripts and images for older Android devices. Serve these for OS versions below the threshold.
  3. Implement pre-lander speed checks and events like scroll and button click to monitor where users drop off before the offer.
  4. Match CR by operator with hold and cancellation rates from postbacks in reports. Exclude operators without profit.

Case Study and Results

The team tested subscriptions in Indonesia and Egypt. A total of 61,000 clicks, 1,960 subscriptions, CR 3.21%, average payout $1.4. After separation by providers and implementing a lightweight landing for Android 7-9, CR rose to 3.9%, and cancellations fell from 26% to 17%. Final ROI shifted from -7% to +12%.

Tips

  • Keep redirect timeouts minimal. Carrier portals often strip excessive referrers and redirects.
  • Build reports in Keitaro based on the combination of operator and OS version. In low-cost segments, weak devices and poor internet are the main CR barriers.

Scenario 7: Native Advertising and Content Arbitrage: Multi-Landing and Cohorts

Who It’s For and Why

Best for Taboola, Outbrain, MGID, and content networks. The goal is to drive traffic to articles and reviews, rotate widgets and offers within content while measuring profitability by the source of creative and platform.

How to Use Keitaro

  1. Create a campaign with content landers, each containing several offer widgets. Set up separate goals for clicks by widget in Keitaro.
  2. Launch multi-landing rotation. For content, use different angles: success stories, reviews, comparisons. Enable auto-optimization based on EPC.
  3. Gather events lead sale repeat purchase via postbacks. Include cohorts based on the first click date in reports.
  4. Test article length and offer placement density. Keitaro will help identify which screen engagement drops.

Case Study and Results

The content arbitrage campaign in nutra and finance across EU Tier 2. 24,300 clicks, 5 articles, 9 offers. Before optimization, EPC was $0.38. Keitaro disabled two articles with high bounce rates, added a comparison chart for offers, and moved the CTA higher. EPC increased to $0.52, and page RPM rose by 31%. Scaling across platforms kept ROI above 20%.

Life Hacks

  • Tag sources and widgets in detail. In Keitaro reporting, you should link source creative platform slot widget.
  • Analyze the funnel events within the article: read-through rates, clicks on anchors, FAQ expansions. This helps decide where to position offers.

Comparison with Alternatives: Why Keitaro Outperforms Cloud and Self-Hosted Solutions

Voluum, RedTrack, BeMob, and other cloud-based trackers simplify the startup process, don’t require a server, and provide ready integrations. However, their downsides are dependency on external infrastructure, limitations on domains and moderation policies at sources, and increasing costs with volume growth. Keitaro, as a self-hosted solution, doesn’t take a commission on revenue and allows flexible domain and proxy management while finely tuning cloaking, which is critical in sensitive moderation verticals.

Binom and other self-hosted solutions are similar in spirit to Keitaro but often fall short in the breadth of postback templates and out-of-the-box cloaking convenience. Keitaro focuses on advanced routing, support for anti-detect setups and mobile proxies, and delivers clear auto-optimization. Plus, there's an active ecosystem of presets and scenarios that are easily scalable via API.

Final Conclusion: If speed of startup without needing servers is crucial — choose cloud solutions. If control, cloaking, and proxy integration at a lower cost of ownership when scaling is what you need — Keitaro has the advantage.

FAQ: 10 Practical Questions

How to Quickly Set Up Keitaro?

Prepare a VPS with the current stack, assign domains for white and black, launch the installer, create your first campaign, and run a test click with postback. The basic setup takes between 30 to 90 minutes.

Which Proxies Are Best for Testing and Cloaking?

For moderation and realistic testing, opt for mobile proxies with residential IPs in the target geo. For internal tasks and bulk validations, resident and quality data center proxies suffice. In Keitaro, they can be assigned to separate streams.

How to Configure Auto-Optimization?

Enable distribution based on EPC ROI metrics and specify a minimum volume for decision-making. For example, disable a variant at 500 clicks if EPC is 20% below the median, and increase the weight of the winner by 15%.

What to Do if Conversions Aren’t Coming?

Check the chain: click ID parameters in the link, the accuracy of redirects, affiliate network template settings, statuses in postback, and server firewall. Run a test lead from the partner's interface and track it in Keitaro.

Is It Possible to Operate Without Cloaking?

Yes. Keitaro is also valuable for white verticals: landing page tests, source merging, micro-events, creative reports, postbacks, and server attribution. Cloaking is only engaged where necessary.

How to Minimize Domain Bans?

Maintain a pool of domains, separate white and black streams into different subnets, refresh SSL, implement clean redirects, mask referrers, and avoid mixing risky offers on the same domain.

How to Control Spending and Metrics?

Pass cost from the source via tokens or load it through API. Build reports based on the source campaign adset creative and monitor EPC and ROI at every level.

Does Keitaro Support Multi-Level Conversions?

Yes. You can accept multiple events per click, assign payout to each, and utilize them in auto-optimization, e.g., trial started, paid, upsell.

What About Performance at High Volumes?

On an optimized VPS with SSD and caching, Keitaro confidently handles heavy loads. Vertical and horizontal scaling is achieved through static file offloading, domain balancing, and database optimization.

How Much Does It Cost?

Pricing starts at $49 per month plus the costs of your server and domains. Generally, self-hosted solutions turn out to be cheaper than cloud options at the same click volumes.

Conclusions: Who is Keitaro For and How to Start

Keitaro is a professional self-hosted tracker for arbitrage and affiliate applications, emphasizing infrastructure control, cloaking, proxy usage, and precise attribution. It enables safe campaign management in Facebook, Google, TikTok, native networks, and push platforms, speeds up landing page testing, automates rotations, and facilitates data-driven decision-making rather than intuition-based choices. If you're operating in verticals with moderation risks or scaling your team, Keitaro provides a genuine competitive edge: quick launch speed, reliable reporting, integrations with partners, flexible routing rules, and cost savings at scale.

To get started quickly: choose a VPS, install Keitaro, connect domains, create your first campaign, set up source templates, link partners via the provided postback, implement event codes on landing pages, and check attribution against a checklist. Launch A/B testing with auto-optimization, and after 2-4 days, evaluate initial results. Scale up by adding scenarios: cloaking for moderation, ASN ISP filters, device slices, and then roles, API, and auto-rules for your team. This way, you’ll create a solid system where every click works towards profitability, not chaos.