You post a giving appeal on Instagram, people tap the link, and donations don’t come in. Your page analytics show plenty of visits. A few donors email to say the form “just spins” or kicks them back to the start. Open the same link in Safari or Chrome and everything works fine.
That pattern almost always points to the in-app browser. Facebook, Instagram, LinkedIn, TikTok, and many email and messaging apps don’t hand links off to the phone’s real browser. They open them inside their own built-in browser, called a WebView. WebViews are stripped-down and often stricter about cookies, pop-ups, and embedded frames. Those are exactly the things a hosted donation form tends to rely on.
Why donation forms break inside social apps
You can’t see Altru’s web form code, so you can’t know the exact cause on any given device. These are the usual suspects when a payment form works in a normal browser and fails in a WebView:
- Embedded frames and third-party cookies. If the form sits on your website inside a frame served from another domain, the in-app browser may block the cookies that frame needs to keep the session alive. The donor fills out step one, and step two loses everything.
- Payment fields in a separate frame. Card entry is usually isolated for security. Some WebViews handle a frame inside a frame poorly, so the card fields never load or never submit.
- Pop-ups and new windows. Anything that opens a new tab or window, like a verification step or a “complete your gift” page, may simply not open.
- No saved cards or wallets. Autofill and Apple Pay or Google Pay are often missing in WebViews. That doesn’t cause an error, but more donors give up partway through.
Whether any of these applies to your particular Altru donation form depends on how it’s embedded and on the app and phone version. The only reliable way to find out is to test it.
Reproduce it before you change anything
- Post the exact donation link to a private or test account on each platform you actually use: Instagram story or bio link, a Facebook post, LinkedIn, and your email platform’s app if you send appeals by email.
- Open it on both an iPhone and an Android phone. WebViews behave differently on each.
- Make a real small gift, or get as far as you can. Write down where it fails: the form doesn’t load, it won’t advance, card fields are blank, or it errors on submit.
- Repeat with the link opened in Safari or Chrome so you have a working baseline.
- Check Altru afterward to see whether the test gifts actually came through as revenue. Delete or reverse them according to your normal process.
Keep notes on the device, app, and failure point. If you end up contacting Blackbaud support, that detail is what gets you past the generic “clear your cache” reply.
Fixes you can make today
Link to the form directly, not to a page that embeds it
If your social links point to a page on your website that wraps the Altru form in a frame, try linking straight to the form’s own hosted page instead. Removing the frame often removes the cookie problem. Your page design suffers a bit, but a plainer page that works is better than a branded one that fails.
Tell people to open it in their browser
Put a short line at the top of your donate page: “Having trouble? Tap the menu and choose Open in browser.” Both Instagram and Facebook offer that option in their in-app browser menu, but most people don’t know it’s there. If your website team can detect in-app browsers (most of these apps identify themselves to the website when they load a page), you can show the message only to those visitors.
Make the email and social path shorter
Every extra redirect, like a link shortener, a link-in-bio page, then your site, then the form, is another place for a WebView to drop the session. Point campaign links as close to the form as you can, and keep your tracking parameters on that single final link.
Give donors a fallback
For a big campaign, add a second path on the same page: a phone number, a text-to-give option if you have one, or “email us and we’ll send a payment link.” You will recover some gifts that would otherwise be lost.
When it’s on Altru’s side
If the form fails even when you link to it directly, and it fails in the in-app browsers but works in Safari and Chrome on the same phone, you’ve done everything you can from your end. Open a case with Blackbaud support and include your test notes: device, operating system version, app, the exact link, and the step where it broke. Ask directly whether the hosted donation form is supported in in-app browsers. If it isn’t, you need that answer in writing before you plan your next social campaign around it.
Where Social Good fits
Some organizations get past this by using a different front end for giving. Our Checkouts product is a branded, mobile-friendly checkout that replaces Altru web forms for donations, tickets, and memberships. It supports Apple Pay and Google Pay where the browser allows them, and gifts write back to Altru. Whatever form you use, run the same in-app browser tests above before a campaign launches.
Quick answers
Why does the form work when I test it but not for donors?
You’re probably testing in a regular browser on a computer. Donors arriving from social media are on a phone, inside the app’s built-in browser. Test the way they arrive.
Can I force Instagram or Facebook to open links in Safari or Chrome?
Not reliably from your side. The apps decide how links open. A clear “open in browser” prompt is the dependable workaround.
Does this affect ticket and membership forms too?
It can. The same WebView limits apply to any embedded payment form, so include your ticketing and membership links in the same round of testing.
