Seatext library / BotRefund evidence
How BotRefund Is Implemented on Your Website
BotRefund is implemented by adding a lightweight tracking script to your website — a process that takes about one minute and requires no credit card. The script monitors every session from affiliate click to...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
BotRefund is implemented on your website by adding a lightweight tracking script — a process that takes about one minute and requires no credit card. You don't need platform integrations to start: the script reads UTM and click IDs directly from the traffic arriving at your site.
Once installed, the script monitors every session from affiliate click through to conversion. It captures behavioral signals, device data, and the full attribution path. Before each payout cycle, you receive a report that scores every affiliate conversion as Approve, Review, Hold, or Reject — with evidence behind each tag.
What the tracking script does after installation
The script runs quietly on each page of your site and watches for patterns that separate human visitors from automated ones. BotRefund uses 106 independent checks to build a picture of each session. Those checks fall into several groups:
- Click behavior — catches ghost clicks that happen without the natural sequence of human intent.
- Trap behavior — honeypot interactions where bots respond to hidden or intentionally deceptive page elements.
- Pointer behavior — robotic linear mouse movements that rarely appear in real user sessions.
- Motion behavior — absence of the small tremor typical of human movement.
- Speed behavior — input under 1 ms, faster than a person could realistically act.
- Path behavior — movement that snaps to precise grid lines instead of natural curves.
- Engagement behavior — sessions that stay too static to match a real browsing journey.
- Session behavior — visit lengths that are too short, too long, or too uniform to be human.
Each signal is one piece of evidence. BotRefund feeds the complete pattern into its prediction model, which evaluates the signals across browser, network, device, and behavior data. The company reports 99% accuracy in identifying a visit as bot or human.
Step-by-step implementation process
Implementation is a small, well-defined job. Here is the full process:
- Get the tracking script. You receive the script from your BotRefund account or during onboarding.
- Add it to your site. Paste the script into your site's code — most teams put it in the header or use Google Tag Manager. This step takes about one minute.
- Confirm UTM parameters. BotRefund reads UTM and click IDs from your traffic to identify which affiliate and click ID drove each conversion. Check that your affiliate links include them.
- Start the free audit. Data collection begins as soon as the script is live. You can export a report and use it in a Google or Meta refund claim.
- Set up reconciliation (optional at start). For exact payout matching, upload your monthly payout CSV or connect your affiliate platform later — no need to do it on day one.
Prerequisites before you install
You do not need much to get started:
- Website access. You or a developer must be able to paste the tracking script into your site's code.
- UTM parameters or click IDs. These let BotRefund attribute each conversion to the correct affiliate. If you don't have them yet, add them to your affiliate links before installation.
- No credit card. BotRefund is added to your site with no payment required to begin.
If you cannot set UTMs today, you can still start — but attribution will be less precise until you upload payout CSVs or connect your affiliate platform.
Understanding the payout review report
Before each payout, your finance and affiliate teams get a report that tags every conversion:
- Approve — clean traffic, standard buyer behavior, attribution path intact.
- Review — anomalies present, worth a manual look before paying.
- Hold — strong fraud signals, payout should pause pending investigation.
- Reject — clear evidence of manipulation, the commission should be declined.
The report comes with evidence, not just a score. That lets your team hold or decline a payout with confidence rather than making a judgment call on a number.
What BotRefund catches that click-level tools miss
Most affiliate fraud is not bot clicks. It happens after the click, when a real session is manipulated so the affiliate takes credit for a conversion they did not drive. Three patterns often hide behind commissions that normal click-level tools pass as clean:
- Last-click hijacking — an affiliate fires a redirect or drops a cookie in the final seconds before a user converts, stealing credit from whoever actually drove the signup or sale.
- Cookie stuffing — tracking cookies placed silently via hidden images or iframes. No user interaction, no real referral, yet a commission is claimed anyway.
- Coupon extension overwrites — browser extensions that inject affiliate cookies at the moment of purchase, claiming commission on a sale the affiliate had no part in.
None of these show up as bot traffic. They look like legitimate conversions. Behavioral signals and attribution-path analysis are what surface them.
Key facts at a glance
| Fact | Detail |
|---|---|
| Setup time | About one minute |
| Credit card required | No |
| Platform integrations | Not required to start |
| Installation method | Lightweight tracking script on your site |
| Independent detection checks | 106 |
| Reported accuracy | 99% |
| Attribution data | UTM parameters and click IDs |
| Reconciliation options | Upload payout CSV or connect affiliate platform later |
Limitations and false-positive handling
BotRefund does not treat one anomaly as proof of fraud. Privacy tools, travel, corporate networks, and unusual devices can produce unexpected behavior in real people. The system cross-checks each signal against independent browser, network, device, and behavior data before making a call.
Points worth knowing:
- A single odd signal is not a verdict. The model weighs the complete pattern instead of trusting a raw rule.
- Evidence is provided to your team — the platform scores conversions, but your team makes the final decision on payout.
- If your campaigns do not set UTM parameters correctly, attribution will be less precise until you upload payout CSVs or connect the affiliate platform.
- The detection focuses on commissions you are about to pay. BotRefund also offers pixel protection to keep fraudulent sessions from distorting your conversion data.
Frequently asked questions
How long does BotRefund take to install?
About one minute. You paste a lightweight tracking script into your site's code and it starts collecting session data right away. No credit card is required.
Do I need to connect my affiliate platform first?
No. BotRefund reads UTM and click IDs from your traffic, so you can start before any platform integration. For exact payout reconciliation, upload your monthly payout CSV or connect your affiliate platform later.
What if I don't use UTM parameters?
Without UTM parameters, BotRefund cannot attribute each conversion to a specific affiliate from traffic alone. Add UTMs to your affiliate links before installing the script, or plan to upload payout CSVs for reconciliation.
What do Approve, Review, Hold, and Reject mean?
These are the four payout report tags. Approve means the conversion looks clean. Review means anomalies merit a look. Hold means fraud signals are strong enough to pause payout. Reject means the commission should be declined.
Can privacy tools or VPNs cause false flags?
They can produce unusual behavior, but a single anomaly is not a verdict. BotRefund cross-checks each signal against browser, network, device, and behavior data before flagging a session.
Does BotRefund work with both Google Ads and Meta Ads?
The detection signals apply to paid traffic from both platforms. The refund feature covers Google Ads spend dating back to 2017 and disputed Meta ad billing.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.