Definition
A route table is the app's map from each deep link path to the screen that path should open, with whatever item or filter it ought to show, plus the behaviour the app falls back on when the straightforward answer is not available. The deep links and app analytics guide calls routing the other half of deep linking: the operating system's job is to open the app, and the route table's job is to put the person on the right screen once it has.
Marketing gets the table from whoever maintains routing in the app and depends on it, because every link a campaign sends is a row in it whether anyone wrote that row down or not. A readable copy, kept current, lets the people who build links check where each one goes before a message is sent.
What the table must cover
A row for each path and its screen is the easy part. The table earns its keep on the cases where that row is not enough.
- Signed out. The person taps a link while signed out. The intended behaviour is to return them to the promised screen after they sign in, not to strand them on the start screen.
- Missing item. The link points at something that has been removed or has sold out. The table says which sensible alternative the app shows instead.
- Renamed or moved screen. A release changes a screen's name or path. Old paths still in circulation, in sent emails, saved messages and printed codes, need a row that resolves them to the new screen.
- Deferred journeys. A person without the app taps the link, installs through the store and launches it; at that first launch the promised screen ought to appear, and the testing tutorial also checks the designed default for when the destination does not come through.
How the operating system opens the app, the web page people without it see and the verification files behind modern links are link mechanics rather than routing; the deep link entry covers those.
In practice: testing, releases, the app playbook and message checks
The tutorial on testing app deep links begins from the route table, or writes one if none exists, and uses each link's expected screen as the pass condition for a grid that crosses every link with platforms, app states and tap contexts. Its signed-out, missing-item and renamed-screen tests check the table's awkward rows directly, and routing changes go in the measurement change log.
Releases are where tables drift. The routine for checking app events on every release uses one tagged link taken from the table on a freshly reset device as a smoke test and sends the full link test back to the tutorial whenever a release renames screens or changes routing. The app marketing operations playbook lists the route table among the inputs to each release and expects links tested before any campaign points at them. And the mobile message send QA checklist asks for each message's link with its route table entry before anything goes out.
A parking app's renamed screen strands an email campaign
Dernaen Parking, an invented app for booking car park spaces, renamed its booking screen from "book" to "reserve" in a release on a Tuesday. On the Thursday, a monthly email to 48,000 users went out with links to the old path. The email platform recorded 3,900 taps, close to the previous month's 4,100, but bookings from the email fell from 610 to 150, because every tap opened the home screen. A support ticket on the Friday led the team to the cause. It added a row resolving the old path to the new screen, shipped it in a fix 5 days later, and made a route table check part of every release from then on. The next month's email recorded 3,800 taps and 590 bookings.
Related terms
A Deep LinkA link that opens a specific screen inside a mobile app rather than its home screen. is the link itself, the address that asks the app for a particular place; the route table decides which screen that request actually opens. A Push NotificationA message an app sends through the operating system's notification service, shown on the device outside the app to people who allowed notifications. sends people into the app from outside it, and the screen each one promises is only reached if its path has a working row. UTMURL tags identifying traffic source. tags and similar campaign parameters ride along on the link to tell analytics where the tap came from; whether they arrive is a separate check from whether the screen is right. An In-App MessageA message shown inside an app during a session the person started, such as a banner, modal or tooltip, needing no operating-system permission. sends people from one screen to another inside a session, and its calls to action resolve through the same table. The Change LogA dated record of changes made to tracking, accounts, reports, lists or rules, with who made each and why, so later movements in the figures can be traced. is where routing changes are dated, so a later fall in activation can be traced to them.
Common confusions
- It is a redirect map for the website. A website's list of old and new page addresses is a separate thing; the route table lives in the app and maps link paths to screens.
- It is lead routing. Rules that pass enquiries to the right salesperson share the word, not the job.
- It is a network routing table. The term here has nothing to do with how data travels between computers.
- If the app opened, the link worked. The app can open on the wrong screen, and the campaign still records the tap.
- It is written once. Each release that renames or moves a screen can leave old paths with nowhere to go, which is why the guides test it with every release.
