Salesforce
Primer connects to Salesforce over OAuth with read-only access, so you can build ad audiences from your accounts, contacts, leads and opportunities. Primer enriches the records it can match, keeps the ones it can’t, and never writes back to Salesforce.
Product example: six connected data sources: Salesforce, HubSpot, the Primer Pixel, CSV upload, Amazon S3 (beta, carrying Snowflake and Fivetran exports) and the API (beta). The SaaS Finance Leaders audience keeps 2,140 records from the CRM, 1,812 of them enriched by Primer, and adds 16,472 people from Primer's database of about 300 million people. Data shown is illustrative.
No. The connection is read-only. Primer reads records to build audiences and never writes, edits or deletes anything in Salesforce.
The most common cause is that the connecting user doesn’t have the API Enabled permission. Ask your Salesforce admin to enable it on the user’s profile or a permission set, then reconnect.
After the first sync, Primer re-reads Salesforce about once a day, so new fields or records can take up to a day to appear as filters.
The sync keeps running. That column is simply empty for the affected records, so you’ll see a coverage gap rather than an error.
Bring your data in, send audiences out, and see what’s working—across the tools your team already uses.
