🧪 Pardot Helper / Adapter Debugger

parent SDK ↔ in-iframe helper postMessage trace

Controls

Drive the simulated helper to emit events
The iframe below is a real Pardot form at info.datavail.com/l/26092/.... The in-iframe helper.js emits lifecycle postMessages as a user interacts with the form. Buttons here are limited to what the parent SDK is allowed to send across origins — the discovery pings that events.ts → pingIframes() uses (requestFormLoad / Visible / Start). To exercise fs / ffs / ffc / fsu / fvf, interact with the form in the iframe directly.

Lifecycle (interact with the form)

  1. fl – fires automatically on iframe load
  2. fv – scroll the iframe into view
  3. fs – focus any field
  4. ffs / ffc – per-field focus & valid blur/change
  5. fsu – submit a valid form
  6. fvf – submit with empty required fields

Adapter ↔ Helper Discovery (parent → iframe)

Iframe

📡 PostMessage Wire (helper ↔ adapter)

Captured BEFORE the SDK boots — full message bus trace.
msgs 0
iframe[src*="info.datavail.com/l/"] — real Pardot form (?_ll_debug=true)

🎯 SDK / Adapter Effects

Adapter calls onto the SDK queue + outbound /collect calls.
events 0
/collect calls 0 form events 0 queued calls 0