---
title: "How to retarget QR code visitors who didn't convert"
description: "Use scan/rescan conditions, visitor journeys, and progressive workflows to re-engage QR code visitors who scanned but didn't take action the first time."
canonical: "https://linkbreakers.com/help/article/how-to-retarget-qr-code-visitors-who-didnt-convert"
last-updated: 2026-10-10
---

# How to retarget QR code visitors who didn't convert

> Use scan/rescan conditions, visitor journeys, and progressive workflows to re-engage QR code visitors who scanned but didn't take action the first time.

## Short answer

This article explains how to retarget QR code visitors who didn't convert with practical guidance, limits, and implementation details so you can apply it consistently.

Most visitors who scan your QR code won't convert on the first interaction. Linkbreakers lets you detect returning visitors and route them through a different experience — so your QR code keeps working long after the first scan.

## Quick summary

- **Detect returning visitors** automatically using scan/rescan conditions
- **Show a different message** to second-time or third-time visitors without reprinting
- **Read each visit's journey** across multiple scans to see who stopped early and who reached the end
- **Combine conditions** to personalize by both scan history and location or time
- **Track drop-off points** per visit to know where to improve the journey

:::try-ai-prompt {"prompt":"Add a scan/rescan condition. First-time visitors see a form collecting email with a special offer message. Returning visitors skip the form and go straight to the redirect.","description":"Try building a retargeting workflow that treats new and returning visitors differently."}:::

## Why first-time scans rarely convert

QR codes in physical environments (packaging, posters, signage, print ads) reach people who are browsing, not buying. Research consistently shows that most offline touchpoints require multiple exposures before a visitor takes action.

| Visit | Typical behavior | What you want to show |
|---|---|---|
| First scan | Exploring, low intent | Welcome message, brand intro, low-friction offer |
| Second scan | Recalling your brand, higher intent | Specific product, testimonial, time-limited offer |
| Third+ scan | Actively considering | Direct CTA, discount, simplified checkout |

Without retargeting logic, every scan shows the same experience — which means returning visitors see a message designed for strangers.

## How scan/rescan detection works in Linkbreakers

Linkbreakers identifies devices using a fingerprint built from browser, OS, screen, and network signals. When a visitor scans the same QR code again, the [scan/rescan condition](https://linkbreakers.com/help/article/how-to-use-scan-rescan-conditions) detects whether this is a new or returning device and routes them accordingly.

```mermaid
flowchart LR
    A[Scan] --> B{First visit?}
    B -->|Yes| C[Welcome journey]
    B -->|No| D[Re-engagement journey]
    C --> E[Brand intro + opt-in form]
    D --> F[Follow-up offer + direct CTA]
```

| Condition result | Meaning | Suggested action |
|---|---|---|
| First scan | New device, never visited this link | Run full onboarding journey |
| Rescan | Returning device, scanned before | Skip intro, go straight to offer |

## Building a retargeting workflow step by step

### Step 1: Define your two journeys

Before opening the workflow editor, write out what each type of visitor should experience:

| Journey | Audience | Goal | Steps |
|---|---|---|---|
| First-visit | New scanner | Introduce brand, capture email | Form → brand content |
| Return-visit | Returning scanner | Drive conversion | Offer → product page |

### Step 2: Create your workflow

1. Go to [QR Codes](https://app.linkbreakers.com/workspace/dashboard/links) in your dashboard
2. Open or create a QR code, then open the workflow editor
3. Add a **scan/rescan condition** as the first step after the scan entry point
4. Connect the **first scan** branch to your welcome journey (form + brand page)
5. Connect the **rescan** branch to your re-engagement journey (direct offer or CTA)
6. Set a fallback destination in case the condition can't be evaluated

### Step 3: Add progressive data collection

For the first-visit branch, include a [form step](https://linkbreakers.com/help/article/how-to-create-a-form) to collect the visitor's email. For the rescan branch, enable **auto-skip if known** on the form — visitors who already submitted won't be asked again.

```mermaid
flowchart LR
    A[Scan] --> B{Scan/rescan?}
    B -->|First| C[Form - email + name]
    B -->|Rescan| D[Skip form auto]
    C --> E[Thank you + content]
    D --> F[Personalized offer]
```

## Combining retargeting with other conditions

Scan/rescan detection becomes more powerful when chained with other conditions.

### Retargeting by location

Show returning visitors a geo-specific offer:

```mermaid
flowchart LR
    A[Scan] --> B{Rescan?}
    B -->|First| C[Generic welcome]
    B -->|Rescan| D{Country?}
    D -->|US| E[US-specific offer]
    D -->|EU| F[EU-specific offer]
    D -->|Other| G[Global offer]
```

### Retargeting by time window

Pair scan history with time-of-day routing to catch returning visitors at the right moment:

| Condition chain | Behavior |
|---|---|
| Rescan + morning | Show breakfast offer |
| Rescan + evening | Show dinner or end-of-day CTA |
| First scan + any time | Always show welcome |

See [how to use scheduler conditions](https://linkbreakers.com/help/article/how-to-use-scheduler-conditions) for the time-based routing setup.

## Using the journey to prioritize returning visitors

Every visit records a [journey](https://linkbreakers.com/help/article/what-is-a-visitor-journey): how many workflow steps the visitor reached, how many were on their path, and whether they reached the end. A returning visitor whose last visit stopped partway is a clear retargeting candidate.

| Last journey | Interpretation | Recommended action |
|---|---|---|
| No steps reached | Casual scan | Nurture with content, no hard sell |
| Stopped partway (e.g. step 2 of 5) | Interested, dropped off | Shorten or simplify the step they stopped at, show social proof |
| Reached the end | Went through every step you set | Direct CTA, discount, sales contact |

The journey appears in the Live view, in CSV exports (`journey_completed`, `journey_progress`), and in webhooks, so you can follow up on visitors who stopped early through your CRM or email tool.

## Tracking retargeting performance

Each branch of your workflow generates separate [events](https://linkbreakers.com/help/article/what-is-an-event-in-linkbreakers), so you can measure first-visit vs. return-visit behavior independently.

| Metric | Where to find it | What it tells you |
|---|---|---|
| Rescan rate | Link analytics | How many visitors are returning |
| Form completion by visit type | Visitor profiles | Whether opt-in rate improves on return |
| Destination click-through | Event stream | Which journey drives more action |
| Journey completion | Live view, CSV export | How far returning vs. new visitors get |

If your rescan rate is below 10%, your first-visit experience may not be compelling enough to bring people back. If it's above 30%, you have a strong retargeting opportunity to capitalize on.

## Common retargeting patterns

| Industry | First visit | Return visit |
|---|---|---|
| Retail / FMCG | Product story + opt-in | Loyalty offer or reorder link |
| Events | Agenda + registration | Post-event survey + replay |
| Real estate | Property overview | Viewing request form |
| B2B | Company intro + whitepaper | Demo booking or pricing page |
| Hospitality | Menu or room info | Upsell or rebooking discount |

## Frequently asked questions

### How does Linkbreakers know a visitor is returning?

Linkbreakers builds a device fingerprint from browser, OS, screen size, and network signals. It's probabilistic — not cookie-based — so it works even when visitors clear cookies or use private browsing. Accuracy is high for typical devices but may vary with VPNs or shared devices.

### Can I limit how many times the rescan branch fires?

The scan/rescan condition distinguishes first scans from all subsequent scans. It doesn't currently distinguish second from third visits. For finer-grained multi-visit logic, consider combining it with form auto-skip behavior to progressively collect data without friction.

### Does retargeting work without form submissions?

Yes. The scan/rescan condition fires based on device recognition, not form submission. Visitors who skipped your form on the first scan can still be routed differently on return.

### Does changing the workflow affect historical analytics?

No. Historical events are stored as-is. Updating the workflow only affects future scans.

### Can I A/B test my first-visit vs. return-visit journeys?

Not natively within Linkbreakers. However, you can compare performance by filtering your analytics to visitors where visit count = 1 vs. visitors with multiple events on the same link.

## Limits and caveats

- Feature availability and limits can vary by plan and workspace setup.
- Results depend on correct implementation, attribution setup, and data quality controls.
- Regulatory and privacy obligations vary by jurisdiction and use case.