Salesforce is where most revenue teams keep the system of record for accounts, pipeline, and closed business. Connecting it as a data source through the Connectors library syncs those tables into your Alta workspace, where they become training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure pipeline and win rates, segment by any Salesforce field, and let Luna answer questions in plain English.
Who this is for: RevOps, sales leadership, and analytics teams who want Salesforce data measured and queried across Alta.
Not the same as the CRM integration. Connecting Salesforce here (under Connectors) brings its data in for analytics and training. If you instead want Alta to sync contacts and write activity back for outreach, use the CRM integration under Settings → Integrations (see Related). Many teams run both.
Before you start
You'll sign in to Salesforce in a popup — use a Salesforce user with read access (via profile or permission set) to every object you want to sync.
For the cleanest, most auditable setup, use a dedicated integration user with a read-only profile.
Know whether you're connecting Production or a Sandbox org so you sync the right data.
You only connect a source once per workspace. If Salesforce already shows Connected, edit the existing connection instead of adding a new one.
Connect Salesforce
Open Connectors from the sidebar.
Find Salesforce — use the CRM category tab or the Search data sources box.
Click the Salesforce card to open the Create connector screen.
You'll see "Connect your Salesforce account using OAuth." Click Connect, sign in to Salesforce in the window that opens, and wait for Authentication succeeded!
Back in the library, the card shows Connected with a spinner and Data is syncing until the first sync finishes.
Choose which tables sync
Open the connection from the library. Salesforce defaults to syncing the
accounttable, alongside standard objects like contacts, opportunities, and leads.In the Salesforce tables section, the Synced toggle and Table name columns control what's pulled in.
Turn off Show only synced tables to see every available object — including custom objects (typically ending in
__c) — and enable more.
Key tables and fields synced
account — the company record:
Id,Name,Industry,Type,AnnualRevenue,NumberOfEmployees,BillingCountry,OwnerId,CreatedDatecontact — people at an account:
Id,AccountId,Email,Title,LeadSource,CreatedDateopportunity — the deal/pipeline record:
Id,AccountId,Amount,StageName,Probability,CloseDate,IsWon,IsClosed,Type,OwnerIdlead — top-of-funnel:
Id,Status,LeadSource,Company,ConvertedDate,IsConvertedopportunitylinehistory / opportunityhistory — stage and amount changes over time, for velocity and stage-conversion analysis
task / event — activity records (calls, emails, meetings) linked to accounts, contacts, and opportunities
user — rep/owner lookup:
Id,Name,Email,IsActive
What you can ask this data
Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:
"What's our total open pipeline by stage this quarter?" — sums
opportunity.Amountgrouped byStageName."Which industries have the highest win rate?" — joins
opportunitytoaccount.IndustryusingIsWon."How many opportunities did each owner close last month?" — counts won opps by
OwnerIdandCloseDate."What's average deal size by lead source?" — averages
Amountgrouped byLeadSource."What's our average sales cycle from creation to close?" — measures
CreatedDatetoCloseDateon won opps."Which deals slipped close date this quarter?" — uses
opportunityhistoryto find pushedCloseDatevalues.
Example use cases
Pipeline & forecast dashboard. Track open pipeline, weighted forecast (
Amount×Probability), and coverage vs. quota, sliced by team, segment, or region.Win/loss analysis. Combine
opportunitystages withaccountattributes to see which segments, sources, or reps convert best — and where deals stall.Rep performance & activity. Join
task/eventactivity to closed deals to connect outreach effort with outcomes.Train Alta on your real customers. With accounts, won opportunities, and industries synced, Alta learns what your best-fit customers look like to sharpen targeting.
Keep it in sync
The Sync status section shows Last sync (with Succeeded or Failed) and the Sync frequency.
Click Sync now to pull fresh data immediately (Sync triggered successfully). It's greyed out while a sync is running.
Use the overflow menu (⋯) to Disable, Enable, or Delete the connection.
Tips and common pitfalls
Sync only what you need. Salesforce orgs have hundreds of objects — enabling everything slows syncs and clutters your data. Start with accounts, contacts, opportunities, and leads, then add custom objects deliberately.
Permission errors come from Salesforce. If a table or field won't sync, the connecting user likely lacks read access (object- or field-level) to it.
Production vs Sandbox. Connecting a sandbox by mistake is a common reason numbers look wrong — confirm the org you authenticated.
Custom fields are included for synced objects, so your bespoke pipeline fields come along too.
Deleting is permanent — it removes all synced Salesforce data and config. Disable instead if you only want to pause.
Related
