How to use scan/rescan conditions?

Route visitors to different destinations based on whether they're scanning your QR code for the first time or returning for a rescan.

Quick summary

• Differentiate between first-time visitors and returning scanners
• Create personalized experiences for new vs. returning users
• Build progressive workflows that evolve with repeated scans
• Combine with other conditions for sophisticated user journeys
• Track visitor behavior across multiple scan sessions

Overview

Scan/rescan conditions let you create different experiences for visitors based on their scan history. First-time visitors can see onboarding content or data collection forms, while returning visitors go straight to the main content or receive personalized updates.

How scan/rescan conditions work

The condition evaluates whether a visitor has previously interacted with your link:

• First scan (Scan): The visitor is new to this link and hasn't scanned it before
• Rescan: The visitor has previously scanned this link and is recognized

Linkbreakers tracks visitors using device fingerprinting and browser sessions, allowing you to identify returning visitors reliably.

Setting up scan/rescan conditions

Step 1: Access your workflow editor

1. Log in to your Linkbreakers dashboard
2. Navigate to QR Codes
3. Create a new QR Code or edit an existing one
4. Open the workflow editor

Step 2: Add the condition

1. Click between existing steps where you want to add the routing logic
2. Select "Scan/Rescan Condition" from the condition types
3. Configure two paths:
   • Scan path: Where first-time visitors should go
   • Rescan path: Where returning visitors should go

Step 3: Connect your paths

1. Create or select the workflow step for first-time visitors (e.g., welcome form)
2. Create or select the workflow step for returning visitors (e.g., direct redirect)
3. Connect each path to its respective step

Common use cases

Onboarding flow with expedited return

Challenge: Collect information from new visitors without annoying return visitors.

Solution: Use scan/rescan condition to bypass forms for known visitors.

Setup:

• Scan path: Route to data collection form
• Rescan path: Route directly to main content
• Result: First-time visitors complete form, returning visitors skip it

Progressive information disclosure

Challenge: Provide introductory content first, then deeper content on return visits.

Solution: Route new visitors to basics, returning visitors to advanced content.

Setup:

• Scan path: "Getting Started" tutorial
• Rescan path: Advanced features or member-exclusive content
• Result: Visitors naturally progress through your content

Event tracking and engagement

Challenge: Measure how many visitors return after initial engagement.

Solution: Different thank you messages or offers for new vs. returning visitors.

Setup:

• Scan path: "Welcome! Here's 10% off your first order"
• Rescan path: "Welcome back! Check out our new arrivals"
• Result: Personalized messages that recognize visitor status

Product registration flow

Challenge: One-time product registration with access to support resources.

Solution: Registration form for new scans, support resources for rescans.

Setup:

• Scan path: Product registration form
• Rescan path: User manual, FAQs, or warranty information
• Result: Efficient flow that adapts to visitor needs

Lead nurturing

Challenge: Capture leads on first visit, then provide value on subsequent visits.

Solution: Gate content initially, then provide free access for registered visitors.

Setup:

• Scan path: Email capture form with content preview
• Rescan path: Full content access without forms
• Result: Build your list while rewarding engaged visitors

Best practices

Make first scans count: Use the first scan to establish value and capture essential information, but don't overwhelm visitors with too many forms.

Reward returning visitors: Show appreciation for repeat scans with expedited experiences, exclusive content, or personalized messages.

Keep rescan paths simple: Returning visitors likely know what they want. Minimize steps between scan and value delivery.

Consider mobile experience: Most QR scans happen on mobile devices. Ensure both paths work flawlessly on smartphones.

Test both paths: Verify that both scan and rescan routes work correctly by testing with different browsers and clearing cookies between tests.

Combine with other conditions: Layer scan/rescan with scheduler or country conditions for even more targeted experiences.

Track conversion metrics: Monitor completion rates for both paths to optimize your funnel.

Advanced patterns

Multi-level progressive profiling

Chain multiple scan/rescan conditions to gradually build visitor profiles:

1. First scan: Collect name and email
2. Second scan: Ask about preferences
3. Third scan: Request detailed feedback
4. Fourth+ scans: Direct access to content

A/B test new content

Use rescan condition to test updated content with returning visitors:

• Scan path: Original content (new visitors)
• Rescan path: Updated content (returning visitors)
• Result: Test improvements with engaged audience first

Membership verification

Create tiered access based on scan history:

• Scan path: Free content with upgrade CTA
• Rescan path: Check for membership status, then route accordingly
• Result: Natural upgrade funnel

Frequently asked questions

How does Linkbreakers identify returning visitors?

Linkbreakers uses device fingerprinting and browser session tracking to identify returning visitors. This works across most scenarios but may reset if visitors clear their browser data or use different devices.

What happens if a visitor scans from a different device?

If a visitor scans your QR code from a different device, they'll be treated as a first-time visitor since the tracking is device-specific. Consider using email or phone capture for cross-device visitor recognition.

Can I have more than two paths based on scan count?

The scan/rescan condition supports two paths (first scan vs. any rescan). For more sophisticated multi-visit flows, chain multiple scan/rescan conditions together.

How long does the system remember a visitor?

Visitor recognition persists as long as their browser session and cookies remain intact. This typically lasts weeks to months unless the visitor clears their browser data.

Can I reset the scan/rescan status for testing?

Clear your browser cookies and cache to reset your visitor status for testing purposes. Alternatively, use different browsers or incognito/private browsing modes.

Does scan/rescan work with password-protected workflows?

Yes! Scan/rescan conditions evaluate before password gates, allowing you to create different experiences even for protected content.

Can I combine scan/rescan with other conditions?

Absolutely! Stack scan/rescan conditions with scheduler conditions and country conditions to create highly personalized, context-aware workflows.

What's the difference between scan/rescan and visitor tracking?

Scan/rescan conditions route workflow paths based on visit history, while visitor tracking provides analytics about all visitor behavior. They complement each other: use scan/rescan for routing and visitor tracking for insights.

Conclusion

Scan/rescan conditions enable you to create adaptive experiences that evolve with your visitors. New visitors get the onboarding they need, while returning visitors enjoy streamlined access. This reduces friction, improves engagement, and creates a more personalized QR code experience.

Ready to create smarter workflows that adapt to visitor behavior? Head to your dashboard and add scan/rescan conditions to your QR codes today.