Separate spam from unsuitable and unanswered inquiries in your report

Avoid one catch-all bad-lead label

A request from outside the service area, a duplicate callback, a robot-generated message, and a customer the team never answered are different situations. Combining them hides the action needed. Define a small disposition list with observable reasons. The goal is useful operations reporting, not a larger headline qualification rate. If a request cannot yet be assessed, mark it unresolved rather than labeling it spam because staff have not reached the person.

Source checks: Conversions vs. key events in Google Analytics · Enhanced measurement events

Write evidence for each disposition

Confirmed spam needs a documented basis such as irrelevant automated content or a verified abusive pattern. Outside scope needs the requested service or area. Duplicate status needs a match to the same inquiry or job. Unanswered status means the business has not completed its handling step. Keep personal details in the restricted inquiry system. The aggregate report should explain the category without exposing the customer's message, contact information, or problem.

Separate interaction events from delivered requests

Analytics can record form interactions or other configured events, but the accepted-request store establishes delivery. A bot interaction, rejected form, or duplicate event may never become a unique business inquiry. Reconcile those layers before computing the spam share. Do not send questionable form contents into ordinary analytics parameters as proof. Review the collection setup and retain only appropriate aggregate information for the marketing report.

Assign the next fix to the correct layer

Confirmed automated spam may call for suitable server-side validation or form protections. Outside-scope demand may call for clearer service wording or targeting review. Duplicates may need request identity and retry safeguards. Unanswered suitable inquiries require staffing or follow-up correction. Avoid solving every category by adding more advertising exclusions; that can remove useful demand while leaving the actual delivery or handling fault unresolved.

Keep ad-traffic conclusions within the evidence

A spam request attributed to a campaign is a useful signal to investigate, but it does not alone prove invalid paid clicks or establish a refund entitlement. Review the account's supported traffic diagnostics and business records separately. Similarly, a legitimate customer who does not book is not automatically spam. Record uncertainty and actual outcomes so the owner can discuss the specific evidence with the implementation or advertising manager.

Measure disposition and useful-work counts together

At the next review, show delivered unique inquiries, each unusable category, qualified requests, bookings, and unresolved cases. Track whether the correction reduced the intended category without reducing suitable work unnecessarily. Check staff consistency when labels change. A lower spam percentage can result from more legitimate traffic rather than a protection working; counts and comparable periods help distinguish those explanations. The report should lead to a specific accountable correction.

Worked example: illustrative figures

For example, 30 received records contain 5 confirmed spam messages, 4 duplicate representations, 6 outside-scope requests, 3 suitable requests still unanswered, and 12 handled suitable inquiries. Unique delivered requests excluding duplicates are 26. Confirmed spam is 5 ÷ 26 = 19.2% of that defined set. The three unanswered suitable requests remain a handling problem, not spam. These categories require evidence and must be mutually defined for the worksheet; they do not establish invalid advertising charges or predict refunds.

Questions about this task