# Amplitude comparison retake

November 10, 2026, Pacific time. Cartos completed the four original questions in a fresh Supastack chat using the existing Amplitude Dashboard API connection. Fresh Global Agent attempts failed at conversation initialization with `FORBIDDEN: Flow is not accessible`. AI Controls showed Agents were on for the organization. The article pairs the fresh Cartos answers with the November 5 Global Agent answers and date both recordings. A fresh native take is still pending.

| Original question | Global Agent, November 5 | Cartos Dashboard API, November 10 |
| --- | --- | --- |
| What share finished? | 26 starters, 5 finishers (19.23%). | 26 starters, 5 finishers (19.2%). |
| What changes if a submission is required? | 26 → 8 → 4. Added channel details and described 18 starters as abandoners. | 26 → 8 → 4. Identified one baseline finisher outside the ordered path. The cause remained open. |
| Did the same finishers onboard? | Zero observed onboarding starts, completed steps, or activations. | Same zero counts. One of five later logged in. |
| What should improve first? | Investigate the signup-to-onboarding redirect and session handoff, then form and channel friction. | Test entry into login or the first setup step and measure later login, onboarding progress, and baseline signup completion. |

The four-question Cartos pass used the Dashboard API default of 30 days. The separate seven-day recheck reproduced 26 → 5, 26 → 8 → 4, 26 → 5 → 1 for later login, and 26 → 5 → 0 for each of onboarding start, onboarding-step completion, and activation. The run included intermediate request repairs before delivering the six successful queries. [Dashboard API funnel settings](https://amplitude.com/docs/apis/analytics/dashboard-rest#funnel-analysis)

## Export API evidence

The original November 5 Cartos run selected Amplitude MCP. Cartos blocked three proposed calls to the separate Export API. In the November 10 Dashboard API retake, the export tool reached Amplitude and found zero rows in both UTC upload-day windows it requested, October 31 and November 1. The underlying synthetic data was uploaded on November 2. A separate probe on `20261102T23` successfully opened a ZIP archive and parsed 25 rows, stopping at the specified cap. It requested no samples and encountered no window errors. [Export API window semantics](https://amplitude.com/docs/apis/analytics/export)

The probe verified export access. The existing sampling tool does not reconstruct a complete same-user sequence. The independent frozen-packet replay found that the excluded finisher’s submission was recorded before signup start. The timing cause remains open.