Pro Feature

Initiator Trace

Identify the observed script or page context most likely responsible for a third-party request and place it on the consent timeline.

Finding a pre-consent request is only the first half of debugging. The practical question is what caused it: a tag manager, an inline loader, a marketing SDK, a dynamically injected script, or another vendor dependency.

Initiator Trace correlates captured script activity and request timing to show the most likely observed initiator for each third-party request. This gives developers a direct lead while preserving an honest distinction between browser-observed evidence and a complete JavaScript call stack.

The result is a faster route from compliance finding to code change. Instead of searching an entire tag stack, teams can start with the script URL, vendor and timing evidence most closely associated with the request.

How it works

1

Capture a fresh page load from the ConsentScope DevTools Panel.

2

Select a third-party request in the Requests or Initiators view.

3

Review the correlated script, page context, request type and before-consent timestamp.

4

Use the evidence to adjust CMP blocking rules, tag-manager triggers or application loading order, then rescan.

Key benefits

Trace likely causes

Connect a network finding to the observed script activity closest to it.

Reduce search time

Focus remediation on a likely loader or vendor instead of inspecting every tag.

Preserve timing evidence

See whether the request and its likely initiator appeared before or after consent.

Verify the fix

Reload and compare the trace after changing tag or CMP configuration.

Who is it for

Web developers

Locate scripts and integrations that bypass expected consent gates.

GTM specialists

Investigate tag sequencing and triggers that fire too early.

Compliance teams

Give engineering teams a more actionable finding than a domain name alone.

Frequently asked questions

Is this a full JavaScript call stack?
No. Initiator Trace reports the most likely observed script or page context based on captured browser activity and timing; it does not claim a complete runtime call stack.
Can it identify tag managers?
Yes. Known tag-manager and vendor scripts are labeled when they appear in the captured activity.
Does it work before consent?
Yes. Pre-consent timing is the primary use case, and each trace is shown relative to the detected consent event.

Unlock Initiator Trace with ConsentScope Pro

One-time payment. Lifetime access. All Pro features included. Start auditing cookies, consent banners, and third-party scripts like a privacy professional.

Upgrade to Pro