A fallback destination is a safety URL that catches users when your QR code's redirection flow breaks due to disconnected steps, missing conditions, or severed connectors between destinations.
Think of a fallback destination as your safety net. When someone scans your QR code but something breaks in the redirection flow, this is where they land instead of hitting a dead end.
A fallback destination kicks in when the connection between your QR code scan and the final redirect gets severed. Maybe you set up conditions that don't lead anywhere. Perhaps connectors between steps got disconnected. Whatever the cause, the fallback destination ensures your users don't end up staring at an error page.
We built this feature because broken links frustrate users and hurt your brand. You've invested time creating a smart QR code flow with conditions, routing logic, and multiple paths. But systems break. People make mistakes during setup. Conditions change. When any of these happen, you need a backup plan.
Without a fallback destination, users who scan your QR code might see nothing. Or worse, they might see a generic error message that makes your brand look unprofessional. The fallback destination prevents this by giving you complete control over what happens when things go wrong.
Your fallback destination will catch users in several situations:
Condition chains that lead nowhere: You've set up conditions based on user attributes or behavior, but some combinations don't have a defined endpoint. Instead of leaving users hanging, they hit your fallback.
Broken connectors: During editing, you might accidentally remove a connector between steps. The fallback catches anyone who would have followed that path.
Missing destinations: Perhaps you deleted a destination page that was still referenced in your flow. The fallback steps in.
Logic errors: Sometimes the conditional logic itself contains errors that prevent proper evaluation. Rather than failing completely, the system redirects to your fallback.
Setting up a fallback destination is straightforward. You simply specify a URL where users should land when the normal flow breaks down. This could be:
The key is choosing something that maintains a good user experience even when things haven't gone according to plan.
Always define a fallback: Never leave this empty. Even if you're confident in your flow, unexpected issues can arise.
Choose relevant destinations: Your fallback should make sense in context. If you're running a marketing campaign, send users to a general campaign page rather than your corporate homepage.
Monitor fallback usage: If many users are hitting your fallback destination, something's wrong with your main flow. Use this as a diagnostic tool.
Test your flows thoroughly: Before launching, test every possible path through your QR code flow. This reduces the chances users will need the fallback at all.
Behind the scenes, Linkbreakers validates your entire flow before anyone scans the QR code. When a scan happens, the system follows the logic you've defined. If at any point the system can't determine the next step, it immediately redirects to your fallback destination.
This validation happens in real-time, so even if you edit your flow while it's live, the fallback protection remains active. You can update your fallback destination at any time without affecting existing QR codes in the wild.
Q: Does using a fallback destination affect my analytics?
A: Yes, but in a good way. We track when users hit the fallback destination, which gives you visibility into flow problems. You'll see these as separate events in your analytics dashboard.
Q: Can I have different fallback destinations for different QR codes?
A: Absolutely. Each QR code flow can have its own unique fallback destination. This lets you customize the experience based on campaign, audience, or any other factor.
Q: What happens if I don't set a fallback destination?
A: We'll use a default Linkbreakers error page. However, we strongly recommend setting your own fallback to maintain brand consistency and provide a better user experience.
Q: Can the fallback destination be another Linkbreakers flow?
A: Technically yes, but we don't recommend it. If that secondary flow also has issues, users could end up in a loop. It's better to use a simple, reliable destination like a static page.
Q: How do I know if users are hitting my fallback destination?
A: Check your analytics dashboard. We log every fallback activation along with the reason it was triggered. This helps you diagnose and fix flow issues quickly.
Q: Can I use the fallback destination for A/B testing?
A: That's not what it's designed for. Fallback destinations exist to catch errors, not to split traffic intentionally. Use our conditional routing features for A/B testing instead.
Q: Will my QR code still work if the fallback destination goes down?
A: If both your primary destinations and fallback are unreachable, users will see a connectivity error. Always use reliable hosting for your fallback destinations.
Q: How quickly does the fallback redirect happen?
A: Instantly. When the system detects a broken flow, it redirects to the fallback without any noticeable delay to the user.
Q: Can I customize the fallback behavior based on how the flow broke?
A: Currently, no. The same fallback destination is used regardless of what caused the flow to break. We're considering more granular fallback options for future releases.
Q: Should my fallback destination explain what went wrong?
A: It depends on your audience. For technical users, an explanation might be helpful. For general consumers, a simple redirect to relevant content works better than confusing error messages.
