Automated Plaid Link Conversion Reporting
Every Monday, WebRun signs in to the Plaid dashboard, reads the last week of Link sessions, works out conversion rate overall and per institution, groups the Link errors by type and counts the sessions each one cost, posts the funnel to Telegram, and files the ranked fix list in Microsoft Teams.
How do I find where users drop out of the Plaid Link flow?
WebRun watches your Plaid Link funnel every Monday. It reads the last week of Link sessions in the dashboard, calculates conversion overall and per institution, groups errors by how many sessions each one ended, posts the funnel to Telegram, and files a ranked fix list in Microsoft Teams.
- The next fix targets the step actually losing users
- Conversion is broken out per institution, not just an average
- Repeating errors are visible because last week's list carries forward
Built for product owners · fintech teams · growth engineers · onboarding teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
dashboard.plaid.comin a real browser with your saved login - no setup, no API keys. -
1
Plaid - read the Link funnel
plaid.com
WebRun opens Plaid to read the Link funnel. - Sign in to the Plaid dashboard and open the last seven days of Link sessions
- Capture sessions started, sessions completed, and the resulting conversion rate
- Break conversion down by institution and flag the ones well under your average
- Group Link errors by type and count how many sessions each one ended
Done when The week has a conversion rate overall, per institution, and an error count per type.
-
2
Telegram - post the weekly funnel
telegram.org
WebRun opens Telegram to post the weekly funnel. - Post the funnel to the product channel: sessions started, completed, conversion rate
- Show the change against last week so a drop is visible immediately
- Name the three institutions with the weakest conversion
Done when The product channel has this week's Link funnel.
-
3
Microsoft Teams - file the fix list
microsoft.com
WebRun opens Microsoft Teams to file the fix list. - File a ranked fix list in the engineering channel, ordered by sessions lost
- Put the error type, the institutions it hits, and the session count on each line
- Carry forward last week's items so a repeating error is obvious
- Never contact an end user or change a Link configuration: WebRun reports the numbers
Done when Engineering has a fix list ordered by how many sessions each error cost.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it see customer bank credentials?
No. WebRun reads session counts, conversion rates, and error types in your Plaid dashboard. It never sees a bank credential, and it never contacts an end user about a failed connection.
How is this different from watching broken connections?
Broken-connection monitoring covers items that were linked and later failed. This covers connections that never happened: the Link funnel, where users dropped, and which errors ended their session.
Can it change Link settings to fix a problem?
No. It ranks the errors by sessions lost and files them for engineering. Changing your Link configuration or institution coverage stays a deliberate change by your team.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.