OSINT Jet · Website research

Website Analytics ID OSINT: What a Shared Tag Really Connects

Finding the same Google tag identifier on two websites gives you a repeatable technical observation. The ownership question is still open. The useful next step is to establish where the identifier appears, what kind of identifier it is, and which explanations would produce the same match.

This guide turns a copied string into a small, defensible comparison. You can complete it with public page source and a note-taking document. It does not require access to an analytics account or a visitor database.

Identify the identifier before comparing websites

Keep the prefix. GTM- identifies a Google Tag Manager container; it is not the same thing as a G- measurement identifier. Google also uses GT- and AW- tag IDs. Its tag ID definition explains that one Google tag can have several IDs. Different strings therefore do not automatically mean different operators.

A container is a package used to manage tags. A Google tag can send information to configured destinations. Neither is a public list of the people who administer it. If your evidence says only that a particular page contains a container identifier, keep that wording. Do not relabel it as a company account number.

Capture the match in its original surroundings

On an ordinary public page that is appropriate to visit, use your browser’s View Page Source command. Search for a known identifier or a relevant prefix. Google’s Site Kit documentation describes checking source for a Google tag ID. Reading source is different from running code: do not paste snippets into the browser console.

For every candidate, save the full page URL, retrieval time in UTC, exact ID including its prefix, and enough surrounding source to show its role. Make a separate note for the final URL if the page redirected. A source file saved at one time should not silently become evidence of the site’s configuration a month later.

Consent settings, dynamic loading and different page templates can affect what you see. This is why the note needs a page and an observation time, rather than the blanket statement “this domain has no analytics.” If the original URL is suspicious, use the no-click link assessment first; this exercise is not a reason to open an unsafe page.

Build competing explanations before drawing the line

Google’s container planning guidance explicitly allows one container to serve multiple domains in a connected experience. Its cross-domain measurement documentation also describes measurement across domains with the same Google tag. A legitimate shared setup is therefore one explanation for a match.

Other possibilities require investigation: a copied page may retain an old snippet; a developer may have reused configuration; a former relationship may have ended while code remained. These are hypotheses, not findings about a particular business. A match alone cannot choose between them.

Ask which next observation would separate the possibilities. A legal notice naming the operator addresses a different question from another technical marker. A company register may clarify a claimed entity. An archived page can help establish when a snippet was visible, but does not identify who placed it there. Keep those checks attached to the specific question they can answer.

Exercise: two installations and one misleading match

Invented teaching exercise. The domains below use the reserved .example suffix. GTM-DEMO is an illustrative placeholder, not a researched production identifier.

• cedar-workshop.example contains GTM-DEMO in its homepage installation code.
• cedar-events.example contains the same placeholder in its homepage installation code.
• web-lessons.example prints that placeholder inside an article explaining tag installation.

All three pages match a text search. Only the first two supply comparable installation observations. The third belongs in a “mentioned in documentation” category and should not become an ownership connection.

Now suppose the first two sites name different legal operators. Do not delete that conflict because the code matches. The two operators could collaborate, use the same contractor, or have no current relationship. The defensible finding is: “These two captured pages reference the same container placeholder; responsibility for the shared configuration and the relationship between the operators remain unresolved.”

Change one fact: the second site contains the string only inside an HTML comment explaining a removed integration. The finding must change too. You now have a current installation reference on one page and a retained reference on the other, not equivalent installation evidence.

Hand over an observation, an inference and a test

Use a compact record: page and time → exact identifier → surrounding code → competing explanations → next distinguishing source. Label a graph edge “same ID observed in source” rather than “same owner.” If ten pages repeat one template, treat that as one implementation pattern across ten locations, not ten independent confirmations of ownership.

The domain research guide supplies the wider registration and website context. When that context creates a business question, move to company claim verification. An extra identifier lookup is useful only if it could change your conclusion.

For a case involving several brands and conflicting operator claims, send OSINT Jet’s manual research request the comparison record and the precise relationship you need assessed. Ask for a scoped review of the public evidence; a tag match is not a reason to purchase an identity verdict. The request starts a scope and price discussion, and does not promise a completed investigation for free.