Your Brand Is in a Scam Ad — What Should You Do First?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
Capture before you click away: a timestamped screenshot showing the ad and its destination URL. Then scan your domain — if the destination is a lookalike, the scan documents it with DNS and certificate evidence. Then file: per-variant reports on Meta from your verified Business Manager account, and a Google Ads trademark report listing the destination domain, stating clearly whether any advertiser is authorised to use your mark.
What is your brand in a scam ad — first moves?
A scam-ad incident is the ad variant of impersonation: paid media wearing your brand, pointing at infrastructure you do not control. It is one of the case system's four target types, and two packet channels — Meta and Google Ads — exist for it, each with its own evidence demands, so the first hour's job is capturing what those two channels will ask for.
What is your brand in a scam ad — first moves?
A scam-ad incident is the ad variant of impersonation: paid media wearing your brand, pointing at infrastructure you do not control. It is one of the case system's four target types, and two packet channels — Meta and Google Ads — exist for it, each with its own evidence demands, so the first hour's job is capturing what those two channels will ask for.
Detection starts with the free scan on TakedownCoop's home page. From your one genuine domain, the scanner builds the candidate set an impersonator would plausibly register — typosquats made by deleting, transposing, duplicating or substituting letters, homoglyph lookalikes, affix combinations, and TLD swaps — and tests each candidate against live DNS. That order matters for your brand in a scam ad — first moves: generation first, evidence second, and nothing is called a hit until DNS or a certificate log says it is real.
How the scan ranks and records it
The results are ranked, not dumped. The scanner's own priority scores put a resolving lookalike with a certificate at 90 and one without at 80, registered-but-dormant names at 50 or 40 depending on whether a certificate exists, and CT-only discoveries at 35 or 30. Certificate Transparency evidence is filtered for relevance — shared certificates carrying unrelated names are not treated as evidence against your brand — and any check that could not be performed is reported as exactly that, never converted into a reassuring claim.
Two channels, two evidence shapes, one destination
Meta will judge the creative; Google will judge the destination and the trademark. The capture discipline serves both at once: the screenshot with the destination visible is Meta's per-variant exhibit and Google's display/destination pair in a single frame. Miss the destination and both filings weaken — an ad can be re-created in minutes, and without its landing domain you are reporting a ghost.
The scan then does what a screenshot cannot: it establishes whether the destination is part of a wider street — sibling lookalikes, dormant variants, a CT trail — so your filings land on a documented campaign, not a single ad. And the authorisation statement closes the last gap: who, if anyone, may advertise under your mark, stated before the reviewer has to ask. First moves, done in this order, turn an alarming screenshot into three filings by the end of the day.
A worked example, end to end
A fictional coffee brand, Altura Coffee at alturacoffee.com, is tagged in a post exposing a '50% off' ad using its photography. The social manager screenshots the ad at 10:05 with the destination altura-coffee-shop.com visible, before the post is deleted. The scan scores the destination 90. By close of business: two Meta variant reports filed from the verified Business Manager account, one Google Ads trademark report listing the domain and stating no advertiser is authorised, and a scam-ad case opened with the registrar packet for the destination domain attached.
Turning evidence into a filing
Evidence only helps if it arrives in the shape the channel expects. TakedownCoop's packet generator produces one packet per channel — registrar, host, Meta, Google Ads, marketplace, app store — each with that channel's own subject line and filing checklist, built on the same evidence block: genuine brand, lookalike domain, detection method, DNS and CT evidence, and priority. Packets are a Pro feature ($49/mo; Agency $99/mo covers multiple client brands), and they are prepared for the brand owner or their authorised agent to file.
- Screenshot the ad immediately — timestamp, creative and destination URL in frame
- Scan your domain and match the destination to documented lookalike evidence
- File Meta reports per variant from your verified Business Manager account
- File the Google Ads trademark report listing every destination, with your authorisation position stated
- Open the scam-ad case and attach the domain's own registrar filing
After you file: tracking the case
The follow-through is where most takedowns quietly die, so the product tracks it as a case. States run from evidence collected through packet built, submitted and provider response, to resolved — and a case can be re-opened as reappeared when monitoring finds the same threat back. Submitted and provider-response states are recorded as holder attestations, honestly labelled, while a verified resolution needs a re-scan showing the target is gone. The recheck after submission is set at seven days.
Where efforts like this usually go wrong
A second failure is overreach — padding a filing with suspicions the evidence does not carry. TakedownCoop's scan is careful to separate what it confirmed from what it could not check, and a filing should inherit that discipline exactly: claim the resolving domain, the certificate, the screenshots you actually hold, and stop there. Reviewers act fastest on filings whose every sentence they can verify, and a single inflated claim taxes all the true ones beside it.
Finally, do not let a win delete the record. Brands that close a takedown by celebrating and clearing the folder meet the reappearance defenceless; brands that keep the case — evidence, tickets, verified resolution and all — meet it with precedent. In this product the record is not paperwork after the work. Kept properly, it is most of the work, because the second filing is always the one that ends the pattern.
Keeping it from coming back
Impersonators rotate, so a one-off filing is a snapshot, not a solution. Monitoring re-scans the domain, and when a known threat reappears the case re-opens and its packet regenerates. Pair that with the verified-genuine page — a public page where customers can confirm they are dealing with the real brand — and the timeline export (JSON and CSV) that processors and insurers ask for, and your brand in a scam ad — first moves stops depending on whoever happens to notice the fake next.
Frequently asked questions
The ad disappeared before I could capture it. Now what?
Re-search your brand terms — the Google checklist's weekly rhythm exists for this — and ask the person who saw it for their screenshot. The destination domain may still be findable via the scan.
Do I report the ad or the domain first?
Capture the ad first — it is perishable. Then file both: the ad channels judge the creative and destination; the registrar judges the domain itself.
A legitimate reseller's ad looks similar. Risk?
That is why the filing states who is authorised. Name your resellers in the Google report so enforcement lands only on the impersonator.
How many Meta reports for one campaign?
One per variant, because Meta treats each creative as its own case.
Keep exploring
TakedownCoop home — run the free brand scan · All TakedownCoop guides · Pricing — Free, Pro and Agency · Get a license key · Takedown cases · My street (dashboard) · Terms · Privacy · Ingenious AI — all platforms
Related guides
- Someone Registered Your Brand with a Different TLD — What Next?
- A Fake Profile Is Messaging Your Customers — What Should You Do Next?
- Why Do Fake Shops Target Your Busiest Sales Periods?
- How Do You Monitor Your Brand Terms in Search Ads Weekly?
- How Do You Monitor App Store Search for Clones Weekly?
- How Do You Build a Brand Protection Routine for a Small Team?