Salesforce Integration with Convertr
Seamlessly connect your marketing campaigns to Salesforce CRM with enterprise-grade security and real-time lead delivery powered by Convertr and Fairway Digital Media.
Get Started
What This Integration Delivers
The Convertr-Salesforce integration transforms how your organization captures and processes leads. This enterprise-grade solution delivers leads in real-time through secure APIs directly into your Salesforce environment, whether you're using Lead or Contact objects.
Built on OAuth2 authentication and Salesforce Connected App architecture, this integration ensures every lead arrives with complete data integrity. Field-level mapping guarantees accurate data placement, while intelligent deduplication prevents duplicate records from cluttering your CRM.
Campaign routing flexibility allows you to assign leads to a single fixed Campaign ID or dynamically route them based on custom business rules—perfect for multi-product lines, regional teams, or complex attribution models.
Comprehensive monitoring and audit logs provide full visibility into the lead journey from form submission to CRM record creation. Operations teams gain complete traceability, making troubleshooting fast and compliance reporting straightforward.
How the Integration Works
01
Authentication Setup
Your Salesforce administrator configures a Connected App and provides OAuth2 credentials to establish secure communication between Convertr and your Salesforce org.
02
Real-Time API Connection
Convertr authenticates against Salesforce using the OAuth2 token endpoint and leverages the Create Record API to instantly create or update Lead and Contact records as forms are submitted.
03
Intelligent Data Mapping
Convertr's field mapping engine transforms incoming form data to match your Salesforce field schema perfectly, ensuring data lands exactly where it should with proper formatting and validation.
04
Campaign Assignment Logic
Optional routing logic assigns each lead to campaigns—either using a single fixed Campaign ID for simple programs or dynamic assignment based on custom rules for enterprise complexity.
05
Error Handling & Logging
Any errors from validation rules, required field mismatches, or permission issues are immediately surfaced in delivery logs, enabling rapid identification and resolution of integration issues.
Enterprise-Grade Security Model
OAuth2 Authentication
Integration uses Salesforce Connected App with OAuth2 protocol, leveraging Client ID/Secret, username, password, and security token for secure access.
Token-Based Access
Credentials are used exclusively to obtain short-lived access tokens. No long-term storage of plain credentials occurs within Convertr's systems.
Scoped Permissions
Integration user must have read/write access to Lead, Contact, and Campaign objects—nothing more, following the principle of least privilege.
Complete Auditability
Every transaction is captured in comprehensive delivery logs, providing full traceability for compliance, security audits, and operational monitoring.
Administrator Checklist: Required Credentials
1
Salesforce Integration User
Username + Password: Dedicated service account credentials for API authentication and record creation access.
2
Security Token
Security Token (Security ID): Can be reset in Salesforce under My Settings if the original email notification is unavailable.
3
Connected App Keys
Client ID (Consumer Key): Obtained from your Salesforce Connected App configuration in App Manager.
Client Secret (Consumer Secret): Must be revealed and copied securely from the Connected App settings.
4
OAuth Token URL
Production: https://login.salesforce.com/services/oauth2/token
Sandbox: https://test.salesforce.com/services/oauth2/token
5
Org Instance URL
Your specific Salesforce instance URL (may be required depending on your organization's routing policies and security requirements).

Where to find credentials: Navigate to Setup → App Manager → Open your Connected App → Copy Consumer Key/Secret (click to reveal). Reset Security Token in My Settings → Reset My Security Token if needed.
Field Mapping & Data Contract
Establish Your Data Contract
Field mapping is the foundation of data integrity. Convertr transforms incoming form data into your Salesforce field schema with precision field-by-field mapping. For example, first_name maps to Lead.FirstName, and job_title maps to Lead.Title.
Include all critical lead qualifiers in your mapping: custom qualification questions, asset identifiers, source tracking fields, and UTM parameters. This ensures your Sales team receives complete context for every conversation.
Deduplication Strategy
Establish clear dedupe rules to maintain CRM hygiene. Common patterns include upserting by email address, matching to existing Contacts, or converting to Leads when no match is found. Document these rules clearly in your integration runbook.
Validation Requirements
Document all required fields driven by Salesforce validation rules—typically company name, phone number, and lead source. Ensure your mapping provides values for these fields either through form collection or default fallback values.
"Maintain a comprehensive mapping sheet in your runbook to keep Marketing, Operations, and vendor teams perfectly aligned on data structure and business rules."
Campaign Routing Options
Option A: Hardcoded Campaign Assignment
Every lead originating from this Convertr campaign receives one fixed Campaign ID stamp. This approach works perfectly for single-asset campaigns or straightforward programs with unified tracking requirements.
Best for: Single product launches, individual webinar registrations, specific content downloads, or any campaign where all leads share the same marketing context and attribution needs.
Option B: Dynamic Campaign ID Routing
Campaign ID assignment happens dynamically for each lead using sophisticated logic based on asset name, geographic region, product line, form responses, or any custom business rules your organization requires.
Ideal for: Multi-track enterprise programs, global teams with regional attribution, product line segmentation, or complex marketing automation requiring granular campaign tracking across diverse audience segments.

Implementation Note: Add a Campaign ID field in your mapping configuration or derive it from business rules. Always confirm all Campaign IDs exist in your Salesforce org before launching the integration to prevent delivery failures.
Configuration Workflow
Convertr Setup (Fairway Configures)
Inside your Convertr campaign dashboard, Fairway Digital Media configures the integration job with precision:
  1. Navigate to Integration → Add Job → Salesforce Integration
  1. Select create-only or create/update (upsert) behavior based on your dedupe strategy
  1. Map fields from Convertr to Salesforce (Lead/Contact + Campaign fields)
  1. Configure Campaign ID behavior (hardcoded or dynamic routing)
  1. Save configuration and enable the integration job
Salesforce Setup (Admin Steps)
Your Salesforce administrator completes these critical configuration steps:
  1. Create or verify Connected App with API access enabled in Setup
  1. Confirm integration user has Lead/Contact/Campaign create and edit permissions
  1. Securely provide Client ID/Secret, Username/Password, Security Token, and OAuth token URL to Fairway
  1. Validate validation rules, assignment rules, and required fields that could potentially block record inserts
  1. Optional: Configure Lead Assignment Rules, Auto-response emails, and Ownership routing for territory management
Testing, Monitoring & Troubleshooting
Pre-Launch Testing
  • Unit Test: Submit a single test lead through Convertr; verify it appears in Salesforce with correct field values
  • Dedupe Test: Post a lead that already exists; confirm upsert/merge behavior works as designed
  • Campaign Test: Verify fixed or dynamic Campaign IDs attach correctly to records
  • Permissions Test: Temporarily remove a permission to confirm errors surface properly in logs
  • Speed-to-Lead: Measure submission-to-CRM time (target: real-time delivery)
Ongoing Monitoring
Use Convertr delivery logs to view real-time status, API responses, and detailed error messages for every submission.
Establish an operations playbook for daily monitoring during the first week post-launch, then transition to weekly cadence once stability is confirmed.
Common Issues & Fixes
  • Validation rule failed: Adjust field mapping or provide default values
  • Required field missing: Add field to form or map a static fallback value
  • Invalid Campaign ID: Create the campaign in Salesforce or correct the ID reference
  • Auth error: Regenerate security token; verify Client ID/Secret; check OAuth token URL
Go-Live Checklist & Team Roles
1
Pre-Flight Verification
  • Connected App created; Client ID/Secret shared securely
  • Integration user has Lead/Contact/Campaign create/edit permissions
  • Username/Password/Security Token verified and tested
  • OAuth token URL configured correctly (production vs sandbox)
  • Field mapping validated against Salesforce schema and validation rules
2
Integration Validation
  • Campaign routing (fixed or dynamic) confirmed operational
  • Test leads created successfully; dedupe and ownership verified
  • Convertr delivery logs clean with no error messages
  • Speed-to-lead performance meets real-time targets
3
Stakeholder Alignment
  • Sales team notified of new lead flow and data structure
  • Revenue Operations team briefed on monitoring procedures
  • Marketing team understands campaign attribution model
  • Monitoring cadence defined: daily for week one, then weekly
Roles & Responsibilities
Salesforce Administrator
Manages Connected App configuration, user permissions, validation rules, and security token lifecycle management.
Fairway Digital Media
Handles Convertr configuration, field mapping setup, delivery monitoring, and provides integration troubleshooting support.
Marketing Operations
Governs mapping standards, manages campaign ID structure, enforces UTM discipline, and ensures reporting alignment across platforms.
Sales Leadership
Defines lead assignment rules, establishes follow-up SLAs, and maintains feedback loop to Marketing for continuous optimization.

Frequently Asked Questions
Q: Can we send to Contacts instead of Leads?
A: Absolutely—configure mapping to the Contact object and define upsert logic (typically matching by email address).
Q: How do we handle regional teams or multiple products?
A: Use dynamic Campaign ID routing combined with additional routing fields to support ownership rules and territory assignment.
Q: What if validation rules block inserts?
A: Add default values at mapping time or relax non-critical validation rules specifically for the integration user; always re-test after changes.
Q: Can we audit what was delivered?
A: Yes—Convertr audit logs capture each payload, success/error status, and precise timestamps for compliance and troubleshooting.
Outcome: Operational Excellence
Achieve faster speed-to-lead, dramatically improve CRM data integrity, and enable repeatable, scalable campaign orchestration—all without manual CSV uploads or data entry errors. This integration transforms your lead management process into a competitive advantage.