What a junk removal call log can and cannot tell you

The two records on the table

Most marketing case studies start with a big number and work backwards. This one starts with the paper. The Vancouver junk removal record on our site is built from two original documents belonging to a local junk removal business, and those two documents are the only real evidence we show.

The first is a call log. It lists inbound calls to the business. The second is a Google Ads screenshot, taken from the advertising account, showing spend, impressions and conversions for a set period.

Both are genuine. Both are useful. And both are easy to misread, because each one answers a narrower question than people tend to ask of it. An owner looking at them together naturally wants to know whether the ads paid for themselves. That is a fair question and an important one. It is also a question these two records, on their own, cannot answer.

So rather than stretch them, we want to read them carefully. What does each record actually say? Where do they overlap? Where do they stop? And what would need to exist alongside them before anyone could honestly say what the advertising did for the business?

What the call log shows

The call log recorded 44 inbound calls between January 1 and February 16, 2026. That window is 47 days, counting both the first and last day.

That is a fact, and a useful one. It tells you the phone was ringing, roughly how often, and across which dates. For a junk removal business, where a lot of work begins with someone calling to ask whether a truck can come this week, inbound calls are a sensible thing to watch.

Here is what the log does not record.

• How each caller found the business. A call from someone who saw an ad looks exactly the same as a call from a past customer, a neighbour's referral, the Google Business Profile, or a truck parked on the street.
• Whether a call became a booked job. Some calls are price checks, some are wrong numbers, some are existing customers rescheduling. The log does not separate them.

So the honest reading is narrow. The business received 44 inbound calls in those 47 days. We cannot say from this record why any of them called, or how many turned into work. Any statement beyond that would be an inference, and we would label it as one.

What the ads screenshot shows

The Google Ads screenshot covers January 14 to February 14, 2026, which is 32 days inclusive. Over that window the platform recorded CA$470.95 in spend, 4,561 impressions and 9 conversions.

The spend and impressions are fairly plain. Money left the account, and the ads were shown 4,561 times. The conversions need more care.

A conversion in Google Ads is whatever the account was set up to count. Depending on the settings, it might be a click on a phone number, a call of a certain length, a form submission or a page visit. The screenshot shows the count, not the definition behind it. That is why we describe these as conversions as counted by the platform and nothing more.

What a platform conversion is not, by itself, is a booking. Nine conversions means the platform saw nine events it was told to count. It does not mean nine trucks went out, nine invoices were paid, or nine new customers were won. Those facts live in the business's own records, not in the ad account.

So the screenshot tells us what Google observed inside its own system. It is a real record of platform activity, and it should be read as exactly that.

Why the date windows matter

The two records do not cover the same days. The call log starts on January 1, which is 13 days before the ads window opens. It ends on February 16, which is 2 days after the ads window closes.

That gap sounds like a small detail. It is not. When two records cover different periods, setting one number against the other quietly mixes days that belong to one record and not the other. Calls from early January cannot be compared with ad activity that had not yet been recorded in the screenshot. Calls from February 15 and 16 fall outside the ads window entirely.

On top of that, the call log has no source field. So even inside the overlapping days, there is no way to tell which calls, if any, came from the ads. The overlap tells you the two records were running at the same time for part of the period. It does not tell you that one caused the other.

This is why we do not put the 44 calls next to the CA$470.95 and draw a line between them. It would look precise, and it would mean nothing. Comparing records properly starts with matching the windows, and then with knowing where each call came from. Our guide to lead attribution covers this in more depth.

What it would take to answer the real question

The owner's real question is simple. What did the advertising produce? Answering it honestly needs a few records that are not in this set.

1. Call source tracking. A tracking number on the ads, a separate number on the Google Business Profile, and the main line everywhere else, so each call carries a record of where it started.
2. Form tracking. Website quote requests tagged with the page and channel that sent the visitor, so form leads are counted alongside calls rather than forgotten.
3. A booked job field. One column in the call log or CRM that says whether this enquiry became a scheduled job, and ideally what the job was worth once it was invoiced.
4. Consistent date ranges. The ad report, the call log and the job records pulled for exactly the same days, so nothing is counted from outside the window.

None of this is complicated or expensive. It is mostly setup and discipline. But until it exists, the most truthful thing anyone can say about this business is what we have said here. The phone rang 44 times over 47 days, Google reported on the ads over 32 days, and the link between the two is unproven. We would rather tell an owner that plainly than hand over a number that cannot hold its weight.