Skip to main content
TrackingConsultingFree audit
RubyAnswering services and AI receptionists

Ruby answers your ad calls. Google Ads still can't tell which ones became clients.

Your number forwards to Ruby and a message lands in your inbox. Google Ads only saw a call that lasted long enough, so a vendor pitch and a new bankruptcy client count the same. We tag the call before it reaches Ruby, carry the ad source into your CRM, and send back only the callers who became signed clients or booked jobs.

Get my free conversion tracking auditSee what we check

Free30 minutesNo obligation

By Ariful IslamHow Ruby works ↓

Ruby · what breaks

What goes wrong when Ruby answers your ad calls

  1. 01

    "Google Ads shows a pile of calls. Ruby's messages show a handful of new leads."

    Google Ads counts any call that runs past the minimum length you set. A Ruby receptionist politely handling an existing client clears it easily, so bidding learns to buy follow-ups, solicitors and wrong numbers with your budget.

  2. 02

    "The good leads are in my email, not in Google Ads"

    Ruby delivers messages by email, text and its app. None of that reaches Google or Meta, so neither learns which campaign produced the consult you signed last Tuesday.

  3. 03

    "Our hottest callers never show up as leads"

    Ruby sends a message when it can't connect a call to you, and its Zapier trigger fires on messages. Transfer a ready-to-hire caller straight to you and there may be no message, no Zap and no CRM record, so that ad gets no credit.

  4. 04

    "Website chat looks busy, but it's mostly questions"

    Ruby's Google Analytics option logs an event when a chat starts, so a visitor asking your hours counts the same as a full intake.

Ruby · the fix

What changes after we fix it — Ruby

  • Only real new-client calls count

    The lead conversion fires from Ruby's intake result in your CRM, so existing clients, robocalls and sales pitches stop teaching Google Ads what to buy.

  • Signed cases and paid jobs flow back to the ad platforms

    Each Ruby lead carries its click ID into Clio, HubSpot, JobNimbus or whichever CRM Ruby feeds, and the outcome goes back to Google Ads and Meta with a real value.

  • Live transfers back on the lead list

    Calls Ruby connected to you are reconciled from the call logs you export from the Ruby portal, so the campaigns producing your best calls finally get credit.

Ruby · architecture

What Ruby actually lets you hook into

Ruby answers and routes conversations; it doesn't report them to ad platforms. Here's what its own documentation shows.

  1. 1

    Call forwarding or a Ruby-hosted number

    Calls reach Ruby by forwarding from your carrier, delayed forwarding, or porting your number to Ruby. Tracking has to happen before that hop.

  2. 2

    Chat code snippet in your site code

    Ruby's chat loads from a snippet placed before your page's closing head or body tag. Its Google Analytics option, set up by Ruby's team from your tracking ID, logs a chat-start event.

  3. 3

    Native CRM and practice-management integrations

    Ruby lists Clio, MyCase, Filevine, Lawmatics, Law Ruler, Rocket Matter, Salesforce, HubSpot, Zoho, Keap, Follow Up Boss, JobNimbus and FieldPulse. We confirm what each one writes for your account, then attach the click ID to that record.

  4. 4

    Zapier

    The trigger fires when a receptionist takes a message, polled every 15 minutes down to every minute depending on your Zapier plan.

  5. 5

    Activity export

    Call and chat logs download from the Ruby portal, and that export is our reconciliation source.

  6. 6

    No documented ad-platform connection

    We found no Ruby-documented Google Ads, Meta Pixel, Conversions API or webhook option, so outcomes travel back through your CRM.

Ruby · diagnose

Where Ruby tracking breaks, in diagnostic order

Start at the phone line, because most Ruby problems begin before a receptionist ever picks up.

  1. 01

    Follow one ad call through every forward

    Call the tracked number from an ad click and confirm the source survives the hop to Ruby.

  2. 02

    Check what Google Ads counts as a call conversion

    Compare the minimum call length against how long Ruby's message-taking calls usually run.

  3. 03

    Compare Ruby's activity export with CRM leads

    Live transfers that never became a message show up here as missing records.

  4. 04

    Open the CRM record for a test ad call

    Look for the click ID on the Clio matter, HubSpot contact or JobNimbus lead tied to that Ruby call.

  5. 05

    Confirm where the chat event lands

    Ruby's help article still describes a tracking ID path, so check the event actually arrives in your GA4 property.

Ruby · prove

How we prove Ruby leads are counted right

Run on real calls through your live number while Ruby is answering, not on a test line Ruby never sees.

Source of truth

Ruby's exported call and chat logs, matched to signed clients or paid jobs in the CRM Ruby feeds

  • One call from an ad-tagged click followed from tracking number to Ruby message to CRM record.
  • One live transfer confirmed as a lead even though Ruby sent no message.
  • An existing-client call and a solicitor call confirmed absent from the lead conversion.
  • Signed clients matched one by one against Google Ads and Meta over a closed window.
  • Rerun a month later, and again whenever forwarding or Ruby's call-handling instructions change.

Ruby · free audit

What we check in the free audit

  • Follow one ad call through every forward
  • Check what Google Ads counts as a call conversion
  • Compare Ruby's activity export with CRM leads
  • Open the CRM record for a test ad call
  • Confirm where the chat event lands

Checked against

Ruby's exported call and chat logs, matched to signed clients or paid jobs in the CRM Ruby feeds

Get my free conversion tracking audit

Free30 minutesNo obligation

Ruby · when not to buy

When Ruby customers can skip this

Plenty of Ruby customers have nothing to fix.

  • If Ruby covers overflow and after-hours only and you don't run paid ads, there's nothing to attribute.
  • If nearly all your calls are referrals and existing clients, Ruby's activity log already tells you what you need.
  • If your CRM already records Ruby's new-client calls with an ad source and you upload signed clients to Google Ads, leave it alone.
  • If the only gap is the chat event, ask Ruby's Customer Happiness team to point it at your current GA4 property. That's a support ticket, not a project for us.

Ruby · what we deliver

The event map on Ruby

  • Call to the tracked ad number

    Recorded on the call tracking or Google forwarding number before your line forwards to Ruby, with the click and keyword attached.

  • Chat started

    From Ruby's chat widget on your site. Kept as a diagnostic signal and never used for bidding.

  • New-client intake by Ruby

    A message or live transfer marked as a new prospect. Existing clients, solicitors, wrong numbers and screened robocalls are excluded.

  • Qualified lead

    Set in your CRM when the matter or job fits: consult worth having, estimate worth driving to.

  • Consult or appointment booked

    Including times Ruby books for you through Calendly or Google Calendar.

  • Signed client or paid job

    The conversion that bidding optimizes for, valued from your retainer or invoice and sent to Google Ads and Meta.

Written guarantee

95%+ tracking accuracy

Measured against Ruby's exported call and chat logs, matched to signed clients or paid jobs in the CRM Ruby feeds. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Ruby questions, answered

Not that Ruby documents. Its integrations cover CRMs, practice-management tools, calendars, phone systems and Zapier, so the ad-platform connection has to run through your CRM and call tracking.

More on Ruby

RELATED GUIDES

Booking tools beside Ruby, and what their bookings feed

Free · 30 min

Find out which Ruby calls your ads actually paid for

Book the free audit WhatsApp

Free30 minutesNo obligation