How to triage a new advertiser without assuming misconduct

A new domain appears beside your brand's ad. The first task is not to decide whether the advertiser has done something wrong. It is to establish what the monitoring result shows, verify who is behind the domain and define the question that still needs an answer. The advertiser may be a competitor, a distributor, an affiliate, an owned regional property or a business your team has not classified.

This playbook is for marketing and channel triage. It does not make a legal finding, decide whether a contract was breached or replace a platform complaint process. A good first note gives the next owner enough context to investigate without having to undo an accusation. Keep the observation, the relationship and the interpretation as separate parts of the record.

1. Preserve the capture before interpreting it

Start with the saved result, not with a new theory. Record the exact query, search engine, country or market, location, language if available, device, operating system if available and the observation time. Preserve the advertiser domain, display URL, headline, description, visible assets and destination URL fields that the capture provides. Note whether the result came from a scheduled check, a fresh check or a manual investigation.

If the result is partial, failed or missing a field, say so. Do not fill a blank with an assumption. A sentence such as 'The domain appeared in the saved mobile check for this query and location at this time' is a useful observation. It does not establish how long the campaign ran, which keyword the advertiser purchased, its bid, its account owner or its intent.

If you revisit the destination later, save that as a new observation or a clearly dated review note. A live page can change after the ad was captured. Keep the original ad copy and URL alongside any later page content so a future reviewer can tell what was seen at each point in time.

2. Verify the domain and advertiser identity

Check the domain against the brand's own-domain list first. Ask whether it belongs to the main brand, a regional storefront, an acquired business, a support property or another part of the same group. A close spelling is not proof of ownership. Confirm uncertain cases with the person responsible for web properties, and record who confirmed the answer and when.

In Ads Lighthouse, the primary brand domain and configured additional domains, including their subdomains, are treated as owned domains for the monitoring calculations. External advertiser analysis excludes those domains. If you correct the list, record the effective date and explain whether a report includes observations collected before or after that change. A change in classification can otherwise look like an advertiser disappearing.

Then compare the domain with the sources your organization uses for identity: retailer directories, reseller records, affiliate program data, partner portals, invoices or public company information. Treat each source as evidence for a particular question. A company name on a directory may help identify the business, while an affiliate identifier may help connect a URL to a partner record. Neither one, by itself, proves that every ad from the domain is authorized.

3. Classify the relationship, without closing the case

Use a small set of relationship states that your team can explain. Ads Lighthouse supports unclassified, competitor, authorized retailer and affiliate labels. These labels describe what the team currently knows about the advertiser. They are not findings about the wording of a particular ad, and they do not prove that the advertiser complied with every agreement.

• Use unclassified when identity or relationship evidence is incomplete. Assign an owner and a date for the next check instead of guessing.

• Use competitor when the business is identified as a competing advertiser under your internal definition. Keep the source of that identification in the note.

• Use authorized retailer when the relevant team has confirmed a reseller or retail relationship. Record the market, product scope and dates if the authorization has limits.

• Use affiliate when the domain or identifier is connected to an affiliate record. A tracking marker can support a follow-up, but it is not confirmation of an affiliate agreement by itself.

When nobody can establish the relationship, leave it unclassified. That is a useful result because it names the missing information. Do not label a domain as a competitor merely to make a queue look complete. If a colleague later supplies an authorization or corrects the identity, update the relationship label while preserving the original observation.

4. Inspect the ad copy and destination separately

Review four things in order: the ad's wording, the display URL, the destination and the offer presented there. Quote the exact phrase that raised the question. State whether the concern is about a brand name, a comparison, an implied partnership, a price, a product description, a redirect or something else. Avoid summaries such as 'looks deceptive' when the record can say which words or page elements need checking.

The destination deserves its own note. Does it identify the advertiser? Does it explain a reseller or partner relationship where that matters? Does it offer the product or service described in the ad? Is the page reachable, and does the final URL differ from the captured URL after redirects? These are review questions, not automatic conclusions. A landing page that changed after the capture should be marked as a later observation.

If the case concerns your own Google Ads account, Google's current Ad Preview and Diagnosis guidance explains how to inspect an ad with settings such as keyword, location and device. Google recommends this tool instead of repeatedly searching Google.com for your own ad because repeated searches can accumulate impressions and affect performance data. That guidance helps validate an owned campaign; it does not identify the keyword, bid or intent behind an unrelated advertiser's observed ad.

For a third-party observation, keep the Ads Lighthouse capture as the evidence of what appeared in the configured search. If you perform a separate manual search, record it as a separate check with its own time and settings. Do not merge two results just because the domain is the same.

5. Separate platform policy, contract and legal questions

These questions often overlap, but they have different owners and standards of proof. Put them in separate fields or paragraphs in the review note.

Google's trademark policy is a useful example of why the separation matters. The policy says Google does not restrict trademarks used as keywords, and it describes circumstances involving resellers, compatible products and informational sites. It also identifies direct-competitor use in an ad and confusing, deceptive or misleading use as situations Google may restrict. Apply the current policy to the actual ad and landing page. An appearance on a brand query is not, by itself, a trademark-policy finding.

A platform policy question is not the same as a contract question. Your affiliate agreement may prohibit activity that a platform permits, or allow activity that still deserves a review of its wording. A legal question may depend on facts and law that marketing has not assessed. Keep the source and owner visible for each conclusion, and use words such as observed, confirmed, reported, requires review and unresolved when they match the evidence.

6. Assess recurrence without overstating coverage

One appearance tells you that the ad was observed under one set of conditions. It does not tell you that the advertiser appeared continuously, served every market or used the same copy elsewhere. To assess recurrence, define the denominator before counting: for example, the number of successful checks for one query, location, device and date window.

Keep those dimensions stable when comparing observations. If the query, engine, market or device changes, describe the result as a different slice of evidence. A fictional example makes the point: if a domain appears in 4 of 10 successful mobile checks for one query in Madrid during a defined week, report 4 appearances out of 10 successful checks. Do not rewrite that as 'the domain appeared 40% of the time everywhere.' The arithmetic is illustrative, not a result from a customer account.

Distinguish no ad observed from a failed or incomplete check. A failed request cannot be the denominator for recurrence, and an empty result may have a different meaning from a provider error. Ads Lighthouse keeps the search, place, device and time together in each observation so the reviewer can make that distinction. The monitoring record can support a follow-up schedule; it cannot prove activity between observations.

7. Assign an owner and define the escalation

A review becomes operational when one person owns the next action. Assign the case to the person who can answer the open question, not necessarily the person who first noticed the ad. Give the owner a due date and a clear reopen condition, such as a new appearance after a partner confirms that the previous campaign should have ended.

• Close the review when the available identity and relationship context explains the appearance and no policy, contract or legal question remains.

• Request clarification from the relationship owner when authorization, market scope, affiliate identity or effective dates are uncertain.

• Schedule more observations when recurrence, location or device differences matter. Preserve each check instead of overwriting the first one.

• Escalate a defined policy question to the authorized policy owner, and a potential legal issue to the approved legal reviewer, before taking an external action that requires their judgment.

• Record any external contact only through the process your organization has approved. Do not promise a takedown, complaint or campaign change from an analyst's initial observation.

A review note another person can use

Use a consistent note structure so the next reviewer can read the case without a call. Start with the observation, then add identity, relationship, behavior, recurrence and next action. A compact record can follow this order:

• Observed: what appeared, for which query, engine, market, location, device and time, with links or capture identifiers.

• Identity: what the domain appears to represent, the source for that view and any unresolved mismatch between business name and domain.

• Relationship: the current label, the confirming record and any limits on market, product, query or date.

• Behavior: the exact copy or destination element that needs review, without a legal label standing in for evidence.

• Recurrence: the checks included, the denominator used and whether any checks failed or were incomplete.

• Decision: the owner, due date, next action, source of the decision and the condition that would reopen the case.

A disciplined triage note can say, 'Observed in one saved mobile check; advertiser relationship unclassified; ad uses the brand term in the headline; destination requires review; channel owner assigned to confirm authorization in this market.' That is more useful than calling the advertiser a violator before the missing facts are checked.

Ads Lighthouse supports the evidence-gathering part of this workflow: configured searches, saved observations, advertiser domains, ad copy and destination details, plus manual relationship labels for competitors, authorized retailers, affiliates and unclassified domains. Those labels remain separate from the observation and from any alert or escalation decision. See the product overview for the current monitoring workflow, and use your organization's approved policy and legal process for decisions beyond it.