Anti-fraud policy

Why this exists

Performance campaigns only work if the actions we report are real. This policy sets out what we treat as invalid traffic, how we check, and what happens when a source fails.

What we treat as invalid

• Installs or events generated by bots, emulators, device farms or automation.
• Click spamming and click injection: large click volumes with abnormal click-to-install times, or clicks fired just before an install.
• SDK spoofing and faked postbacks.
• Incentivised or misleading placements where the campaign does not permit them.
• Traffic from sources, geographies or placements not approved for the campaign.

How we check

• Click-to-install time distribution per source.
• Install-to-event and event-to-retention ratios compared with organic baselines.
• Retention curves (D1, D7, D30) per source against the campaign’s quality gate.
• Attribution-platform fraud signals and blocklists.
• New sources start with a capped test budget and are reviewed before scaling.

What happens

Traffic that fails is excluded from reporting and billing. Sources that fail repeatedly are removed from the campaign and from our partner list. Disputes are resolved with data from the client’s attribution platform.

Reporting a concern

Clients and partners can raise a traffic-quality concern at any time at info@fixspotter.com.