Vendors Tagnovo detects

Every analytics and marketing vendor with a published signature: what identifies its loader, what identifies its collection request, and how it fails.

Published signatures

Version 1 of the signature set. A loader request proves the script was fetched. A collection request proves an event left the page. Shopify Trekkie is a control signal, not merchant analytics — without that distinction every Shopify store would look like it had analytics installed.

Every vendor in signature set version 1
VendorLoaderCollectionRole
GA4googletagmanager.com/gtag/js*.google-analytics.com/g/collectAnalytics
Google Adsgoogleadservices.com/pagead/conversiongoogle.com/pagead/1p-conversionAds
Metaconnect.facebook.net/*/fbevents.js*.facebook.com/trAds
TikTokanalytics.tiktok.com/i18n/pixel/events.jsanalytics.tiktok.com/api/v2/pixelAds
Pinterests.pinimg.com/ct/core.jsct.pinterest.com/v3/Ads
Snapsc-static.net/scevent.min.jstr.snapchat.com/Ads
Klaviyostatic.klaviyo.com/onsite/js/klaviyo.jsa.klaviyo.com/onsite/trackEmail
Microsoft Clarityclarity.ms/tag/*.clarity.ms/collectSession
Hotjarstatic.hotjar.com/c/hotjar-*.hotjar.io/Session
Shopify (Trekkie)cdn.shopify.com/s/trekkiemonorail-edge.shopifysvc.com/Control

Reading a signature

A tag can load and still send nothing. That is the failure this product exists to find, so the two columns are recorded separately. A change to either signature is a new set version and a changelog entry — never an edit — or every historical scan silently changes meaning.