Opening links from social apps

When someone taps a link inside a social app, the app may open its own browser. That browser can handle websites and app links differently from Safari or Chrome.

What TapBaton does for you

When a visitor opens a website destination from inside an in-app browser (Instagram, TikTok, Telegram and similar), TapBaton tries to open it in their own browser straight away. There is nothing to set up and no mode to choose.

• It worked. The visitor lands on your destination in Safari, Chrome or another browser.
• It did not. After about a second and a half the visitor sees a message with an Open in browser button and a Copy link button. The page follows the phone’s light or dark setting and is written in English, Ukrainian or Russian, whichever the phone asks for; English if it asks for another language.
• A visitor who is not in an in-app browser goes straight to your destination.

An offer card or quiz shown first does the same when the visitor taps its button.

What TapBaton can choose

A Flow can open a website, an app, or a sequence you configure. It can use information available at the time of the visit, such as the source app or device, to choose a Flow. If a signal is unknown, a rule that needs it cannot be treated as a match.

The final handoff also depends on the visitor’s phone, browser settings, the source app, and the destination app. Some visits need a tap or another action from the visitor. No single route is guaranteed to behave the same way in every app and device combination.

Test the full journey

1. Use Test route to check which Flow your draft would choose.
2. Publish the version you want to try.
3. Open the public link from the actual source app on a real phone.
4. Follow the route through to the destination.
5. Check Logs → Clicks for the visit and confirm the destination on the phone.

Repeat for the main apps and phones your audience uses. Record the app, phone, destination, and what happened when a visit behaves differently. Troubleshoot a route.

What a preview can tell you

Test route can explain why a sample visitor matched a Flow. It cannot prove that a browser opened, that an app accepted a link, or that a person completed a later action. Keep those checks separate when you review a campaign.