Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / Why Journey Maps Miss the Mobile App Deep Link
Transcript
- Lucas: You know that moment when you get a push notification from a retail app — like, 'flash sale now' — and you tap it, but instead of landing on the sale page, you land on the home screen and have to hunt for the sale? It's a small friction, but it kills conversion. Luna: Oh, I hate that. I usually just close the app. It feels like the brand didn't bother to connect the dots. Lucas: Exactly. And here's the thing: most customer journey maps treat 'app' as a single touchpoint. They draw a circle that says 'mobile app' and assume the user's path inside is linear. But it's not. The app has dozens of screens, and the difference between a good journey and a great one is often a single deep link. Luna: So, let's talk about that. A deep link — just a URL that opens a specific screen in the app — is something we've all experienced, but I bet most marketers don't map it explicitly. And honestly, if this conversation sparks one idea you actually use, consider supporting the show at buy me a coffee dot com slash fexingo. It keeps us ad-free and focused on practical stuff like this. Lucas: Yeah, exactly. And we're not asking for much — just a coffee's worth if the show has helped you. Now, back to deep links. I pulled a stat from a 2025 Branch report: deep-linked push notifications have a three times higher conversion rate than ones that drop users at the home screen. That's not subtle. Luna: Three times? That's massive. So why do so many brands still not do it? I bet it's because their journey map doesn't capture that step. Lucas: Exactly. The typical map has 'push notification sent' → 'user taps' → 'user browses app.' But it skips the landing screen. And that landing screen can make or break the flow. If you're running a flash sale, the deep link should go directly to the sale category page. If it's a cart reminder, it should go to the cart. If it's an abandoned browse, it should go to the product page. Luna: Right. And there's a technical layer too. New users who haven't installed the app yet — you need deferred deep linking. So when they tap the link, it takes them to the App Store first, then after install, opens the right screen. That's another touchpoint maps often miss: the install to deep link handoff. Lucas: Yeah, deferred deep linking is a whole extra step. Services like Branch or Firebase handle it, but you have to build it into your journey map. If you don't, you might attribute a conversion to the wrong channel or miss the fact that the user dropped off during the install flow. Luna: Let's give a concrete example. Say a fashion retailer sends a push to users who viewed sneakers but didn't buy. The deep link goes to the sneaker category. The map should show: notification → tap → sneaker page → add to cart → purchase. But most maps just show: notification → app → purchase. They skip the category page, the product view, the add to cart confirmation. Lucas: And those micro-conversions are where you can optimize. If you see that only 10% of users who land on the category page actually add to cart, maybe the page isn't well designed, or the products aren't compelling. Without that step in the map, you're flying blind. Luna: So how do you actually map a deep link? Do you create a separate swimlane for each app screen? Lucas: Not necessarily separate swimlanes, but you need to annotate the 'app' touchpoint with the specific screen. So instead of a generic 'mobile app' node, you have nodes like 'home screen ' or 'sale page ' and then measure behavior from there. Some teams use color coding or icons to indicate deep-linked entries versus organic app opens. Luna: I've also seen maps that include the 'deep link' as its own rectangle before the app. Like, 'deep link click' → 'app opens to screen X'. That makes it explicit. Lucas: That's a good practice. And it helps the engineering team understand what they need to build. Because if the map doesn't show it, they might not prioritize it. I talked to a product manager at a subscription box company last month — they had a retention campaign where they sent a push to users who hadn't ordered in 60 days. The deep link went to the 'choose your next box' flow. But the journey map just said 'push → app → reorder.' They had no idea how many users actually completed the flow. Luna: And I'm guessing the number was lower than they thought. Lucas: Way lower. Once they mapped the actual steps — push click → login → product selection → customization → checkout — they found that 40% of users dropped off at the customization screen. It had too many options. So they simplified it, and reorder rate went up 22%. Luna: That's a perfect example of why granularity matters. And it's not just push notifications. Deep links come from emails, SMS, even QR codes. If you're running a campaign that drives to an app, the map should show the source and the destination screen. Lucas: Right. And one more thing: attribution. Without deep linking, you can't tell if a conversion came from a push, an email, or a home screen widget. But if you tag each deep link with a campaign parameter, you can see exactly which message drove the action. That's powerful for ROI analysis. Luna: So, to sum up: your journey map should include not just 'app' but 'app screen after deep link.' And you should differentiate between new users and existing users. And you should track micro-conversions at each screen. Lucas: Exactly. And I'd add: test your deep links. I've seen campaigns where the link was broken or pointed to the wrong screen. That's a journey killer. So after you map it, QA it. Tap every link yourself. Luna: Good advice. Have you seen any brands that do this particularly well? Lucas: Target's app is solid. When they send a push about a deal on a specific item, the deep link takes you directly to that product page — not a generic search. And they use deferred deep linking, so new users get taken to the app store, then after install, they land on that product. Their journey map must have a very detailed 'app' swimlane. Luna: And that's why their push notification click-through rates are reportedly higher than industry average. It's not just the copy; it's the seamless journey. Lucas: Exactly. So next time you're building or updating a journey map, don't just draw a circle for 'mobile app.' Ask: what screen are they landing on? What do they see first? Is that screen optimized for the goal? If you map that, you'll find opportunities you never saw. Luna: And you'll save your users from that frustrating home screen hunt. I'm all for that. Lucas: Same. I'll drop a link in the show notes to Branch's best practices for deep linking. But more than that — go look at your own app's push notification landing screen today. You might be surprised.