Attribution arguments in embedded finance are usually a missing query string. Someone used UTM_campaign and assumed it was the partner code. Someone wrapped the URL. Someone opened Chrome Custom Tabs and the parameter vanished. Then partnerships asked engineering for “the funding API logs.” There are no public lending API logs. There is your unique partner link and a dashboard.
Loanable embedded solutions depend on that ref. Loanable is not a lender. 150+ lenders get the matched file. 50/50 of Loanable profit, Monday ACH, no minimum, if the funded application still carries your partner identity. Treat the ref like a payment credential. You would not strip a Stripe key in a redirect. Do not strip this either.
Ref is not UTM
Marketing UTMs tell you about campaigns. Partner ref tells Loanable which partner owns the application. You can have both if you are careful. You cannot replace ref with utm_source=partner and hope. Test the production URL, not the Figma prototype. Test logged-in webviews. Test email. Test SMS. Test the help-center button your success team pastes.
- Canonical URL documented in your repo
- Regression test that ref survives navigation
- Separate codes for app versus website if you need to see the difference
- No link shorteners until they are proven to keep query strings
What you will not get from an API key
You will not get a server-to-server offer. You will not get a webhook that says “approved” from a public Loanable lending API. You might wish you did. Ship attribution first. Working capital as soon as 24 hours only matters on files that are actually yours. A $50M facility attributed to nobody is a story you tell in a loss review.
Operations when ref is missing
If the dashboard is empty after a launch, do not start with “lenders are slow.” Start with the network tab on a real device. If applications appear without your code, your marketing site is leaking a clean URL. Fix entry points before you hire more salespeople to “drive funding volume.”
A monitoring check that is not a lending API
Once a day, a job can open your production CTA URL in a headless browser and assert the ref query is present after redirects. That is monitoring. That is not underwriting. When it fails, page the team that owns navigation, not “the capital vendor.” Loanable cannot append a code you stripped.
Alert on dashboard silence after a release, too. If clicks continue and starts drop, you shipped a breaker. 50/50 of profit, Monday ACH, 150+ lenders, as-soon-as-24-hour working capital, $50M facilities — all downstream. The upstream health check is unique partner link still on the live button. Call it attribution monitoring so nobody files it as API latency.
Add the canonical apply URL, with ref, to your integration test suite the same way you test OAuth callbacks. If marketing launches a new landing page, the test should fail until the code is on the button. 50/50 of Loanable profit, Monday ACH, and 150+ lenders are meaningless on an unattributed session. There is still no public REST lending API to “look up” the partner after the fact. unique partner link is the lookup.
Protect the only identifier that pays you. Implement Loanable embedded attribution around unique partner link and stop calling a dropped query string an API outage.