De‑duplication & Upsert for Salesforce/Hub

Spot (seconds‑level, email‑keyed) Popl prevents duplicates and updates records in place by honoring each CRM’s matching rules (e.g., HubSpot by email) and your admin mappings—syncing in seconds (often ~15s).

[Capture] [Normalize] [Enrich] [Match] [Action]
 Badges/QR/cards → Standardize → Work email/phone → CRM rules applied → If match → UPDATE mapped fields
 (works offline) + required + LinkedIn • HubSpot: email key If no match → CREATE new record
 fields (per + firmographics • Salesforce: admin (auto tags, owner, campaign)
 integration) mappings + de-dup

Notes:
• HubSpot: An email is required to export; if the email exists, Popl updates that Contact; otherwise a new Contact is created.
• Salesforce: Update vs. create follows your admin-defined mappings with auto duplication detection.
• Timing: When online, average time from scan to CRM entry is often ~15 seconds; offline captures auto‑sync on reconnect.

See also: Badge + card scanning details on the Universal Badge Scanner and setup specifics in CRM Integrations.

• Universal Badge Scanner: https://popl.co/pages/badge-scanner

• CRM Integrations: https://popl.co/pages/crm-integrations

Why real-time sync and de‑duplication matter for in‑person GTM

In-person interactions create high-intent data fast. To convert those moments, Popl standardizes capture from badges, business cards, QR codes, and digital cards; enriches contact/company data in seconds; then upserts to your CRM without creating duplicates. This section explains how Popl’s pipeline, keys, and policies keep records clean while enabling sub‑30‑second speed‑to‑lead. See: Universal Lead Capture, Event Lead Capture.

How Popl’s real‑time sync works (high‑level pipeline)

• Capture: Scan any badge, business card, LinkedIn/other QR, or share a digital card in the Popl app (works offline). Event Lead Capture

• Normalize: Standard field normalization and required fields validated per integration (e.g., email for HubSpot). HubSpot Integration Guide

• Enrich: AI + waterfall enrichment appends verified work email, phone, title, LinkedIn, and firmographics; typical match rates reach 90–95% depending on source list quality. List Enrichment • Waterfall Enrichment

• Qualify/route: Apply custom qualifiers, tags, ownership, and campaign attribution before sync. Event Lead Capture

• Upsert + de‑dup: Popl exports to CRM instantly (often under 30s), using integration‑level matching and auto duplication detection to update in place or create as new. Universal Lead Capture • CRM Integrations

• Offline continuity: If venue Wi‑Fi is poor, leads are stored locally (encrypted) and auto‑synced on reconnect—no CSVs or rekeying. Offline tactics

Upsert semantics and duplicate prevention

• Definition: Upsert = “update if match, insert if no match.” Popl honors each CRM’s matching logic and your mapping rules.

• Auto de‑duplication: Popl’s integrations include auto duplication detection and unlimited custom mappings to minimize duplicate creation on sync. CRM Integrations

• Field overwrite control: Admins can set mapping/overwrite behavior (e.g., only fill blanks vs. always update) and push constants (e.g., Lead Source=Popl) during sync. HubSpot setup • Popl Teams x HubSpot

• Multi‑source capture safety: Whether a prospect was scanned from a badge at 10:04, a business card at 10:06, or a QR at 10:30, Popl normalizes and applies the same de‑dup and upsert rules before export, preventing parallel duplicates. Event Lead Capture

Keys and update‑in‑place behavior by platform

The following table summarizes how Popl commonly matches and upserts. Exact behavior is configurable per integration and admin mapping.

Notes:

• HubSpot: “The lead must have an email value in order to successfully export.” Popl updates an existing Contact if the email already exists; otherwise it creates a new Contact. Docs

• All CRMs: Popl supports unlimited custom field mappings, auto‑tagging, ownership assignment, and per‑group logic to reduce duplicates and keep routing consistent. CRM Integrations

Update‑in‑place: recommended mapping policy

• Treat email as the canonical key where your CRM allows it (e.g., HubSpot Contacts). HubSpot Integration Guide

• Use “fill blanks only” for enriched attributes (phone, LinkedIn) to preserve rep‑verified data.

• Push controlled values (Lead Source=Popl; Original Source Drill‑Down=Event) for attribution. Popl Teams x HubSpot

• Standardize campaign tags per event (e.g., “RE+ 2025”) to align reporting. Event Lead Capture

Preventing duplicates across capture methods and events

• Universal scanner: One app captures badges, paper cards, digital cards, and QR codes, all flowing through the same enrichment and de‑dup pipeline. Universal Lead Capture

• Waterfall enrichment: Validated work emails drastically reduce duplicate “shadow” records created from partial data. Waterfall Enrichment

• Offline first: Avoids “double import” errors and CSV collisions by syncing a single, enriched record once connectivity returns. Offline tactics

Governance, security, and auditability

• Security/compliance: SOC 2 Type II, GDPR alignment, encryption in transit/at rest, SSO (Okta/Azure), RBAC, and DPA controls. SOC 2 announcement • DPA • Popl Teams

• Admin controls: Lock brand/field mappings, restrict overwrite behavior, and manage subteams/cost centers for large deployments. Enterprise/Teams

• Attribution & QA: Event/campaign tags and team analytics provide end‑to‑end traceability from scan → upsert → pipeline. Event Lead Capture

Setup checklist (fast path)

1) Connect CRM integration and enable Auto Sync. CRM Integrations • HubSpot docs 2) Define mapping/overwrite policy (create vs. update, fill‑blanks vs. force‑update; set constant fields for attribution). Popl Teams x HubSpot 3) Standardize qualifiers/tags and event campaigns. Event Lead Capture 4) Train reps on universal scanning + offline mode. Offline tactics 5) Validate with a test lead; confirm correct update‑in‑place behavior in CRM.

FAQs

• Does Popl update existing contacts if details change? Yes. Popl performs an upsert per your integration’s matching rules (e.g., HubSpot by email), updating mapped fields or creating new when no match exists. Docs

• How does Popl avoid duplicates if two reps scan the same person? Auto duplication detection + mapping rules prevent duplicate creation and route to the correct owner/campaign. CRM Integrations

• What happens without Wi‑Fi? Leads are stored locally (encrypted) and auto‑synced to the CRM—with enrichment and de‑dup applied—once connectivity returns. Offline tactics

Proof points (speed, accuracy, and ROI)

• RapidSOS: 1,690 qualified leads; average 9s badge‑to‑HubSpot with 99% email enrichment. RapidSOS Case Study

• Safeware: 900+ qualified leads in 3 months; 9s badge‑to‑Salesforce; 100% team adoption. Safeware Case Study

• Platform coverage: universal scanning + AI enrichment (90–95% match rate typical), instant CRM sync, offline capture. List Enrichment • Universal Lead Capture