> AffiliateOS Help Center. Index of every article for AI tools: https://www.affiliateos.ai/help/llms.txt

# Traffic you may and may not send

Fraud Defense and traffic quality · For publishers, networks · Updated 30 October 2026
Web version: https://www.affiliateos.ai/help/fraud-defense/traffic-you-may-send

Send real people who chose to tap your link or open your wall, from the countries, platforms and US states the offer accepts. Don't send bots, faked devices or places, one person under many accounts, or users you reached with spam or misleading claims. Section 4 of the [terms](https://www.affiliateos.ai/terms#s4) is the rule; this page shows how it plays out in our checks.

## You may send

- **Real people who chose to tap.** In your app, on your site, in your newsletter.
- **Users you reward in your own currency,** on placements built for it: the Hosted Offerwall, or your own offer screen built on the Offer API or the Top Offers Feed.
- **Readers you don't reward,** through Offer Links: our team approves those offers one by one, for traffic that gets no reward. [Where incentivized traffic runs on AffiliateOS](https://www.affiliateos.ai/help/fraud-defense/incentivized-non-incentivized-traffic) explains the difference.
- **Users inside the offer's targeting.** On the Offer API, send the player's US state as `state` (`state=TX`): offers whose state list we enforce, and that turn that state away, are left out of your list. [Users in states or regions an offer doesn't accept](https://www.affiliateos.ai/help/links-and-tracking/excluded-states-and-regions) explains which.
- **Your own test users,** one test user ID per device.

## You may not send

| Not allowed | What happens |
|---|---|
| Bots and scripted browsers | The user is rejected, and earlier pay can be taken back |
| Users hiding where they are | The user is rejected, and earlier pay can be taken back |
| Faked or emulated devices | The user is rejected, and earlier pay can be taken back |
| One person under many accounts | The user is rejected, and earlier pay can be taken back |
| Users outside the offer's targeting | The page "This offer isn't available in your state" |
| Reward traffic on an offer that doesn't allow it | Agreed offer by offer. Ask before you reward users for an offer you got through Offer Links. |
| Faked sources: cookie stuffing, click injection, forced redirects, cloaked landing pages | Not a single check. Breaks section 4 of the terms. |
| Spam, malware, misleading claims or bidding on a brand's name where the offer forbids it | Not a single check. Breaks section 4 of the terms. |

The labels in bold are the reasons **Traffic Quality** shows. We don't publish the limits behind them.

## What happens to traffic that breaks them

1. **The tap is refused.** The user sees "This offer isn't available for your account". The advertiser never sees the tap, so nobody is paid for it.
2. **The user is rejected for 30 days.** Their conversions pay $0 and send no postback. They show on **Reporting**, then **Traffic Quality**.
3. **Earlier pay can be taken back,** as standard reversals with the reason in plain words: 7 days back for multiple accounts on one device, 30 days back for emulated devices, duplicate accounts, or a VPN or proxy.
4. **Our team can pause an offer for your account,** or more. The terms let us withhold, reverse or claw back pay for invalid activity, and suspend or close the accounts involved.

> **Rejected and reversed pay is gone.** A conversion we reject or reverse for invalid traffic isn't paid to you. If you already credited the user, the loss is yours: dedupe on `action_id` and `status`, and deduct on `status=reversed`.

## Not sure about a source?

Ask before you send it. [Contact us](https://www.affiliateos.ai/contact?topic=support) with the source, the countries and how users find the offer. A new kind of traffic is easier to approve before it arrives than to explain after it's rejected.