New lead
Google Ads
First touch, read from OmniScale
- UTM source
- UTM medium
- cpc
- Campaign
- Ceramic coating
- Click id
- Present
- Landing page
- /ceramic-coating/
- Referrer
- google.com
Attribution
A lead lands with its source attached and the close is a paid job in Urable, so your ad spend is set against both and you see what a customer cost from each source. The return sits beside it.
Leads reach Scale Command through your OmniScale new-lead workflow, at your lead address, and the source is read from the fields OmniScale already keeps on the lead: session source, UTMs, click id, campaign, landing page, referrer. First touch wins.
LeadsSample shop
New lead
Google Ads
First touch, read from OmniScale
A lead becomes a customer when its Urable job has money paid on it. The revenue is what was paid, not the invoice total, and it counts the same whoever booked the job: you, your manager or one of our reps.
It has 60 days from first touch to its first payment to count under that source. The few the data cannot place we tag by hand, and log every tag.
One customerSample shop
Lead in: Google Ads. First touch.
Day 1
Booked by your manager.
Day 4
Paid in Urable: $1,250.
Day 9
Counted: a new Google Ads customer, inside the 60 days.
Day 9
Six figures per source: new customers, cost per lead, close rate, cost per customer, return, and what those customers are worth over time, the app's LTV to date, counted across twelve months. Cost per customer is the source's ad spend divided by the paying customers it brought; return is what they paid in their first 60 days against that spend. Small counts and young groups are marked too early rather than judged, and how it's counted is written out beside the numbers.
AttributionSample shop
12 weeks. Weakest return first.
How it's counted
The rule behind each figure, written out beside it.
Blended cost per customer is all your ad spend divided by every new paying customer, the ones from your website, organic, referral, call in and unknown included. Ad-only divides the same spend by the customers an ad source brought. Referral and Organic never get a cost of their own, since no ad money bought them.
Both figures, on your phone in the Partner PortalAttributionSample shop
Cost per customer
$148blended
$6,204 in ads, 42 new paying customers
Ad-only counts the 27 customers who came from an ad source.
The same ad spend feeds the Ads screen's weekly return, and attribution sits beside that card.
AdsSample shop
Week 12
$4.11 booked for every $1 of ads
Four things, then the tag flips to Attribution ready: a Urable key, your lead address, your Google account and a baseline.
What each step needs, and who does itGet set upSample shop
Jobs and payments.
New-lead workflow.
Spend, LSA included.
$450 a job, 9 new a month.
Attribution ready
Without Urable there is no payment to count, so the app shows booked-only numbers and labels them that way.
Connect it under Connections and the figures switch to payments.
What Urable sendsAttributionSample shop, no Urable
Cost per customer
Booked only$131blended, booked only
Counts booked jobs until Urable is connected.
Paste your key once, under Connections.
The first one counts. First touch wins, and the first section above lists the fields it is read from.
The week: spend by platform against what was booked, as $4.11 booked for every $1 of ads. Attribution adds the per-source cost and return beside it. The Ads page has the card.
In Scale Command, and in your Partner Portal on your phone: the sources, cost per customer and return. Attribution ready shows once setup is done. The Partner Portal page has the four tabs.
On the call we go through where your customers come from now, and what the numbers would show once Urable and your ads are connected.