Start with what you can prove
Preserve the campaign and ad-set context, timestamp, landing URL, click or browser identifier available to your stack, observed network type, and the session behavior. Keep the language factual: “the session arrived through a network classified as a VPN” is supportable; “Meta delivered this ad to a user in another country” may not be.
Why multi-layer evidence matters
Meta describes a multi-layered approach to fraud and scam prevention that includes automated technical defenses, account and asset enforcement, and partnerships. A VPN signal is therefore best used to identify a cluster for investigation, not as a replacement for Meta’s internal classification.
For advertisers, the commercial question is whether a segment of paid traffic is producing the expected business outcome. Compare VPN/proxy clusters with session depth, lead quality, add-to-cart activity, purchase completion, and repeat-click timing. Include the control group so the reviewer can see the difference.
How to keep the report credible
- State the source and timestamp of the network classification.
- Keep real customers who use privacy tools out of any automatic block rule.
- Use platform-native campaign exports to reconcile clicks with onsite sessions.
- Do not claim that Meta endorses BotRefund or guarantees a credit.
Read the full VPN Detection overview or continue with the privacy and fairness guide.