Brand Safety And Fraud Prevention, Built Into Every Bid.

Invalid traffic (IVT) is commonly split into two classes. General invalid traffic (GIVT) is the easy-to-identify kind: known data-center IPs, declared crawlers and bots, and traffic that fails basic validity checks. Sophisticated invalid traffic (SIVT) is engineered to look human — emulated devices, hijacked SDKs, device farms, attribution manipulation — and needs behavioral and statistical analysis to detect.

Before Adora X places a bid, every request is checked. Traffic that fails these checks is never bought.

• Request validity: malformed or inconsistent bid requests (impossible device/OS combinations, mismatched app identifiers) are dropped.
• Supply authorisation: we check sellers against app-ads.txt and sellers.json so we only buy inventory from authorised sellers.
• IP and device reputation: known data-center ranges and device identifiers previously linked to invalid activity are blocked.
• Supply-path quality: placements and sources with a history of abnormal patterns are excluded or down-weighted.
• Brand-safety rules: app category, content rating and advertiser-specific block lists are applied before the bid.

Some fraud only becomes visible after the impression or the install. We monitor delivery and outcome patterns continuously and act on sources that look wrong.

• Click-to-install time (CTIT) distributions — very short CTIT suggests click injection; very long, flat distributions suggest click spamming.
• Engagement depth — installs with no sessions, no events or identical event sequences point to bots or farms.
• Device and geo consistency — mismatches between bid-time, click-time and install-time signals.
• Placement-level anomalies — sudden spikes in volume, CTR or conversion rate without a creative or bid change.

Click injection happens when a malicious app on the device detects a new app being installed and fires a click just before the first open, stealing the attribution. Install hijacking more broadly covers any technique that claims credit for an install another source (or organic discovery) actually drove. Both inflate a source's apparent performance while the advertiser pays for users they would have acquired anyway.

Defenses combine MMP-side signals (install referrer timestamps on Android, CTIT analysis) with our own source-level monitoring. When a source shows these patterns we block it, and fraudulent conversions rejected by your MMP are excluded from billing according to the agreed terms.

Your MMP is the neutral referee. Most leading MMPs offer fraud-protection suites that reject or flag suspicious installs and in-app events in real time and after the fact. We configure postbacks so that rejected installs and their reasons flow back to Adora X, reconcile them weekly with you, and feed those signals into source-level decisions — so the same pattern is not bought twice.

No platform eliminates fraud entirely, and we do not claim third-party certifications we do not hold. What we commit to is transparency: source-level reporting, clear rules on how rejected conversions are treated, and fast action when you or your MMP flag a problem.