✦ squircle
explored the −4pt drop in signup→verified across Amplitude + Databricks.
Read: it's one country, one step — not the whole funnel. 1 move for you.You're clear — Brazil's isolated and Natalie's shipping the fix.
Signup → verified · 7d
61%
−4pts WoW
held ~65%, fell sharply from Jun 15
✦ PROPOSEDexplore · KYC auto-pass
Brazil's KYC auto-pass crashed — Onfido stopped recognizing the new CIN ID
The whole −4pt dip is one cohort. Brazil's signup→verified fell to
44% (−19pts) while every other country held. It breaks at one step —
KYC auto-pass — where Brazil's top reject reason, "ID type not recognized,"
jumped from 6% to 31%. That lines up exactly with
Onfido document-model v4.2 (shipped Jun 15), which dropped the template for Brazil's new
CIN national ID. Real users with valid new IDs are auto-bouncing — ≈312 this week.
20 Brazil reject records from Databricks · 8s
✦ NEXTfollow-up · ship the fix
✓Confirmed — 18 of 20 sampled Brazil reject records cite the new CIN card, all auto-rejected "ID type not recognized." Hypothesis holds. (Reason codes only — no document images.)
Send Natalie the fix: route new-CIN docs to manual review
Until Onfido re-adds the CIN template, the safe fix is to route docs that fail only on "type not recognized" to the
manual queue instead of auto-rejecting. squircle drafted the ask to Natalie (growth eng),
cc'ing Priya-C for the compliance sign-off, and a one-line ticket:
“Brazil auto-pass −19pts = Onfido v4.2 dropped the new CIN template (confirmed, 18/20 sample). Route ‘type not recognized’ → manual review for BR until the template’s back. Compliance ok per KYC playbook §4. Est. recovers ~312/wk.”
Slack #kyc-ops · Jira KYC-2231
✓
Cause isolated — and handed off
Natalie's on the fix · ticket KYC-2231 filed · Priya-C cc'd
✦ GET AHEADproactive · recover the cohort
One move to get ahead: 312 Brazil users were wrongly bounced this week and haven't retried. Once Natalie's fix lands,
squircle can re-verify their docs and send a one-tap "you're verified — finish funding" nudge. Want it queued to fire on deploy?
✓ Queued — squircle will re-verify the 312 and nudge them the moment KYC-2231 deploys.
That's everything — the funnel's back in your court when the fix lands.
What squircle looked at
funnel + cohort breakdown
Funnel ·
the break
Breakdown byCountry ▾tap a row to see its funnel
Every other cohort is flat WoW — the dashboard moved, but the cause is contained to one country and one step.
squircle drilled here so you didn't have to slice it by hand.
Cohort drill-downs use only aggregate counts — no individual KYC documents are shown here.