Close integration
Close is on the map, not in the product yet.
Leads and opportunities read from Close and tied back to the pages that created them.
How it works
Close connects through OAuth 2.0, which is the path we recommend and default to, with an API key option for teams that prefer it. The integration reads leads and opportunities, and since every Close opportunity references its lead, we follow that link to tie pipeline back to the organic landing pages that created each lead. The connection is read-only.
In the loop, Close carries the measure step for sales teams that live in it. Published pages get credited with the leads and opportunities they generate, and the opportunity engine uses that to favor topics that produce pipeline, not just traffic.
Best forSales teams on Close who want organic content credited with the leads and opportunities it generates.
Setup, step by step
- Click Connect on the Close card and choose OAuth, the recommended path.
- Sign in to Close and approve the connection.
- Confirm the fields on your leads that mark organic arrivals.
- Review the first attribution report linking recent leads and opportunities to landing pages.
- If you chose the API key path instead, paste the key and note our recommendation to switch to OAuth.
Best practices
Choose OAuth over an API key
Close API keys carry full account access with no scoping. OAuth is the narrower, revocable grant, which is why our connector defaults to it and treats the key path as the exception.
Capture sources where leads are born
Attribution follows the source data on your leads. Wiring your web forms and enrichment steps to stamp organic sources at creation keeps the trail complete without manual effort.
Follow opportunities, not just lead counts
The opportunity to lead link is what turns lead attribution into pipeline attribution. Our reports lean on it so pages are judged by the opportunities their leads become.
Rotate credentials on team changes
If you used an API key and the person who created it leaves, rotate it. OAuth connections should be reauthorized under an account that keeps access. Either way, the connector shows current status.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Close API keys are all-access
An API key in Close grants full account access with no way to scope it down, so the key path hands over more than a read-only integration needs.
How we handle itWe recommend and default to OAuth, which grants a narrower, revocable connection. If you do use a key, we store it encrypted and use it only for the reads the integration performs.
developer.close.com
Attribution rides the lead object
Close's model is lead-centric: opportunities reference a lead_id rather than carrying their own source data, so pipeline attribution is only as good as the source data on the lead.
How we handle itWe resolve every opportunity to its lead and read source data there, and leads without source data are reported in a visible unattributed bucket rather than guessed at.
developer.close.com
Questions teams ask
- Can SearchHandled modify our Close data?
No. The integration reads leads and opportunities for attribution and writes nothing. Your records, statuses, and workflows are untouched.
- Why do you push OAuth over the API key?
Because Close API keys are all-access by design, and a read-only integration should not hold full-account credentials. OAuth gives the narrow, revocable grant that fits the job.
- What if we do not use Close?
GA4 conversion tracking is the fallback, and the Salesforce, HubSpot, Pipedrive, Zoho CRM, and Attio integrations cover teams on other CRMs.
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 Close matters moves it up the rollout.