Turn form submissions into qualified Bigin records with the right pipeline and stage—no manual sorting required.
Popular Mappings
- Form Email → Bigin Contact Email
- Company/Website → Bigin Account Name
- Dropdown/Radio → Pipeline Stage (e.g., New Lead, Contacted)
- Hidden UTM fields → Custom fields for attribution
See examples and best practices: Gravity Forms for Bigin CRM.
Field Mapping Deep‑Dive
Precise mapping is where most teams win or lose. Start with a lean, reliable map and only add complexity where it pays for itself.
- Contact: First Name, Last Name, Email (primary key), Phone, Job Title.
- Account: Company, Website, Industry, Employee Count (optional).
- Deal: Deal Name (e.g., “{{Company}} – Inbound”), Amount (if captured), Pipeline, Stage, Owner.
- Attribution: utm_source, utm_medium, utm_campaign, landing_page, referrer → custom fields.
Conditional Logic Patterns
- Product‑based routing: If Product = “Pro”, Pipeline=Pro Sales, Stage=New Lead; else Pipeline=Core Sales.
- Region ownership: If Country in EU, Owner=EMEA Round‑Robin; if US, Owner=AMER Round‑Robin.
- Intent gating: If “Request a demo” checked, Stage=Qualified; else Stage=New Lead with Task for SDR validation.
Duplicates and Updates
Use email as the uniqueness key for Contacts. On match, update owner/stage and append notes rather than creating a second Contact. For Deals, key by a composite (e.g., Contact Email + “Inbound”) and update stage if an open deal exists.
Common Pitfalls (and Fixes)
- Stage mismatch: make sure names match Bigin exactly (case and spacing).
- Empty owner: verify the user exists and has rights in the target pipeline.
- UTM drop‑off: ensure hidden fields exist on the form and are included in the feed mapping.
Reporting Readiness
By preserving UTMs and consistent stages, you can segment velocity and win‑rate reports by campaign and source without manual cleanup.
For deeper dives, see How to Connect Gravity Forms to Bigin CRM (Quick Start), Use Cases: Send Leads from Gravity Forms to Bigin (No Code).
Security, Privacy, and Reliability
Keep tokens in WordPress, not in client-side scripts, and rotate them on a regular cadence. Limit user roles to the minimum necessary for feed administration. If you need audit trails, log feed execution results to a private log channel so failed mappings or permission problems are obvious within minutes rather than days.
Performance and Scale
On high-traffic forms, throttle optional webhooks and remove post-submit heavy tasks. The direct write to Bigin completes quickly; expensive enrichments can run asynchronously. Use short forms for first contact, then enrich on the Bigin side with tasks, sequences, or a follow-up form that gathers detail from motivated prospects.
Team SOP (Standard Operating Procedure)
- Sales ops owns the field map and signs off on any changes before they go live.
- Marketing owns UTMs, naming conventions, and campaign codes.
- Weekly QA: sample 10 recent submissions to confirm owner, stage, and attribution are correct.
- Monthly review: remove dead fields, merge duplicates, and archive unused pipelines.
Metrics and KPIs
- Time-to-first-touch (median minutes from submit to first human action)
- Conversion rate by source, medium, and campaign
- Stage-to-stage velocity for inbound deals
- Duplicate rate and data quality score
Implementation Checklist (Copy/Paste)
- Create form with required + hidden UTM fields
- Install plugin and authenticate to Bigin
- Map Contact/Deal/Account + custom fields
- Set default pipeline/stage; add conditional routes
- Configure owner assignment and auto Task
- Submit 3 test entries covering each route
- Build dashboard segmented by UTMs
Security, Privacy, and Reliability
Keep tokens in WordPress, not in client-side scripts, and rotate them on a regular cadence. Limit user roles to the minimum necessary for feed administration. If you need audit trails, log feed execution results to a private log channel so failed mappings or permission problems are obvious within minutes rather than days.
Performance and Scale
On high-traffic forms, throttle optional webhooks and remove post-submit heavy tasks. The direct write to Bigin completes quickly; expensive enrichments can run asynchronously. Use short forms for first contact, then enrich on the Bigin side with tasks, sequences, or a follow-up form that gathers detail from motivated prospects.
Team SOP (Standard Operating Procedure)
- Sales ops owns the field map and signs off on any changes before they go live.
- Marketing owns UTMs, naming conventions, and campaign codes.
- Weekly QA: sample 10 recent submissions to confirm owner, stage, and attribution are correct.
- Monthly review: remove dead fields, merge duplicates, and archive unused pipelines.
Metrics and KPIs
- Time-to-first-touch (median minutes from submit to first human action)
- Conversion rate by source, medium, and campaign
- Stage-to-stage velocity for inbound deals
- Duplicate rate and data quality score
Implementation Checklist (Copy/Paste)
- Create form with required + hidden UTM fields
- Install plugin and authenticate to Bigin
- Map Contact/Deal/Account + custom fields
- Set default pipeline/stage; add conditional routes
- Configure owner assignment and auto Task
- Submit 3 test entries covering each route
- Build dashboard segmented by UTMs
Practical Mapping Table
| GF: Email | Bigin: Contact.Email (key) |
| GF: Company | Bigin: Account.Name |
| GF: Product | Bigin: Deal.Pipeline / Stage (conditional) |
| GF: Message | Bigin: Description (append) |
| GF: utm_source | Bigin: Custom.UTM Source |
| GF: utm_campaign | Bigin: Custom.UTM Campaign |
Start simple, ship, measure, then add nuance once the core path is stable.
Owner Rules That Scale
Use a hidden field with a token like owner_hint, set by conditional logic. Map that hint to a specific user or queue in Bigin. When territories change, you only update the logic once, not every feed.
Validation and Error Handling
Make validation visible to the user and forgiving on format. For example, accept common phone formats and normalize in Bigin. When a feed fails, notify ops with the entry ID and the error message so you can correct the mapping quickly without disrupting the team.
Operational rigor matters: small, predictable improvements compound. Keep owners accountable, review mappings on a cadence, and protect the core lead path from complexity.
Case Study: From Chaos to Clarity
A midsize SaaS company ran three nearly identical forms that wrote to different places in Bigin. Reps missed follow-ups, owners were wrong, and UTMs were lost. We consolidated to a single Gravity Form with conditional feeds: one source of truth, predictable owner rules, and UTMs mapped to custom fields. Within two weeks, time-to-first-touch fell by 42% and demo-to-opportunity rose 18% because routing and attribution were finally consistent.
Related reading
- How to Connect Gravity Forms to Bigin CRM (Quick Start)
- Use Cases: Send Leads from Gravity Forms to Bigin (No Code)
- Automate Bigin Workflows from Gravity Forms Submissions (October 2026)
Frequently Asked Questions
- Do I need Zapier or webhooks? No. This plugin posts directly to Bigin using your authenticated token, which is more reliable for core lead capture.
- How should I handle duplicates? Treat email as the Contact key. Update existing records and advance stage rather than inserting a second Contact.
- What about consent and compliance? Add a required consent checkbox in Gravity Forms and map its value to a custom field in Bigin.
- How do I measure campaign performance? Map UTM parameters to custom fields and build Bigin dashboards segmented by source, medium, and campaign.
- Can I route to multiple pipelines? Yes—create multiple conditional feeds and route by product, region, or form responses.
Best Practices Recap
Ship a simple, reliable path first: no brittle rules, clear ownership, and consistent stages that everyone understands. Collect just enough information to route the lead and book the first conversation, then enrich in Bigin where the team works every day. Review the pipeline weekly, fix broken mappings immediately, and keep the entire process visible so sales, marketing, and ops share the same mental model. This discipline turns forms into meetings, meetings into opportunities, and opportunities into revenue without creating operational drag.
