← Go back

Why Should Every Ad Variant Be Reported Separately?

Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team

The short answer

Because the channels judge creatives, not campaigns. TakedownCoop's Meta checklist states it directly: report every ad variant separately — Meta treats each creative as its own case. One umbrella complaint leaves the other variants running, while per-variant reports, each with its own screenshot and destination domain, give every case a complete, independent chance of removal.

Run the free brand scan — one domain, no account, no card

What is reporting ad variants separately?

An ad variant is one distinct creative — one combination of copy, image or video and destination — running under an impersonation campaign. Variant-level reporting is the discipline of filing each one as its own case with its own evidence, the rule written into the Meta packet and echoed in the marketplace packet's per-listing rule.

What is reporting ad variants separately?

An ad variant is one distinct creative — one combination of copy, image or video and destination — running under an impersonation campaign. Variant-level reporting is the discipline of filing each one as its own case with its own evidence, the rule written into the Meta packet and echoed in the marketplace packet's per-listing rule.

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 reporting ad variants separately: 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.

Granularity is how platforms are built to act

Platforms moderate artefacts: this ad, this listing, this app. Their internal cases attach to a single creative ID, so evidence bundled across twelve variants cannot be actioned twelve times — it is actioned once, against whichever variant the reviewer opens. The marketplace channel follows the same logic with listing IDs, and the app-store channel with individual app listings; the packet generator applies per-item filing everywhere it appears.

Per-variant filing also compounds. Each report returns its own case ID, and those IDs become the history that escalates repeat offenders. A variant you skipped is not just an ad still running — it is a missing entry in the pattern that proves the advertiser is a repeat impersonator when the next domain rotates in, which the Google Ads checklist warns is the normal pattern: scam advertisers rotate domains, so the record has to be built variant by variant.

A worked example, end to end

A fictional skincare brand, Alba Botanica-style 'Alba Skin' at albaskin.com, finds one fake profile running five ad variants to alba-skin-shop.com. Instead of one report, the owner files five, each with that variant's screenshot beside the genuine Page and the same destination domain cited. Four variants come down on their own cases; the fifth, initially left standing, is re-filed quoting the four sibling case IDs — and the advertiser's next account is caught by monitoring re-using a variant the case history already documents.

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.

  1. Screenshot every variant separately with its destination URL visible
  2. File one report per variant, each with trademark evidence and the lookalike domain
  3. Record each case ID against the same scan and brand case
  4. Re-file any surviving variant citing its sibling case IDs
  5. Watch for rotated domains carrying the same creatives

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

The commonest failure with reporting ad variants separately is treating it as a message instead of a case. A report typed from memory, sent from the wrong account, missing its ticket number within the week — each is a small thing, and together they are why impersonators outlast brands that were right about everything. The artefacts exist to remove memory from the loop: the evidence block is generated, not recalled; the checklist is written for the channel, not improvised; the case holds the IDs, not an inbox thread nobody can find in month two.

There is also a sequencing mistake: acting on the loudest artefact instead of the highest-priority one. A furious customer message about a dormant name feels urgent; a quiet scan result showing a live, certified clone is urgent. The priority score exists to arbitrate exactly that conflict — 90 before 40, live before loud — and the teams that follow it spend their filing hours where the money is actually leaving.

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 reporting ad variants separately stops depending on whoever happens to notice the fake next.

Frequently asked questions

Is one report with all screenshots attached just as good?

No. Meta treats each creative as its own case; a bundled report is actioned as one case, not twelve.

Does the same rule apply outside Meta?

Yes — the marketplace packet lists each listing ID separately, and app reports attach to individual app listings. Per-item filing is the generator's consistent rule.

What connects the variant reports into one story?

The shared evidence block and the case history: same genuine brand, same lookalike domain, and case IDs recorded together.

New domain, same ad creative — new report?

Yes, and cite the earlier case IDs. Rotated domains with recycled creatives are the repeat-offender pattern the history exists to prove.

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