Debug Mailchimp in Chrome DevTools

What Mailchimp traffic looks like

Mailchimp's on-site footprint has three distinct request families. Telling them apart is most of the debugging work.

Endpoint pattern

Connected-site loader from chimpstatic.com (typically mcjs-connected/js/users/<user-hash>/<script-hash>.js); hosted forms and lists on per-datacenter hosts like mc.us19.list-manage.com, where us19 is the account's datacenter; visitor-event beacons to the Intuit-hosted collector at eventcollector.mcf-prod.a.intuit.com

Transport

Script load for the connected-site loader (installed to enable pop-up forms, retargeting, and site tracking for an audience); form POSTs to the list-manage.com family for classic signup and pop-up subscribe forms; beacon payloads of visitor events to the collector

Key parameters

u audience user hash and id list ID on form calls · mc_cid campaign ID and mc_eid subscriber email ID as landing-page URL parameters. The connected-site script reads them to tie the browsing session to a known subscriber, the mechanism behind click-to-site attribution

Debugging Mailchimp with Event Watcher

• Detects Mailchimp from its request URLs: each script load, form call, and collector beacon appears in the live stream with the platform name and marketing-automation category badge.
• No dedicated Mailchimp parser: requests display their parsed query and body parameters rather than decoded sections. The datacenter host, user hash, and list ID are readable directly in the parameter view.
• Each event gets the cookies section and the consent check.

Mailchimp and consent

The extension checks Mailchimp against the marketing consent category. The connected-site script is the piece to scrutinize: it exists to link on-site behavior to email subscribers, and with mc_eid in the landing URL that link exists before any banner interaction.

A collector beacon firing while the CMP is undecided is flagged pre-consent and feeds the violations counter; a list-manage.com signup submit is its own consent action, but any tracking fired around it still needs the CMP grant.

Common debugging scenarios

• Pop-up form never appears. Confirm the chimpstatic.com loader actually fires; the Script Tree view shows whether it is embedded directly or lost inside a tag manager container that loads conditionally.
• Signup submits but no subscriber appears. Inspect the list-manage.com form call's parameters and verify the u and id values match the intended audience. Wrong-list wiring is common after audience migrations.
• Campaign attribution missing. Land through a real campaign link and check that mc_cid/mc_eid are present in the page URL and that collector traffic follows.
• Pre-consent beacons from email arrivals. Replay the campaign-landing path with the CMP undecided and read the consent badges on the collector events.
• Untangling multiple email tools. Pivot Grouped view by Tool to separate Mailchimp traffic from Klaviyo or HubSpot during a platform migration where both are live.