HighTouch enables modern data teams to sync customer data from Salesforce and other sources into activation platforms without custom code. By combining Salesforce Data Loader exports with HighTouch reverse ETL, you can keep your CRM and warehouse synchronized in near real time.
This guide walks through the end to end process of preparing Salesforce data exports, configuring HighTouch connections, and automating activation workflows. The steps below assume you have admin access to both systems and want a durable, repeatable setup.
| Tool | Primary Purpose | Typical Frequency | Security Controls |
|---|---|---|---|
| Salesforce Data Loader | Bulk extract and load data from Salesforce objects | Daily to weekly | IP restrictions, OAuth, encryption at rest |
| HighTouch Reverse ETL | Push warehouse data back into Salesforce and downstream tools | Hourly to daily | RBAC, SCIM, audit logs, field level masking |
| Data Warehouse | Central source of truth for analytics and syncs | Continuous ingestion | Column level security, VPC endpoints |
| Activation Platform | {td}Target apps such as ad platforms, support, or CDP{/td}Near real time or batch | Webhooks, API rate limit controls |
Installing and Configuring Salesforce Data Loader
Download and Authentication Setup
Install the latest Salesforce Data Loader on a secure server or workstation with access to your org. Use an integration user with minimal but sufficient permissions, and configure OAuth JWT Bearer flow for headless authentication.
Export and Query Planning
Design SOQL queries that select only the fields and date ranges required for HighTouch activation. Schedule exports using the command line version so the output CSV files land in a secure, monitored storage location such as an encrypted S3 bucket.
Preparing Your Data Warehouse and HighTouch Source
Staging and Transforming Salesforce Exports
Land raw Data Loader extracts in a staging schema, then apply cleansing, deduplication, and type normalization before merging into your canonical data model. Ensure surrogate keys and change tracking fields like SystemModstamp are preserved for delta syncs.
Connecting HighTouch to the Warehouse
In HighTouch, add your warehouse as a data source using service credentials with read only access to the relevant schemas. Map warehouse tables to Salesforce objects using explicit join keys and avoid ambiguous fan joins that can cause sync overages.
Configuring Reverse ETL Sync Rules
Mapping Fields and Destination Objects
Define field mappings between warehouse columns and Salesforce fields, including picklist translations and record type selection logic. Use HighTouch transformation functions to handle edge cases such as null handling, lookups, and upsert key matching.
Scheduling and Rate Limit Management
Set sync frequency aligned with downstream consumption needs while respecting Salesforce API limits. Configure HighTouch concurrency controls, error backoff policies, and partial failure handling to avoid org wide lockups and API quota exhaustion.
Monitoring, Logging, and Alerting
Success Criteria and KPIs
Track key metrics such as rows exported per run, latency from warehouse update to Salesforce activation, error rate, and API usage. Implement dashboards that surface both Data Loader file generation success and HighTouch sync job outcomes in a single view.
Auditing and Compliance
Enable detailed logging in both tools, rotate credentials periodically, and store logs in a tamper evident system. Align row level security in the warehouse and field level security in Salesforce so that activation respects the same least privilege principles used in analytics.
Operational Best Practices and Key Takeaways
- Use an integration user with scoped permissions and OAuth JWT flow in Data Loader
- Preserve change tracking fields and surrogate keys to support reliable upserts
- Maintain canonical mapping tables in the warehouse for picklists and lookups
- Respect Salesforce API limits with controlled concurrency and backoff logic
- Monitor end to end latency, error rates, and data quality in unified dashboards
- Rotate credentials periodically and store secrets in a secure vault
- Log unresolved references and failed rows for audit and reprocessing
FAQ
Reader questions
How do I handle referential integrity when syncing from warehouse to Salesforce?
Maintain canonical mapping tables in the warehouse for types, owners, and record types, and use deterministic external IDs for upserts. Validate foreign key relationships before export and log unresolved references to a quarantine table for manual review.
What should I do if HighTouch sync jobs start failing due to API limits?
Reduce concurrency, add proxy rotation or IP pooling, and align batch sizes with Salesforce governor limits. Monitor API usage dashboards in real time and implement exponential backoff plus retry queues for transient errors.
Can I use Data Loader or HighTouch alone without a data warehouse?
While lightweight integrations are possible, skipping a warehouse removes the single source of truth and makes mapping, debugging, and auditing significantly harder. For production grade syncs, a warehouse remains strongly recommended.
How frequently should I rotate integration user credentials for Data Loader and HighTouch?
Follow your organization identity policy, typically every 90 days for high privilege integration users, and immediately rotate keys on any suspected exposure. Automate credential rotation and update stored connections in both tools using secure secret management.