The RankUpside form snippet is one script tag for the client's site. It remembers the page a visitor first landed on and whether they came from search, then adds both to every form as hidden fields named landing_page and lead_source. The CRM stores them with the lead, and won deals carry them back by CSV or webhook.
What it doesn't do: The snippet sends nothing to us and sets no cookies. It can't reach forms inside an iframe; those need the values passed another way.
Updated
Add the snippet to the client's site before </body>. Copy it from Client settings › Leads & revenue. From then on, every form on every page carries the visitor's first landing page and how they arrived.
<script src="https://rankupside.com/t.js" defer></script>
More on this:Form snippet docs
landing_page is the first page's address without the query string. lead_source is one of these, checked in this order:
| lead_source | When |
|---|---|
| paid | The landing URL has gclid, gbraid or wbraid, or a utm_medium of cpc, ppc or paid |
| utm_source / utm_medium | The landing URL is tagged with UTM parameters, for example gbp |
| google maps | The visitor came from maps.google |
| organic | The visitor came from Google, Bing, DuckDuckGo, Yahoo or Ecosia search |
| referral: host | Another site linked to the page |
| direct | None of the above |
The first landing page and source are kept in the browser's local storage for 90 days. A later visit from search, ads or a referral replaces them; a direct visit doesn't, so a returning visitor who types the address keeps their original source. Fields a form already fills are never overwritten.
No. The snippet only fills form fields. It makes no network calls and sets no cookies.
Every form in the page itself, filled on load and again on submit. Forms inside an iframe can't be reached by a script on the parent page.
Leads from the client's Business Profile belong to the map pack, not to SEO. Tag the website link on the profile and those leads are recorded as gbp, then kept out of organic search revenue.
| Website link on the Business Profile | lead_source | |
|---|---|---|
| Before | https://copperlinegutters.example/ | organic or google maps |
| After | https://copperlinegutters.example/?utm_source=gbp | gbp |
More on this:RankUpside for local SEO agencies
Custom forms that send their data with JavaScript can read window.searchRevenue, which holds landingPage and source. Forms embedded in an iframe, as some GoHighLevel and HubSpot embeds are, need the values passed into the iframe's URL or captured by the CRM's own landing-page field.
// For forms that post with JavaScript instead of a normal submit
const { landingPage, source } = window.searchRevenue;
await fetch("/your-form-endpoint", {
method: "POST",
body: JSON.stringify({ ...fields, landing_page: landingPage, lead_source: source }),
});The snippet gets the landing page into the CRM. When a lead becomes a won deal, send it back with that landing page, by CSV or webhook, and the report can tie it to searches.
More on this:CSV importWebhooksAttribution docsAllocated revenue
The first report builds from 13 weeks of Search Console history as soon as you connect. Start with 3 client sites.
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.