Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / How Customer Journey Maps Miss the Mobile App Deep Link Gap
Transcript
- Lucas: You're building a customer journey map. You've got the website funnel mapped beautifully. You've got email, social, paid search. But there's a channel that's probably sitting on your map as a single generic rectangle labeled 'mobile app' — and inside that rectangle, there's a blind spot that's quietly costing you conversions. Luna: The deep link gap. I've seen this one in the wild. It's like when someone sends you a link to a specific page on a website, but instead of taking you there, it drops you on the homepage. Lucas: Exactly. And on mobile, that broken experience happens more often than most marketers realize. Let me give you a concrete example. I was talking to the marketing team at a mid-size home goods retailer — we'll call them HomeNest — who launched a native app last year. They had great download numbers, decent retention, but when they looked at conversion rates from app users versus mobile web, they saw a weird pattern. Luna: What kind of pattern? Lucas: App users who came from email campaigns were converting at thirty percent lower than mobile web users who clicked the same email. Same offer, same product, same creative. The only difference was the destination. Luna: So the email was linking to the app store to open the app, but not deep linking to the specific product page. Lucas: Right. The email links were universal links that opened the app — that part worked — but they didn't carry a deep link parameter, so the app just launched to its default home screen. The user had to search for the product again. Some did. Most bounced. Luna: And that's the gap. Your journey map shows a seamless path from email to app to purchase. But the actual user experience is email to app homepage to frustration to exit. Lucas: If these marketing conversations have sparked something you've actually used in your own work, that's exactly what we hope for. And it's why we keep the show ad-free — no sponsors, no midrolls, just the ideas. If that approach resonates, and you want to help us keep it that way, the link is buy me a coffee dot com slash fexingo. No pressure ever. Now back to the deep link gap. Luna: Yeah, and it's one of those fixes that sounds simple but gets complicated fast. Because deep linking isn't just about one link type. There's basic deep linking, deferred deep linking, contextual deep linking. Lucas: Let's break that down. Basic deep linking means if the app is already installed, a link can take the user to a specific screen. Deferred deep linking handles the case where the app isn't installed — it takes the user to the app store first, then after install, opens the app and navigates to the right screen. Contextual deep linking passes additional data, like which campaign the user came from or a referral code. Luna: And HomeNest wasn't doing any of that. They had a basic 'open app if installed' setup, but nothing for new users, and no parameters passed to the app. Lucas: So they started mapping their customer journey with deep link status as a variable. They looked at every touchpoint that could send a user to the app: email, push notifications, social media links, QR codes in stores, even SMS campaigns. Luna: What they found was that about forty percent of their app traffic came from channels that were only using shallow links — opening the app to the home screen. Lucas: The fix was a phased implementation. Phase one: implement deferred deep linking for all email and push notification links. That alone recovered about twelve percent of the conversion drop within a month. Luna: And phase two? Lucas: Contextual deep linking for social media and referral links. That allowed them to personalize the in-app experience based on where the user came from. If someone clicked a link from an Instagram ad for a specific lamp, the app opened directly to that lamp's product page. If they came from a referral link from a friend, the app showed a welcome message with the referral credit. Luna: That changes the user's entire perception. Instead of 'I have to find that lamp again,' it's 'oh, here it is, and I get a discount.' Lucas: Exactly. And the impact on their journey map was significant. They had to redraw the app path from a single arrow labeled 'app session' into multiple branches: 'app session via email deep link,' 'app session via push deep link,' 'app session via organic direct open.' Each branch had different conversion rates and different friction points. Luna: And I bet the branch that surprised them most was push notifications. Lucas: That's a great point. Push notifications are often treated as a retention tool, not a conversion tool. But if you send a push about a flash sale and the deep link takes the user to the sale landing page, that's a high-intent moment. If it takes them to the home screen, you've just annoyed someone who was ready to buy. Luna: I've seen data that push notification click-through rates can be five to ten times higher when the deep link is correct. Because the user's expectation is set by the message copy. If the message says 'your cart items are on sale' and the link goes to the cart, great. If it goes to the home page, you've broken a promise. Lucas: That promise-breaking is exactly what HomeNest discovered. Their push notification CTR was decent — around four percent — but the conversion rate from those clicks was abysmal. After implementing contextual deep links, the conversion rate from push nearly tripled. Luna: Now, there's a technical hurdle here that marketers don't always anticipate. Deep links require coordination between the marketing team, the product team, and the engineering team. Because the marketing team decides the campaign parameters, but engineering has to build the link infrastructure and handle the routing logic. Lucas: And that's where a lot of journey maps stay broken. The marketing team has a beautiful map of ideal paths, but they don't have the technical implementation to make those paths real. HomeNest solved this by creating a shared document that listed every campaign type, the intended deep link destination, and the fallback behavior if the app wasn't installed. Luna: So basically a deep link spec sheet that both teams agreed on. Lucas: Yes. And they tested it with a small subset of users before rolling out broadly. They used a feature flag to enable deep links for only ten percent of their push notification audience for a week. The results were clear enough that they rolled it out to everyone the following week. Luna: And I imagine they also had to revisit their attribution model, because deep links change how you track conversions. Lucas: That's another layer. When a user comes through a deep link, you can pass campaign parameters through the link and into the app. That means you can attribute the conversion back to the original touchpoint — whether it was an email, a push, or a social post. Without deep linking, an app session that starts on the home screen often gets misattributed to 'organic' or 'direct' even if the user was driven there by a campaign. Luna: So the journey map was showing a lot of organic app conversions, but in reality, those should have been attributed to email or push. Lucas: Exactly. HomeNest found that about twenty percent of what they thought were organic app conversions actually came from a marketing campaign that just landed on the home screen. That misattribution skewed their ROI calculations for those channels. Luna: And when they fixed the deep links, those numbers shifted. Suddenly email looked more valuable, and organic looked less so. Which is fine — it's accurate. Lucas: Right. And it changed their budget allocation. They increased spend on email and push because they now had confidence that those channels were driving actual in-app purchases, not just app opens. Luna: So what's the takeaway for someone listening who has a mobile app and a customer journey map? Where should they start? Lucas: I'd say start by auditing every link that currently sends users to your app. Click each one on a test device. Does it land on the intended screen? If you don't have intended screens defined for each campaign, that's step zero. Define, for each campaign type, what the ideal landing page is. Luna: And check both installed and not-installed scenarios. Because deferred deep linking is where a lot of the value is — capturing users who download the app for the first time from a campaign. Lucas: Absolutely. And then once you have that working, you can start experimenting with contextual parameters. Pass the campaign name, the user ID, maybe a promo code. That opens up personalization opportunities that the journey map can then reflect. Luna: I think the deeper point here is that customer journey maps are only as good as the data feeding them. If your app is a black box that just says 'app session,' you're missing a huge part of the story. Lucas: And the fix — deep linking — is not that hard to implement. It's a few lines of code per platform, a bit of coordination, and then a lot of testing. But the payoff is a journey map that actually reflects reality, not a wish. Luna: So next time you update your map, zoom in on that app rectangle. Make sure it has branches, not just a straight line. The gap might be smaller than you think, but it's almost certainly there. Lucas: And if you find it, you'll probably recover conversions you didn't know you were losing. That's the kind of win that makes the whole exercise worth it.