Salesforce integration
Salesforce is on the map, not in the product yet.
Leads and opportunities read from Salesforce, attributed to the organic landing pages that produced them.
How it works
Salesforce connects through OAuth 2.0 using an External Client App, the current generation of what Salesforce long called Connected Apps. The integration is read-only: we query leads and opportunities and correlate them with the organic landing pages those records trace back to, so published content gets credited with the pipeline it creates. Nothing is written to your org.
In the loop, Salesforce is the measure step at full weight. Rankings and traffic are proxies; pipeline is the number the business runs on. When an article's landing page shows up behind real opportunities, the opportunity engine learns which topics produce revenue-shaped outcomes, not just clicks, and prioritizes accordingly.
Best forSales-led companies on Salesforce who want organic content credited in pipeline terms their leadership already trusts.
Setup, step by step
- Have a Salesforce admin create and authorize the External Client App, following our guided admin setup doc.
- Click Connect on the Salesforce card and sign in through the OAuth flow.
- Approve the read-only access on the consent screen.
- The connector checks your edition's API access and reports plainly if it is unavailable.
- Review the first attribution report tying recent leads and opportunities to landing pages.
Best practices
Bring your admin in early
The External Client App must be created and authorized by a Salesforce admin, and that is the longest step. Sending them our setup doc before you start turns a back-and-forth into one sitting.
Keep lead source data honest
Attribution rides the source fields on your leads. Imports and manual entry that blank or overwrite source data erase the trail, so fold source hygiene into your team's data rules.
Judge content on opportunities, not just leads
A page producing leads that never convert differs from one producing pipeline. We read both objects so pages are weighed by what their leads become, and the reports keep the distinction visible.
Reconnect when admin ownership changes
The client app and its authorization live in your org under admin control. If the authorizing admin leaves or the app is deactivated, the connection pauses until an admin reauthorizes it.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
An admin must create and authorize the client app
External Client Apps can only be set up by a Salesforce admin, so a marketer cannot complete the connection alone, and setups stall waiting on admin time.
How we handle itOur guided admin setup doc covers the exact clicks with screenshots, sized so an admin can finish in one short session. The connector then verifies the app before moving on.
developer.salesforce.com
API access depends on your Salesforce edition
Not every Salesforce edition includes API access, so some orgs cannot connect regardless of setup effort.
How we handle itWe detect API availability at connect and say so in plain language rather than failing cryptically. If your edition lacks API access, GA4 conversion tracking remains the fallback measure.
developer.salesforce.com
Questions teams ask
- Can SearchHandled change anything in our Salesforce org?
No. The connection is read-only. We query leads and opportunities for attribution and cannot create, edit, or delete records, fields, or configuration.
- Why does setup involve our Salesforce admin?
Salesforce requires an admin to create and authorize the External Client App that any integration connects through. It is a one-time step, and our setup doc walks your admin through it directly.
- What if our edition has no API access?
The connector detects that at connect and tells you plainly. Attribution then falls back to GA4 conversions, which still measures outcomes, just without named pipeline records behind them.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Salesforce matters moves it up the rollout.