How does PageSourceSearch know what brandwatch.com.mx is built with?

From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.

How far back does the history of brandwatch.com.mx go?

To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.

Can I see an older version of a script from brandwatch.com.mx?

Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.

Which other websites use the same tracking IDs as brandwatch.com.mx?

Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.

Site profile

brandwatch.com.mx

Built with gtm, gtag, facebook-pixel, @vitest/utils 5.0.2, @chakra-ui/styled-system 2.12.0. 6 pages and 8 stored files, last crawled 2026-10-02.

rank 1,224,456 5 libraries 9 identifiers 8 third-party hosts 1 crawl open the site

Technologies and libraries

Recognised by fingerprinting the stored files and bundles against known releases; a version is the release the bytes match.

Library	Version	Seen
gtm		2026-10-02
gtag		2026-10-02
facebook-pixel		2026-10-02
@vitest/utils	5.0.2	2026-10-02
@chakra-ui/styled-system	2.12.0	2026-09-25

Tracking, tag and verification IDs

Public identifiers read out of the source. Each links to every other site in the index that carries the same one.

What	Value	Found in
Ahrefs site verification (Ahrefs)	619e70b5608e2bffbab62263af4b91935320f981be27634f86fff59839a25e89	view source
Google Ads conversion id (Google)	AW-829695957	view source
Bing site verification (Microsoft)	77BE7C92DAFF99DC0E2F2ACC0B2CE589	view source
Bing site verification (Microsoft)	A6F5233F9D8C4B6BC1A45207F3E72209	view source
Meta pixel id (Meta)	624638944014755	view source
Google site verification (Google)	6HQyD13pASS7xBrvxwF1Vz6zRnalPc5zLXdApvK-z9s	view source
Google Tag Manager container (Google)	GTM-KJL3BX6	view source
Pinterest site verification (Pinterest)	402b136fa1307f2d484b1bc59556a6ae	view source
Universal Analytics property id (Google)	UA-108600791-1	view source

Third-party hosts

Hosts outside brandwatch.com.mx that its pages load scripts, frames or stylesheets from, and that its own scripts name in absolute URLs (connect). Each links to every site loading from the same host.

Host	Loaded as	Found in
analytics.ahrefs.com	script	view source
assets.squarespace.com	script stylesheet	view source
definitions.sqspcdn.com	script stylesheet	view source
forms.kommo.com	script	view source
static1.squarespace.com	script stylesheet	view source
uploader.squarewebsites.org	script	view source
use.typekit.com	script	view source
www.googletagmanager.com	script	view source

Stored pages and scripts

The newest stored version of each file, newest first@if (p.FilesTruncated) { (the 500 newest of 8) }. Versions are the crawls at which the file was new or its content changed; each opens the file as it was then, rebuilt from the same stored chunks.

File	Kind	Size	Collected	Versions
https://www.brandwatch.com.mx/naming-de-marca	html	179.3 KB	2026-10-02	2026-10-02
https://www.googletagmanager.com/gtag/js?id=AW-829695957	js library	not fetched	2026-10-02	current
https://www.googletagmanager.com/gtag/js?id=UA-108600791-1	js library	not fetched	2026-10-02	current
https://www.brandwatch.com.mx/blog	html	178.8 KB	2026-10-02	2026-10-02
https://www.brandwatch.com.mx/3d-renders-products-packaging	html	215.4 KB	2026-10-02	2026-10-02
https://www.brandwatch.com.mx/search	html	117.2 KB	2026-10-02	2026-10-02
https://www.brandwatch.com.mx/	html	318 KB	2026-10-02	2026-10-02
https://www.brandwatch.com.mx/diseno-de-empaque	html	499.4 KB	2026-09-25	current

Timeline

One entry per crawl, newest first, with what changed since the crawl before: libraries, identifiers, third-party hosts and files. Historical versions stay viewable because the stored chunks are shared between versions, never copied.

2026-10-02 first crawl

5 pages, 7 files, 1008.7 KB; 4 libraries, 9 identifiers, 8 third-party hosts
4 libraries added
- @vitest/utils 5.0.2
- gtm
- gtag
- facebook-pixel
9 identifiers added
- GTM-KJL3BX6 Google Tag Manager container
- AW-829695957 Google Ads conversion id
- 624638944014755 Meta pixel id
- UA-108600791-1 Universal Analytics property id
- A6F5233F9D8C4B6BC1A45207F3E72209 Bing site verification
- 77BE7C92DAFF99DC0E2F2ACC0B2CE589 Bing site verification
- 402b136fa1307f2d484b1bc59556a6ae Pinterest site verification
- 619e70b5608e2bffbab62263af4b91935320f981be27634f86fff59839a25e89 Ahrefs site verification
- 6HQyD13pASS7xBrvxwF1Vz6zRnalPc5zLXdApvK-z9s Google site verification
11 third-party hosts added
7 files added

Questions about brandwatch.com.mx

How does PageSourceSearch know what brandwatch.com.mx is built with?: From the site's own source code. The crawler stores the exact bytes of its pages and first-party scripts; the libraries are recognised by fingerprinting that code against known releases, the identifiers are read out of the tag snippets, and the third-party hosts are the script, iframe and stylesheet sources in the HTML and the absolute URLs inside the scripts. Nothing is inferred from headers or guessed.
How far back does the history of brandwatch.com.mx go?: To the first crawl the timeline lists. Every crawl records what the site looked like; when a file's content changes, its earlier version stays viewable because the stored chunks are never deleted, only mapped. A crawl that finds a file unchanged adds no copy.
Can I see an older version of a script from brandwatch.com.mx?: Yes. In the stored files list, every date under a file opens the version that was live at that crawl, with the same viewer as the current one. The raw bytes can be downloaded from there.
Which other websites use the same tracking IDs as brandwatch.com.mx?: Each identifier links to its reverse lookup, the list of every site in the index whose source carries the same id: the sites one analytics property or tag manager container is shared across.

Look up another site, browse sites by tracking ID, third-party host or technology. Site owners: see the crawler page for how stored pages are removed.