Skip to main content
PlaidPayments and financing

Your ads count applications. Plaid knows who actually connected a bank.

If your loan or rental application asks people to link a bank through Plaid, the ad platforms usually stop watching at the form. They can't see who quit at the bank step or which applications funded. We wire Plaid Link's callbacks and your funding records into Google Ads and Meta, so bidding learns from connected, approved applicants and no bank data leaves your systems.

Free30 minutesNo obligation

Plaid · what breaks

What goes wrong when Plaid sits in your application

  1. 01

    Google shows lots of applications, but few fund

    Most setups count the form before anyone links a bank. Smart Bidding then chases people who quit at the Plaid step, and every one of them costs you a click that never becomes a loan or a lease.

  2. 02

    I can't tell where people bail

    Plaid Link loads from cdn.plaid.com, outside your page tags, and Plaid notes onExit doesn't fire when someone hits the browser Back button. So you keep funding the campaigns that lose people at the bank login without knowing which ones they are.

  3. 03

    Facebook clicks stall at the bank login

    OAuth banks open in a pop-up or new tab, which in-app browsers like Facebook's often block. Plaid says those users can't finish OAuth without a redirect page you host, so you pay Meta for applicants who physically can't connect.

  4. 04

    I'm scared we're leaking bank data to Meta

    Plaid's onSuccess metadata includes the bank name and account masks. Pushed into a dataLayer, it can reach GA4 or Meta, and Plaid's developer policy bars distributing End User Data without its written permission. That's a vendor relationship your business depends on.

Plaid · the fix

What changes after we fix it — Plaid

  • Bidding learns from connected, funded applicants

    Google Ads and Meta get a signal at the bank connection and another when the loan funds or the lease is approved.

  • The Plaid step visible by campaign

    Opens, connections, exits and errors sit against the ad click, so you see which campaigns bring people who quit at the bank login.

  • Bank data stays home

    Ad platforms get an event name, a timestamp and your lead ID. Bank names, balances and transactions stay with you.

Plaid · architecture

What Plaid actually lets you hook into

We found no Google Ads, GA4 or Meta Pixel integration in Plaid's docs. These hooks are what Plaid documents, and they run through your own code.

  1. 1

    Link callbacks in your page

    onSuccess, onExit and onEvent fire in your JavaScript, each with a link_session_id that holds for the session.

  2. 2

    Stable versus informational events

    Plaid lists OPEN, HANDOFF, EXIT and ERROR among its stable events and marks the rest informational, subject to change and for analytics only, so no conversion hangs on them.

  3. 3

    OAuth redirect URI

    A page you host and allowlist in the Plaid Dashboard that reinitializes Link with the same token. In-app browsers depend on it, and lost sessions and stray tags show up here.

  4. 4

    Webhooks to your server

    ITEM_ADD_RESULT for a new connection, SESSION_FINISHED once Link events are enabled, PRODUCT_READY for an Asset Report.

  5. 5

    Hosted Link for SMS and email

    Runs on Plaid's page, and the completion redirect opens whether the applicant finished or quit, so the webhook decides success.

Plaid · diagnose

Where Plaid tracking breaks, in the order we check

The usual fault isn't a missing tag. It's a conversion counted before the bank step starts.

  1. 01

    Find which event Google Ads and Meta call a conversion

    If it's the form load, every Plaid drop-off counts as a win.

  2. 02

    Run a test application from an ad-tagged URL

    Confirm the click ID is on the lead before Link opens and after the bank login.

  3. 03

    Read the dataLayer during a Plaid session

    Look for bank names, account masks or routing numbers reaching GA4 or the Pixel.

  4. 04

    Test an OAuth bank inside the Facebook app

    Open the ad link in Facebook's in-app browser, finish a bank login, and watch the redirect page for a dead end or a duplicate conversion.

  5. 05

    Compare funded deals with reported conversions

    Per application over a closed month, joined on link_session_id.

Plaid · prove

The QA evidence on a Plaid flow

Run in Plaid's Sandbox first, then on real applications through your live form, desktop and phone.

Source of truth

Your application and funding records joined to Plaid's link_session_id: who connected a bank, submitted, and was approved, funded or signed a lease, by date

  • A Sandbox application from an ad-tagged URL, with the click ID confirmed on the lead.
  • One bank-connect conversion per successful Plaid session, sharing an event ID in Meta Events Manager.
  • An abandoned Plaid session producing no conversion anywhere.
  • An OAuth bank tested from Facebook's in-app browser on a phone, with the redirect page firing nothing extra.
  • A network capture showing no Plaid financial fields reaching GA4, Google Ads or Meta.
  • Funded or approved deals matched record by record across a closed window.
  • Repeated 30 days later and after any change to the application flow.

Plaid · free audit

What we check in the free audit

  • Find which event Google Ads and Meta call a conversion
  • Run a test application from an ad-tagged URL
  • Read the dataLayer during a Plaid session
  • Test an OAuth bank inside the Facebook app
  • Compare funded deals with reported conversions

Checked against

Your application and funding records joined to Plaid's link_session_id: who connected a bank, submitted, and was approved, funded or signed a lease, by date

Get my free conversion tracking audit

Free30 minutesNo obligation

Plaid · when not to buy

When you don't need this on Plaid

Some businesses using Plaid aren't ready for this yet.

  • If applications come from brokers, referrals or a marketplace rather than your own ads, there's no click to tie a funded deal to.
  • If Plaid only appears after approval, say for ACH rent or loan payments, track the approval and leave Plaid out of the ad signal.
  • If you fund only a few deals a month, fixing the bank-connect event alone may be enough.
  • If your developer already posts onSuccess to your server and funded counts match Google Ads, we'll say so on the call.

Plaid · what we deliver

The event map on a Plaid application

  • Application started

    On your own site, with the gclid, fbclid and UTMs stored on the lead before Plaid opens.

  • Bank step opened

    Plaid's OPEN event, kept for funnel reporting, never a bidding conversion.

  • Bank connected

    Plaid's onSuccess, saved with the link_session_id. The qualified-lead conversion, with no account details.

  • Application submitted

    The completed file, after any Income or Assets check your process runs.

  • Approved and funded, or lease signed

    Sent by server from your loan or property system, valued at what the deal earns you.

  • Exits, errors and declines

    Logged with Plaid's exit status for diagnosis, excluded from every bidding signal.

Written guarantee

95%+ tracking accuracy

Measured against Your application and funding records joined to Plaid's link_session_id: who connected a bank, submitted, and was approved, funded or signed a lease, by date. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Plaid questions, answered

No. Plaid requires Link to load straight from cdn.plaid.com, in a frame you don't control. You track it through Link's callbacks on your page and Plaid's webhooks on your server.

Free · 30 min

See which of your ads bring applicants who actually connect a bank

Free30 minutesNo obligation