Own domains, subdomains, and retailer sites: a brand monitoring setup guide
Get domain classification right before reading advertiser counts, with a practical checklist for brand sites, local domains, and partner storefronts.
A monitoring report can look wrong even when the ad observation is correct. If the brand's regional store is missing from the own-domain setup, it can appear as an external advertiser. If an independent retailer is entered as an own domain, its appearances can disappear from the external count. Both errors begin with a configuration decision, so build the domain list before interpreting the numbers.
In Ads Lighthouse, each project represents one brand, with an internal project name that can differ from the brand name. A project can include several own domains. Other domains remain external and can carry relationship classifications such as competitor, authorized retailer, affiliate or unclassified. Those categories help the team review what it saw; they do not replace proof of ownership or permission.
Build an ownership inventory
Ask the brand or web team for the sites the company actually operates. Start with the primary site, country domains, local storefronts and any separate domain used in search advertising. Confirm who controls each property and which brand it represents. Include a contact who can answer questions when a new hostname appears.
Record the exact domain or hostname that appears in the ad and the business property it represents.
Identify whether the property is operated by the brand, a subsidiary, an agency or an independent partner.
Note the markets, products and storefronts that the property covers.
Add the owner and confirmation date for every entry, including entries that are still being checked.
Use a fictional brand, Northstar Shoes, as an example. Its internal project might be called Northstar Spain while the brand field remains Northstar Shoes. If the company operates northstar.example and a separate Spanish storefront, both belong in the setup after ownership is confirmed. A local shop selling Northstar products belongs in the retailer register instead.
Choose the domain boundary deliberately
Ads Lighthouse treats a configured own domain and its subdomains as belonging to the brand for monitoring calculations. A store subdomain under a configured parent therefore needs to be understood before the parent is added. Confirm that the parent represents the brand alone, especially when it hosts separate businesses, franchisees or independently operated storefronts.
Review country domains individually. Sharing a brand name does not establish that two domains have the same owner. A domain name that contains the brand is not evidence of ownership either. When the boundary is unclear, leave the domain unclassified and ask the web or brand owner for confirmation instead of changing the configuration to make an inconvenient count disappear.
Keep own domains separate from partner labels
An own-domain entry answers a narrow question: which domain should the project treat as belonging to the monitored brand? An authorized retailer or affiliate label answers a different question about the relationship with an external advertiser. A retailer should remain external even when the brand has approved its advertising. Hiding that retailer as an own domain removes useful context from the report.
Keep the relationship record with the person who manages the partner. Permission to sell products does not necessarily cover every market, product, phrase or promotion. The own-domain list should express confirmed ownership, while the advertiser relationship and review outcome remain visible separately.
Read URL details without overreading them
An ad URL can contain a hostname, path, redirect route and campaign parameters. Google's tracking documentation explains how tracking templates and URL parameters support measurement. Preserve the available URL with the observation, but base the own-domain decision on the confirmed site identity.
A recognizable campaign parameter can help the affiliate or partner manager investigate an observation. It does not prove who owns the destination, who controls a redirect or whether a campaign has permission. When a tracking hostname or unfamiliar route creates ambiguity, record the open question and keep the relationship unclassified until the relevant owner checks it.
Test the setup with real observations
Use a small validation set after the inventory is confirmed. Check the result that each case should produce, and keep the observed query, location, device and time beside the decision.
Review an ad from the brand's primary domain and confirm that it is recognized as the project's own advertiser.
Check a confirmed regional storefront or subdomain when it appears in the captured results.
Verify that an authorized retailer remains external and carries its relationship label.
Leave an unfamiliar domain unclassified and assign a person to resolve its identity.
If a needed example has not appeared, mark the validation as incomplete. Do not run repeated searches simply to force a particular domain into view. A scheduled sample may not contain every domain you expect, and absence from one capture does not settle ownership or establish that a site never advertises.
Document shared properties and changes
For a shared host, ask the web team whether the monitored property represents the brand alone or includes unrelated storefronts. Save the answer with the date and owner. If the product cannot represent the boundary accurately, keep that limitation visible in the reporting notes rather than presenting a precise-looking classification.
Review the setup after a rebrand, domain migration, market launch or change in partner ownership. Changing own domains in Ads Lighthouse affects labels and calculations for future monitoring checks. Previously stored daily metrics are not recalculated, so explain a correction in the next report. Otherwise readers may interpret a change in external counts as a sudden change in advertiser activity.
The product overview describes the project workflow. The maintenance task is to keep the brand owner, web team and monitoring owner working from the same confirmed domain list before the next reporting period begins.