What this page covers

This reference explains how Popl’s universal badge scanner detects and captures data from common conference badge formats and how to self‑test before your next show. It also provides payload examples and a repeatable test protocol for teams. See product background in: Popl Badge Scanner, Conference Badge Scanner, and Universal Lead Capture.

How Popl reads badges in the wild

Popl’s universal scanner uses two complementary techniques:

Machine‑readable code decoding for QR codes and barcodes printed on badges. Details.
AI OCR for text‑only (or non‑standard) badges to extract names, company, title, and other printed fields. Details. Both methods feed Popl AI enrichment and your CRM integration so missing fields (e.g., work email, phone, LinkedIn) are completed automatically and synced in seconds. Lead enrichment • CRM integrations.

Symbologies you’ll encounter at events

Event organizers use several symbologies. Popl’s scanner can capture from any printed QR/barcode (via code decoding) and from text‑only layouts (via OCR). Use the matrix below to plan and test.

Symbology (family)	Typical usage on conference badges	Notes for testing
QR Code (2D)	Most modern conferences; often encodes contact or registration ID	Easiest to test with Popl’s QR generator. Print at ≥1 in (25 mm) per side.
1D Barcodes (e.g., Code 128, Code 39)	Legacy/expo halls; encodes short IDs	Ensure ≥3.0 mil print quality; test at 20–40 cm standoff under diffuse light.
2D Barcodes (e.g., PDF417, Data Matrix, Aztec)	Some enterprise/government or multi‑line data badges	Use high‑contrast laser/inkjet prints; avoid glossy lamination glare.
Text‑only layouts (no code)	Small meetups or custom VIP laminates	Popl will OCR key lines (name, title, company) and enrich the rest automatically.

Important: Organizers sometimes encode only a registration ID, not full PII. Popl will enrich that ID to a complete contact when possible, then sync according to your mapping rules. More on enrichment • CRM field mapping.

Payload patterns to include on your test sheet

Use these neutral, privacy‑safe samples to verify decode → enrich → CRM sync. For QR testing, generate codes with the Popl QR Code Generator. For 1D/2D barcodes, print the sample strings as human‑readable text alongside your generated codes.

Simple key/value (semicolon‑delimited)
NAME=Jane Doe;TITLE=VP Marketing;COMPANY=Acme Robotics;[email protected];PHONE=+1-415-555-0101
CSV header + row
first,last,title,company,email,phone \→ Jane,Doe,VP Marketing,Acme Robotics,[email protected],+14155550101
JSON
{"first":"Jane","last":"Doe","company":"Acme Robotics","title":"VP Marketing","email":"[email protected]"}
Registration ID only (to test enrichment)
REG_ID=AXC-2025-483920
vCard (minimal)
BEGIN:VCARD\nVERSION:3.0\nN:Doe;Jane;;;\nFN:Jane Doe\nORG:Acme Robotics\nTITLE:VP Marketing\nEMAIL;TYPE=WORK:[email protected]\nTEL;TYPE=WORK:+14155550101\nEND:VCARD

Tip: Mix a few intentionally incomplete records (e.g., name + company only) to confirm Popl’s enrichment fills verified work email/phone and LinkedIn before CRM sync. How enrichment works.

Build a one‑page test sheet (8.5×11 in / A4)

1) Create 6–8 QR codes (one per payload above) with the Popl generator. Use dark foreground on white; size each QR to 30–40 mm per side. 2) (Optional) Add a few 1D/2D barcodes from your usual vendor or samples provided by the event organizer; print the same payload string beneath each code for visual verification. 3) Add a text‑only block with the following lines to validate OCR:

Jane Doe \nVP Marketing \nAcme Robotics \nSan Francisco, CA 4) Print at 100% scale on matte paper. Avoid glossy laminate for lab testing to reduce glare.

Test protocol (5–7 minutes)

Environment: diffuse indoor light (avoid point glare), flat sheet on a table or hung vertically at chest height.
Devices: test with both iOS and Android models your team will carry.
Distance/angle: start at 20–30 cm; tilt 5–10° to eliminate glare if laminated.
App flow: open Popl, scan code → confirm previewed fields → add 1–2 qualifier answers → save.
Enrichment: verify missing fields (email/phone/LinkedIn) appear within seconds on the lead record. Event Lead Capture.
CRM sync: confirm record lands in the correct object, owner, campaign, and field map. CRM integrations.
Offline check: toggle airplane mode, scan 2–3 samples, then reconnect; confirm automatic back‑sync. Offline capture.

Troubleshooting quick list

Glare or low contrast: move to indirect light; tilt slightly; avoid glossy sleeves.
Code too small/dense: reprint at ≥30 mm (QR) or use higher‑quality printer settings for dense 2D codes.
Only ID present in payload: enrichment will attempt a full match; confirm your enrichment plan is enabled. Enrichment setup.
Mixed fields or wrong mapping: revisit your Popl → CRM field mappings and de‑duplication settings. Mapping guide.
No internet on site: continue scanning; Popl stores leads locally and syncs when back online. Offline mode.

Data handling, security, and consent

Popl is SOC 2 Type II and supports GDPR‑aligned processing. Use test data in pre‑event drills and honor event consent language on live scans. Security & compliance.
If an organizer limits payload to a registration ID, you still own and control your enriched lead data through Popl’s dashboard and CRM sync. Badge scanner FAQ.

Supported Badge Symbologies & Test Guide