Search Console can't connect to a CRM directly, because it reports searches and pages, never individual visitors. The working join is the landing page: record the page each lead first arrived on, keep it on the deal, then match won deals to that page's search clicks. A CSV export, a webhook or a form snippet carries the page.
What it doesn't do: This join can't name the search one buyer typed. It splits each deal across a page's searches by click share, and deals without a landing page stay unmatched.
Updated
Search Console counts searches and the clicks they send to each page. It never records who clicked. Your CRM records people and deals, but not the search they typed. The only thing both know is the page.
So the join runs through the landing page, and each deal is split across that page's searches by share of clicks. That rule is called click-share attribution; the exact version RankUpside uses is in how revenue is allocated.
Pick at least one way to put the page on every new lead. Most sites need the form snippet and call tracking together.
| Method | Works for | Setup |
|---|---|---|
| Form snippet | Any site whose forms are plain HTML forms on the page | One script tag on every page. It adds hidden landing_page and lead_source fields to every form, and the CRM stores them with the lead. See the form snippet docs. |
| Call tracking | Businesses that get leads by phone | CallRail or WhatConverts sends the landing page with each call by webhook. See CallRail. |
| The CRM's own first-page field | CRMs that record where a lead first arrived | Nothing to install. Check the field is filled on new leads and included in exports. |
Forms inside an iframe, such as some embedded booking widgets, don't get the hidden fields; use the widget's own landing-page capture there. More on the snippet: website forms.
Export won deals with a date, an amount, a landing page and a status (won, open or lost). Common header names from HubSpot, Jobber and GoHighLevel exports are recognized, so most files upload without renaming columns. Re-uploading the same file updates deals instead of adding them twice. See the CSV format and CSV import.
A CRM workflow posts each won deal to POST /api/hooks/revenue with the client's revenue key as a bearer token. One request can carry one deal or a list of up to 500. Sending a deal again with the same ID updates it, so a status change from open to won lands on the same deal.
POST /api/hooks/revenue Authorization: Bearer rk_•••••••• { "id": "D-1042", "date": "2026-10-14", "landing_page": "https://copperlinegutters.example/", "amount": 4200, "status": "won", "source": "organic" }
Field names, responses and the leads webhook: webhooks. Overview: won-deal webhook.
In each client's sub-account, build one workflow triggered when an opportunity is marked won. Add a webhook action that posts to the client's revenue webhook with the bearer key, and map the opportunity's ID, close date, value and landing page to the deal fields. Make sure the landing page field is filled on the contact or opportunity first, from the form snippet or your own capture.
Trigger and action names change between GoHighLevel versions, so use the names in your own workflow builder. One workflow per sub-account. More: GoHighLevel.
The simplest route is a CSV: filter deals to closed won, include the landing page property, and export. For deals as they close, a HubSpot workflow on a closed-won deal can post to the webhook, where your HubSpot plan includes workflow webhooks.
Check the property and action names in your own HubSpot account. More: HubSpot.
If the CRM can't post a webhook, Zapier's webhook step can: trigger the zap on a won deal, then post the same JSON fields to the same endpoint with the bearer key. Check that your Zapier plan includes webhook steps. More: Zapier.
When a deal arrives, it goes to its landing page. Its value is then split across the searches that sent that page clicks over the last 13 weeks, by each search's share of the page's clicks. Clicks from searches Google hides keep their own line, so no named search is over-credited.
| Search | Clicks | Share of page clicks | Allocated |
|---|---|---|---|
| gutter repair fairview/services/gutter-repair | 3 | 18% | $150 |
| gutter guard installation/ | 3 | 3% | $121 |
| fairview gutter repair/services/gutter-repair | 2 | 12% | $100 |
| gutter cleaning fairview/blog/gutter-cleaning-fairview-cost | 12 | 25% | $85 |
| gutter covers installation/ | 2 | 2% | $81 |
| gutter cleaning/blog/gutter-cleaning-fairview-cost | 3 | 6% | $21 |
| Other searches and searches Google hides | $4,832 | ||
How to present the result to a client without overclaiming: how to prove SEO revenue to clients. The feature itself: revenue by search.
?utm_source=gbp so map-pack leads are labeled and kept separate.No CRM data yet? Estimate what search is worth from the client's own lead numbers with the SEO revenue calculator.
Phone numbers and emails are used only to link a won deal to the call or form lead it came from. They are stored as salted hashes, plus the last two digits of the phone number for display. A won deal links to a lead with the same contact within 120 days.
Full details: data and permissions.
RankUpside takes won deals by CSV, webhook or form snippet and splits each one across its page's searches, with hidden searches on their own line.
Weekly search report · Copperline Gutters
Sep 14 – Oct 11, 2026 vs the 4 weeks before
Copperline Gutters got 27 clicks from named buyer searches in the last 4 weeks, up 23% from the 4 weeks before. Google hides the search terms behind 84% of all 289 search clicks. Rankings rose across the site: pages that steadily show up are up about 2.4 positions.