How the Intarsia node diagram works
Every website is a circle.
Many websites are many circles.
Bigger dots have more traffic; smaller dots have less.
Filter to focus on what's important.
Lines are links.
For example, a portfolio might contain some vanity URLs. Those are linked to the sites they point to.
Dots can also be other things.
Yellow dots are Google Analytics properties.
The graph is interactive.
When a site sends data to a GA property, the two are linked together.
The diagram organizes itself based on the forces of nature.
Instead of GA, sites can be linked to their GTM containers.
(GTM nodes are purple.)
And instead of GTM, we can link to other types of nodes - media pixels or campaigns, for example.
Sites, GA, and GTM can all be shown at once.
Note the way that sites organize themselves around a central GTM container and GA Rollup property.
Unowned/unknown GA and GTM nodes are highlighted for further investigation.
How the back end works
Our graphs are built primarily from a combination of two types of datasets:
Site URLs & meta data
Our scraper runs over your list of sites, collecting available IDs for analytics, tag management, consent tools, and media to create a proprietary dataset.
Your site metadata - owners, brands, divisions, countries - is combined for filtering and grouping in our UI.
Analytics data
A subset of aggregated data is scraped from all available Google Analytics properties and Google Tag Manager containers via Google APIs.
No user-level or PII data is collected.
Data is stored in Google BigQuery.
Datasets are
matched and combined to create an enterprise-wide, end-to-end view of site data.
Relationships are found, and the graph is built.
Finally, the results are displayed in a custom interface built on D3.js.
Custom filtering, etc. can be flexibly added to the interface to support your specific needs.
Access to the interface is available by login.
SVG files (without animation) can be exported for wider sharing.