App widgetsScripts, styles and embedded storefront UI
Shopify third-party monitoring
See what changes across the services your storefront depends on
GO4 External Radar opens representative storefront pages in a controlled browser and keeps a persistent inventory of the external providers and resource groups they load — so new, missing, failed or slow dependencies are easier to investigate.
Your storefront extends beyond Shopify
A page can be healthy while one of its external dependencies is not
Themes, apps, analytics, reviews, chat, marketing and other services can add browser-loaded resources to the storefront. External Radar gives those dependencies their own monitoring layer instead of leaving them hidden inside one network trace.
Shopify storefrontThe page customers open
Analytics & pixelsExternal measurement and marketing resources
Reviews & engagementCustomer-facing third-party components
External servicesCDNs, APIs and provider-hosted assets
External Radar does not assume that every new dependency is bad. It preserves evidence so change, failure and slowdown can be reviewed in context.
Persistent dependency inventory
Keep a history of what representative storefront pages actually load
A browser network panel shows one moment. External Radar builds an inventory over repeated scans, groups external resources into dependencies and keeps page-level history so drift is visible later.
Dependency inventoryObserved provider groups
PERSISTENTProvider groupResourcesSeen on pagesState
Reviews provider64Stable
Analytics provider87Stable
Chat provider35Changed
Recommendations provider52Issue
Ignored dependencies can be excluded from problem counts, while important provider groups can stay visible for investigation.
Change awareness
Know when the dependency picture around a page changes
External Radar records newly observed dependency groups. Optional missing-dependency detection can also flag dependencies that were previously seen on the same URL but are no longer observed in a later scan.
Earlier scanKnown dependency set
reviews.example/widget.jsKNOWN
analytics.example/pixel.jsKNOWN
chat.example/client.jsKNOWN
Latest scanCurrent dependency set
reviews.example/widget.jsKNOWN
analytics.example/pixel.jsKNOWN
cdn.example/new-widget.jsNEW
chat.example/client.jsNOT OBSERVED
“Not observed” is intentionally different from “removed”. A dependency can be absent from one scan for several reasons, which is why missing-dependency detection is optional and uses per-URL history.
Resource health
Separate dependency discovery from failure and slowdown
External Radar keeps the provider map, then applies configurable thresholds to failed external resources and slow resource groups. New-dependency and missing-dependency impact can also be tuned independently.
Latest resource evidenceExternal provider health
recommendations.example/widget.jsExternal resource failed during scan
FAILEDreviews.example/assets.cssAbove configured slow threshold
1.8 sanalytics.example/pixel.jsObserved normally
82 mschat.example/client.jsObserved normally
126 msConfigurable Radar thresholds
Decide which dependency signals affect status
The current product supports separate controls for failed resources, slow groups, newly seen dependencies and optional missing dependencies.
Failed resourcesSet an allowed count and choose the resulting impact level.
Slow resource groupsDefine the duration threshold and how many slow groups are acceptable.
New dependenciesInformation is the safe default, with higher impact available when required.
Missing dependenciesOptional per-URL detection after stable history has been built.
Representative storefront coverage
Build a focused page inventory, then rotate through it over scheduled runs
External Radar can monitor specific pages or maintain automatic coverage from the homepage, existing checks and sitemap-derived inventory. It does not need to reopen every known page on every run.
Coverage inventoryRepresentative page contexts
ROTATING/Homepage
Selected/products/example-productExisting check
Selected/collections/exampleSitemap inventory
Due next/pages/contactSitemap sample
LaterPage selection
Specific or automatic coverage
Specific pages
Provide the exact storefront URLs that should stay in Radar coverage.
Automatic discovery
Build coverage from enabled URL sources and keep it focused on representative layouts.
Scheduled rotation
Limit URLs per run and scan duration so recurring Radar work stays controlled.
Coverage limits and URLs per run are plan-aware, while the service also enforces hard safety limits.
Three browser-side perspectives
External Radar, Browser Lab and JS Agent answer different questions
All three involve browser evidence, but the source and purpose are different. Keeping that distinction clear makes each monitoring layer more useful.
Browser Lab
Investigates a page run with timing, screenshots, JavaScript errors, resource evidence and historical comparisons.
Synthetic page evidencePerformance comparisonScreenshots & resources
External Radar
Builds a persistent map of provider/resource groups across representative pages and watches dependency change and health.
Dependency inventoryNew / missing signalsFailed / slow groups
JS Agent
Receives passive browser-side evidence from actual storefront pageviews that match active JS Agent checks.
Real pageviewsRendered browser stateCustom DOM evidence
From dependency scan to investigation
Keep dependency evidence inside the normal GO4 monitoring lifecycle
A Radar run records page and dependency observations, evaluates configured thresholds and returns findings that can affect check status. Quality incidents remain optional for External Radar checks.
GO4 opens the selected representative page batch in a controlled browser.
External resource groups are stored with provider, page and history context.
New dependencies and optional per-URL missing dependencies are identified.
Failed and slow external resources are compared with configured thresholds.
Findings affect status, while Quality Incident opening remains a check-level choice.
Shopify third-party monitoring questions
What merchants usually want to know about External Radar
External Radar is dependency intelligence from controlled browser scans. It is not a generic uptime checker, security scanner or real-user monitoring agent.
What is Shopify third-party monitoring?
It is monitoring of the external services and browser-loaded resource groups a storefront relies on. GO4 External Radar scans representative pages and keeps dependency history so changes and resource problems are easier to see over time.
What does External Radar monitor?
It records external dependency groups observed by the controlled browser, including provider and page context, request counts, failures, slow groups and newly seen dependencies. Optional missing-dependency detection can compare later scans with history for the same URL.
Does External Radar install code in customer browsers?
No. External Radar uses GO4 controlled browser scans. Passive evidence from real visitor browsers is the role of JS Agent, which is a separate monitoring layer.
Is External Radar the same as Browser Lab?
No. Browser Lab is centered on the evidence around an individual controlled page run and historical performance comparison. External Radar is centered on a persistent dependency inventory across representative page coverage.
Does every new dependency mean there is a problem?
No. New dependency impact defaults safely to Information. A new provider or resource group is evidence of change, not proof of a fault. The impact can be raised when a store has stricter review requirements.
Can GO4 detect a dependency that disappears?
Yes, when optional missing-dependency detection is enabled after useful history exists. The comparison is made per same URL, and the UI should be read as “not observed in this scan” rather than automatic proof that the dependency was permanently removed.
Can External Radar identify the exact Shopify app behind every resource?
Not reliably in every case. GO4 groups dependencies by observed provider and host context. That evidence can help an investigation, but it should not be presented as guaranteed Shopify app attribution for every external request.
Why monitor more than one storefront page?
Different templates can load different dependencies. Product, collection, content and homepage contexts may not use the same widgets or services, so representative page coverage gives a more useful dependency picture than one URL alone.
Make external dependencies visible
Keep a history of the services your storefront relies on
Use External Radar to turn third-party resource drift, failures and slowdown into evidence you can investigate alongside the rest of GO4 monitoring.
Persistent dependency historyRepresentative browser coverageConfigurable change & health signals