QR codes on business cards: the size, placement, and tracking rules that work

A business card QR is a low-stakes deployment of a high-value pattern. Print one card, hand it out at a conference, scan tracking tells you which event drove the most engagement and which rep's card actually got used. Scale that to a 20-person sales team across 12 events a year and the tracking data is valuable.

Here is the practical guide.

Where the QR goes on the card

Back of the card, centered or right-aligned. The front carries the name, title, company logo, and primary contact info. The back is for QR plus optional secondary brand details (website URL, social handles, brief tagline).

Some teams put the QR on the front in the bottom-right corner. This works if the card design is minimal and the QR is small. For most card layouts, back placement reads cleaner.

Avoid: putting the QR over a brand mark, near the edge of the card (binding clip risk), or on a glossy laminated surface (camera glare on scan).

Sizing

A business card is roughly 8.5 cm by 5.5 cm. The QR should be 2 to 3 cm square.

• 2 cm minimum. Older Android phones struggle below this size. Scan reliability drops.
• 2.5 cm sweet spot. Comfortable for most cameras at the typical 30 cm scanning distance.
• 3 cm if you have the space. Larger is more forgiving; the trade-off is the QR dominates the card design.

Higher print resolution lets you go smaller; offset litho on heavy stock at 300 dpi scans cleanly at 1.8 cm. Digital print on cheaper stock needs the upper end. When in doubt, larger is safer.

What the QR should encode

Two patterns work; one is better for tracking.

1. URL pointing at a redirector (recommended). The QR encodes acme.co/<rep-name> or acme.co/<rep-id>. The redirector points at the rep's personal landing page (or a generic team landing page if reps share). You can change the destination later, you can track scans, you can A/B test the landing page.

2. vCard (encoded contact info). The QR encodes contact data directly. Scanning it triggers an "add to contacts" prompt on the visitor's phone. No tracking, no editing, no analytics, but the user experience is faster (no landing page).

For sales-rep cards, option 1 is usually the right call. For executives or networking-focused cards where speed of contact-add matters more than tracking, option 2 can be defensible.

You can do both: a dynamic QR pointing at a redirector that detects the user agent and either serves a vCard download or redirects to a landing page. The piece on trackable QR for print marketing covers this pattern.

Per-rep utm_content

If you tag the redirector destination with UTMs, give each rep their own utm_content value:

utm_source=qr
utm_medium=offline
utm_campaign=business-card
utm_content=<rep-name-lowercase-hyphenated>

For a sales rep named Jordan Lee:

utm_content=jordan-lee

Now scans from her cards show up in GA4 distinct from scans from other reps' cards. Sales managers can see which reps' cards drove the most engagement. The piece on campaign naming for SaaS covers the convention.

Per-event utm_content

If your reps attend many events, layer event identifier into the utm_content:

utm_content=jordan-lee-saastr-2026

Or use a separate utm_term for the event:

utm_content=jordan-lee
utm_term=saastr-2026

Now you can slice scans by rep, by event, or by both combined. The trade-off is each rep needs a different short link per event, which means more link management. Most teams reserve per-event tagging for big events (top 4 to 6 per year) and leave smaller events on the per-rep slug only.

Card design rules with a QR on it

Three principles:

1. Quiet zone around the QR. The QR specification requires roughly one module's worth of clear space on every side. Card layouts that crowd the QR with text or other design elements break scanning.

2. Brand colors with sufficient contrast. Brand-color QR codes work as long as the dark color is dark enough. Navy, deep red, dark green on white. Avoid pastels-on-pastels.

3. No logo overlay needed for cards. A 2 to 3 cm QR with a logo overlay barely fits the logo legibly. Skip the logo overlay on cards; reserve that decoration for larger surfaces (posters, packaging) where the logo can actually be seen.

The piece on branded QR code design rules has the longer list of design rules.

The destination landing page

The page the QR redirects to should be:

• Mobile-first. Scans happen on phones. The page should load in under 2 seconds and render cleanly without zooming.
• Personalized to the rep, if possible. A page with the rep's photo, contact info, and a clear next-step CTA converts better than a generic team page.
• One primary CTA. Schedule a meeting, download a resource, request a demo. Multiple CTAs split the user's attention and lower conversion rate.
• Form-prefilled from URL parameters when used at events. If you append ?event=saastr-2026 to the destination, the form on landing pre-populates the event name, saving the visitor a typing step.

A common pattern: the rep's personal landing page is yoursite.com/team/<rep-name> and the QR points at the redirector wrapping it. The redirector's URL stays constant; the landing page can be redesigned without reprinting cards.

Tracking what actually matters

Scan count is interesting but not the decision-driver. The real metrics:

1. Scan-to-meeting-booked rate. Of N visitors who scanned, how many booked a meeting on the landing page.
2. Scan-to-form-fill rate. For event lead capture, how many visitors completed the form.
3. Scans by event. If your card is in circulation across 4 events, which event drove the most scans? That's the event worth re-attending.

A reasonable benchmark for a B2B sales-rep card at a conference: 5 to 12 percent of scanners book a meeting or fill the form. Below 3 percent, either the landing page is broken or the rep is handing the card to the wrong audience.

When a printed URL beats the QR

The case against QR on business cards: a 2 to 3 cm QR feels like 2020 design, and a clean printed URL at the bottom of the card (acme.co/<rep>) is competitive on phones running iOS 14+ where you can long-press a URL to open it.

Two real positions:

• Pro-QR: The QR is explicit, scannable from across a table, and tracked. A printed URL still works but does not capture which event the card was handed out at unless the user types it later.
• Pro-URL: A short, branded printed URL is cleaner visually and works without a phone-camera step. For executive cards where design polish matters more than tracking, this is the move.

Most teams do both: the QR on the back, a clean printed URL on the front. Belt and suspenders.

For the broader QR strategy, the QR codes pillar guide covers the static-vs-dynamic question. For the event-specific patterns, trackable QR codes for events and conferences covers booth backdrops, swag bags, and other surfaces where the same QR rules apply.