ManyChat Links Dying in the In-App Browser? Fix the Conversion Leak
Your comment-to-DM flow converts, then the link opens Instagram's in-app browser and the sale dies. Here's the two-minute fix — flat $19, unlimited clicks.
⚡ Zippy: your automation already won the hardest part — the DM got opened. Don't lose the click in the last three centimeters.
Comment-to-DM automation is the best-converting link delivery on Instagram right now — ManyChat flows regularly beat link-in-bio on click-through. And then the click lands in Instagram's in-app browser, and the numbers stop making sense: clicks registered, nothing downstream.
If you've typed some version of "ManyChat says they clicked but I got no sales" into a search bar, this page is the answer.
Why your ManyChat clicks don't convert
Every link a ManyChat flow sends opens inside Instagram's webview — not the user's real browser, and not the app your link points at. Three things break, silently:
- The login wall. Your link goes to YouTube, a shop, another social profile — the webview is a browser where nobody's logged in. On Android, users hit a "Continue" interstitial that often fails to open the external browser at all; on iOS they get "download the app" prompts for apps they already have.
- The blind pixel. Webview cookies are sandboxed. The click happens; your pixel, your affiliate tag's attribution, your retargeting audience — none of them see it.
- The checkout choke. No Apple Pay, no autofill, no saved cards. Buyers who already tapped, gone.
Your flow didn't fail. The last three centimeters did.
The two-minute fix (works on any ManyChat plan)
- Make a Zippy link for your destination — paste your URL at app.zipthe.link, get back something like
zipthe.link/yourname. - Paste that into your ManyChat button or message instead of the raw URL.
That's it. When the tap comes from inside Instagram, Zippy detects the webview and springs the real app — YouTube opens YouTube, TikTok opens TikTok, a product link opens where the user is logged in with their payment methods alive. Wrong platform or desktop? It degrades to a normal redirect. Nothing ever breaks.
And because Zippy reports outcomes, not just clicks, Link Pulse shows you what no click counter can: how many of those DM taps actually opened the real app versus died in the webview — per platform, per hour.
The dynamic version (Legend, via the API)
Generating links inside your flows — a unique link per campaign, per broadcast, per subscriber segment — takes one External Request block in ManyChat:
- Method:
POST· URL:https://api.zipthe.link/v1/links - Headers:
Authorization: Bearer zip_…(your API key from the dashboard) ·Content-Type: application/json - Body:
{"url":"{{your destination}}"} - Response mapping: JSONPath
$.shortUrl→ a ManyChat custom field → use that field in your message.
shortUrl comes back as the finished URL on purpose — ManyChat binds one JSONPath per custom field and can't join strings, so there's nothing to assemble on your side.
Every generated link is tracked in the same dashboard, with the same app-open outcomes. API access ships on the Legend plan. Step-by-step, with the body payload and the per-subscriber variant: the ManyChat docs page.
What about the deep-link tools that already plug into ManyChat?
They exist, and the good ones work — that's the honest truth. The difference is the meter:
| Zippy | Per-click tools (e.g. URLgenius) | |
|---|---|---|
| Pricing | $19/mo flat, unlimited clicks | ~$0.01/click after a small free tier |
| 1,900 DM clicks/mo | $19 | ≈ $19 |
| 20,000 DM clicks/mo | $19 | ≈ $200 |
| A reel goes viral | $19 | your bill goes viral too |
| Link lifespan | Never expires — even if you cancel | stops when you stop paying |
| App-open outcome analytics | ✅ per-click opened / webview / broken | click counts only |
Comment-to-DM is a volume game — the whole point of automation is more taps. A per-click meter means your costs scale with your success. Flat $19 means they don't.
FAQ
Why do my ManyChat links open in the wrong browser?
Because Instagram doesn't hand the tap to your phone's browser at all — it opens the URL in its own in-app webview, inside the Instagram app. ManyChat can't change that; it sends the message, and Instagram decides what to do with the link in it. That webview is a browser where you're logged into nothing, Apple Pay doesn't exist, and cookies are sandboxed away from the pixel you're paying for. A Zippy link detects the webview and hands the destination to the real app instead.
Does fixing this require a ManyChat upgrade?
No. Pasting a Zippy link into a flow works on any ManyChat plan — it's a URL in a message, which is a thing every plan can send. Only the dynamic recipe (generating a link per campaign with an External Request block) needs ManyChat Pro on their side and the Legend plan on ours.
Can I tell whether my DM links actually opened the app?
Yes, and it's the number a click counter structurally cannot give you. Each link reports the share of taps that reached the real native app versus the ones that stayed in the browser. Give each flow its own link and that becomes a per-flow answer. The rates are sampled estimates and shown as such — a link nothing has been measured on reports no rate at all rather than a misleading 0%.
Do I have to connect my ManyChat account to Zippy?
No. There's no OAuth, no permissions screen, and Zippy never reads your ManyChat account. The integration is the link itself, plus — if you want it — an outbound HTTP call that you configure inside your own flow.
What happens to links I sent last year if I downgrade?
They keep redirecting. A downgraded workspace goes read-only, never dead — every DM you've already sent still works, and no link Zippy has issued has an expiry date or a click cap.
The short version
- ManyChat gets the DM opened. The in-app browser kills the click. Zippy un-kills it.
- Simple: paste a Zippy link into your flow. Dynamic: one External Request block against the API.
- Flat $19, unlimited clicks, links that outlive your subscription — and analytics that finally tell you whether the app actually opened.
Fix your DM links → app.zipthe.link — free plan, no card, two minutes.
- Docs: ManyChat + Zippy — the paste-a-link recipe, the External Request block, and how to read whether the app actually opened.
- The Zippy API — the
/v1surface the External Request block calls, with keys and rate limits. - Webhooks — get pushed the moment a DM tap opens the app, instead of checking the dashboard.
- A/B split testing — race two destinations in the same flow and compare them on app opens, not clicks.
- MCP server — mint the flow's link by asking your AI assistant instead of opening the dashboard.
- Your n8n workflow can branch on whether the app actually opened — the same events, on an automation canvas.
- Every link tool has an API. This one tells your automation whether the app opened.
- Changelog: ManyChat recipe