Tool Funnel Event Reconciler

How to use Tool Funnel Event Reconciler

Page views and a successful tool output are different measurements. Reconcile exported attempt records without treating synthetic tests or a declared nontest label as verified visitors.

1. Export minimal authorized event metadata with stable event and attempt IDs and the actual event names.
2. Declare the maximum attempt window, case/tool context and known test classification without guessing missing facts.
3. Resolve duplicate, missing or conflicting stages and separately establish traffic filters and real-user attribution.

Good to know

• A complete chain needs exactly one of each declared stage, consistent nonempty context, chronological ordering and completion within the entered window. Equal timestamps are allowed; unknown event names are findings.
• At most 86,400 seconds per attempt. No analytics account, live collection, cross-device attribution, bot detection, revenue or verified visitor count is provided. Declared nontest is explicitly unverified.
• Each input field is limited to 8,000 UTF-16 characters. CSV needs the exact displayed header and at most 100 data rows. Quoted commas, doubled quotes and quoted newlines are supported. Duplicate identities are refused unless the tool explicitly reports them as findings.
• Markdown and CSV are editable review artifacts, not certificates. Spreadsheet-like text is apostrophe-prefixed in CSV to reduce formula execution risk; check the actual importer before sharing. Decimal ratios are rounded to at most 12 places.
• Runs only on the records you enter, locally in your browser. No AI call, provider connection, account inspection, upload, automatic outreach or saved input. Use neutral identifiers rather than personal or secret content.