Analytics Detection
developer/v1/domain/analyticsDiscovers analytics, tracking, error-monitoring, feature-flag, and consent-management tools on a website. Goes beyond marketing pixels — also detects production developer-tooling SDKs (Sentry, Datadog RUM, Rollbar, LogRocket, New Relic, Bugsnag), feature-flag platforms (LaunchDarkly, Statsig, GrowthBook, Optimizely, Split.io, ConfigCat, Unleash), and CMPs (OneTrust, Cookiebot, CookieYes, Iubenda, Termly, Osano, TrustArc).
What It Does
Scans HTML source, inline scripts, and script source URLs for analytics scripts, tracking pixels, marketing tags, error-monitoring SDKs, feature-flag SDKs, and consent-management platforms. Each detection is tagged with a sub-category (analytics, tag-manager, conversion-pixel, session-replay, heatmap, chat, error-monitoring, feature-flag, cmp). Extracts ALL matching tool IDs (catches GA UA+G dual-config during migrations) and surfaces consent-mode-deferred GTM via dataLayer initialization patterns.
Why It's Useful
A full inventory of the modern dev + marketing + privacy stack in one call. Privacy officers get the consent layer + every tracker for GDPR/CCPA documentation. Dev-tool sales teams see whether prospects already use a competitor (Sentry vs Datadog, LaunchDarkly vs Statsig). MarTech audits catch dual-tracking-ID migrations that single-ID detectors silently hide.
Use Cases
MarTech Audit
Audit analytics implementations to ensure all tracking is properly deployed and no duplicates exist.
Ensure data quality by identifying tracking gaps or duplicates.
Privacy Compliance
Identify all tracking technologies for privacy policy documentation and consent management.
Maintain GDPR/CCPA compliance with complete tracking inventory.
Competitive Intelligence
Analyze competitor analytics stacks to understand their measurement approach.
Identify analytics tools to consider for your own stack.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | Required | The domain to detect analytics forExample: example.com |
Response Fields
| Field | Type | Description |
|---|---|---|
domain | string | The queried domain |
analytics | array | Detected tools, each with name, category (analytics | tag-manager | conversion-pixel | session-replay | heatmap | chat | error-monitoring | feature-flag | cmp), confidence, evidence, toolId (first ID, backward-compat), and toolIds (all extracted IDs — important for dual-config migrations) |
count | number | Total number of tools detected across all categories |
byCategory | object | Tools grouped by sub-category (e.g., { "analytics": ["Google Analytics"], "error-monitoring": ["Sentry"], "cmp": ["OneTrust"] }) — convenience accessor for dashboards and MCP consumers |
Code Examples
curl "https://api.edgedns.dev/v1/domain/analytics" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "domain=example.com"const response = await fetch(
'https://api.edgedns.dev/v1/domain/analytics?domain=example.com',
{
headers: {
'Authorization': 'Bearer YOUR_API_KEY'
}
}
);
const data = await response.json();
console.log(data);import requests
response = requests.get(
'https://api.edgedns.dev/v1/domain/analytics',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
'domain': 'example.com'
}
)
data = response.json()
print(data)Read the full Analytics Detection guide
Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.
Read the guide →Related Endpoints
External References
Learn more about the standards and protocols behind this endpoint.
Try This Endpoint
Test the Analytics Detection endpoint live in the playground.