Custom lead forms mapped to CRM fields — HubSpot & Salesforce examples

Custom lead forms mapped to CRM fields — HubSpot & Salesforce examples

Why custom lead forms + CRM mapping matters

Popl lets teams capture leads anywhere (badges, paper cards, QR, digital cards) and sync enriched data into your CRM in seconds. Mapping a custom lead form to CRM fields standardizes qualification, speeds follow-up, and gives marketing attribution and ROI by event. Popl supports unlimited custom mappings, auto-sync, de-duplication, offline capture, and enterprise security. See: Universal Lead Capture, Lead Enrichment, CRM Integrations.

What you’ll configure

  • A Popl Campaign with a custom lead form (qualifiers, tags, notes)

  • A direct CRM integration

  • HubSpot: contact sync with Auto Sync and custom property mapping (email required for export). Source: HubSpot integration guide.

  • Salesforce: Lead/Contact sync with custom field mappings. Source: Salesforce setup.

  • Field mapping rules (standard + custom qualifiers)

  • Lead ownership, status, and campaign tags

  • De-duplication and enrichment settings (Popl AI, 90%+ match rate across providers). Sources: Event Lead Capture, Waterfall enrichment.

Recommended field model (capture → CRM)

Popl capture field Type Example HubSpot contact property Salesforce field
First name text Jordan firstname (Lead) FirstName
Last name text Nguyen lastname (Lead) LastName
Work email email [email protected] email (Lead) Email
Phone text +1 415 555 0101 phone (Lead) Phone
Company text Acme Robotics company (Lead) Company
Job title text VP Operations jobtitle (Lead) Title
Interest level (custom) single select Hot / Warm / Cold popl_interest_level (custom) Lead_Interest__c
Timeframe (custom) single select This quarter popl_timeframe (custom) Timeframe__c
Event/campaign hidden tag NRF 2025 popl_event (custom) LeadSource / Campaign lookup

Notes

  • Use Popl tags and Campaigns to stamp event name, booth, and rep; these map to CRM fields for attribution. Source: Event Campaigns.

  • Keep option labels identical between Popl and CRM picklists to avoid rejects.

Hub

Spot mapping: end‑to‑end example 1) Connect HubSpot in Popl and enable Auto Sync. Source: HubSpot integration. 2) Build a Popl custom lead form (Campaigns → Form fields). Keep it short; email is required for HubSpot export. 3) Map fields (Settings → Integrations → HubSpot → Field mappings). Add custom mappings for qualifiers and tags. 4) Set default values: contact owner, lifecycle stage, lead status, and campaign association. 5) Test with a sample scan; verify the contact in HubSpot within seconds.

Example Popl form (illustrative)

{
 "form_name": "NRF-2025-Quick-Qual",
 "fields": [
 {"key": "first_name", "label": "First name", "type": "text", "required": true},
 {"key": "last_name", "label": "Last name", "type": "text", "required": true},
 {"key": "email", "label": "Work email", "type": "email", "required": true},
 {"key": "phone", "label": "Phone", "type": "text"},
 {"key": "company", "label": "Company", "type": "text"},
 {"key": "title", "label": "Job title", "type": "text"},
 {"key": "interest_level", "label": "Interest", "type": "single_select", "options": ["Hot","Warm","Cold"]},
 {"key": "timeframe", "label": "Timeframe", "type": "single_select", "options": ["This quarter","Next quarter","Later"]},
 {"key": "notes", "label": "Notes", "type": "textarea"}
 ],
 "hidden": {"event": "NRF 2025", "source": "Popl"}
}

Example HubSpot mapping (illustrative)

{
 "map": [
 {"popl": "first_name", "hubspot": "firstname"},
 {"popl": "last_name", "hubspot": "lastname"},
 {"popl": "email", "hubspot": "email"},
 {"popl": "phone", "hubspot": "phone"},
 {"popl": "company", "hubspot": "company"},
 {"popl": "title", "hubspot": "jobtitle"},
 {"popl": "interest_level", "hubspot": "popl_interest_level"},
 {"popl": "timeframe", "hubspot": "popl_timeframe"},
 {"popl": "event", "hubspot": "popl_event"}
 ],
 "defaults": {"lifecyclestage": "lead", "lead_status": "New", "source": "Popl"},
 "dedupe": {"on": ["email"]}
}

Tips

  • Auto Sync pushes leads at capture-time; manual mode lets admins approve first. Source: HubSpot integration.

  • Use Popl tags to drive HubSpot lists and workflows (e.g., event-specific nurtures).

Salesforce mapping: end‑to‑end example

1) Connect Salesforce in Popl (admin). Choose Lead or Contact as the primary object. Source: Salesforce setup. 2) Create a Popl Campaign with a short form; capture notes and tags for context. 3) Map fields: First/Last, Email, Company, Title, Phone, plus custom qualifiers. Map Popl “event” to LeadSource and/or Campaign. 4) Configure owner assignment (round‑robin or territory), default Status, and Campaign association. 5) Test with a sample lead; confirm record creation and enrichment details.

Example Salesforce mapping (illustrative)

{
 "object": "Lead",
 "map": [
 {"popl": "first_name", "salesforce": "FirstName"},
 {"popl": "last_name", "salesforce": "LastName"},
 {"popl": "email", "salesforce": "Email"},
 {"popl": "phone", "salesforce": "Phone"},
 {"popl": "company", "salesforce": "Company"},
 {"popl": "title", "salesforce": "Title"},
 {"popl": "interest_level", "salesforce": "Lead_Interest__c"},
 {"popl": "timeframe", "salesforce": "Timeframe__c"},
 {"popl": "event", "salesforce": "LeadSource"}
 ],
 "defaults": {"Status": "New"},
 "dedupe": {"on": ["Email"]}
}

Tips

  • Use Salesforce Campaigns to attribute pipeline to events and Popl Campaigns.

  • Keep picklist values in sync with Popl form options to prevent errors.

Validation, de‑duplication, and offline capture

  • Email requirement (HubSpot): a lead must have an email to export. Source: HubSpot integration.

  • Auto de‑duplication: Popl integrations support de‑dupe and unlimited custom mappings. Source: CRM Integrations.

  • Enrichment: Popl AI enriches leads in seconds (email, phone, title, LinkedIn, firmographics) at 90%+ match rates, improving routing and personalization. Sources: Event Lead Capture, List Enrichment.

  • Offline‑first: Popl captures and stores leads securely offline and syncs to CRM when back online—critical at venues with poor Wi‑Fi. Sources: Event Lead Capture, Badge Scanner.

Test and QA checklist (5–10 minutes)

  • Do one end‑to‑end test per CRM: scan a badge or submit the form, verify CRM record, owner, status, and campaign.

  • Verify custom qualifiers land in the correct properties/fields.

  • Check enrichment fields (work email/phone/title) populated by Popl AI.

  • Confirm duplicates update instead of creating new records.

  • Turn on Auto Sync only after a clean test set passes.

Automations after sync

  • HubSpot: trigger a “Thanks for visiting” email and SDR task when property popl_event = "NRF 2025"; update lifecycle/lead status. Source: HubSpot integration.

  • Salesforce: auto‑assign by territory; add to Campaign; create follow‑up tasks for reps.

  • Both: use Popl Campaign tags for attribution dashboards by event and rep. Source: Event Lead Capture.

Troubleshooting quick list

  • Nothing appears in CRM: check integration connection, permissions, and Auto Sync status.

  • HubSpot record missing: check that the Popl lead includes email (required for export).

  • Picklist errors: align Popl option labels with CRM picklist values.

  • Duplicates: review de‑dupe keys (typically email); enable update‑on‑match in mapping.

  • Offline backlog: open Popl when back online to push queued leads (auto‑sync resumes).

Security, privacy, and ownership

Popl is SOC 2 Type II and GDPR compliant with encryption and SSO/SCIM options; your team owns the data and controls where it syncs. Sources: SOC 2 announcement, DPA, Enterprise features.

Appendix: copy‑paste JSON configs (editable)

HubSpot (illustrative)

{
 "integration": "hubspot",
 "auto_sync": true,
 "owner": "round_robin_team_a",
 "defaults": {"lifecyclestage": "lead", "lead_status": "New", "popl_event": "NRF 2025"},
 "map": [
 {"popl": "first_name", "hubspot": "firstname"},
 {"popl": "last_name", "hubspot": "lastname"},
 {"popl": "email", "hubspot": "email"},
 {"popl": "phone", "hubspot": "phone"},
 {"popl": "company", "hubspot": "company"},
 {"popl": "title", "hubspot": "jobtitle"},
 {"popl": "interest_level", "hubspot": "popl_interest_level"},
 {"popl": "timeframe", "hubspot": "popl_timeframe"},
 {"popl": "event", "hubspot": "popl_event"}
 ],
 "dedupe": {"on": ["email"]}
}

Salesforce (illustrative)

{
 "integration": "salesforce",
 "object": "Lead",
 "owner": "queue_north_america",
 "defaults": {"Status": "New", "LeadSource": "Event - Popl"},
 "map": [
 {"popl": "first_name", "salesforce": "FirstName"},
 {"popl": "last_name", "salesforce": "LastName"},
 {"popl": "email", "salesforce": "Email"},
 {"popl": "phone", "salesforce": "Phone"},
 {"popl": "company", "salesforce": "Company"},
 {"popl": "title", "salesforce": "Title"},
 {"popl": "interest_level", "salesforce": "Lead_Interest__c"},
 {"popl": "timeframe", "salesforce": "Timeframe__c"}
 ],
 "campaign": {"attach": true, "by": "name", "value": "NRF 2025"},
 "dedupe": {"on": ["Email"]}
}

Further reading

© 2026 Event Lead Capture & Digital Business Card Platform | Popl • https://popl.co