Review where leads came from and resolve uncertain source assignments using evidence. The goal is a supported attribution record, not a more flattering report.

What you’ll see

The Attribution tab, where you confirm where leads came from when LeadScore couldn't match them on its own.

Before you start

You need access to attribution settings and enough context to recognize the source of an enquiry or outcome. Review only records you are authorized to see. No sender, phone number, or automation setup is needed to inspect the review queue.

Review the queue

  1. Open Settings → Marketing → Attribution and use Refresh to retrieve the current report. Read How sources are assigned to understand the shared rules used by intake, outcomes, and reporting.
  2. Work through Needs Review. A record here needs attention because its source could not be confidently resolved; it is not automatically an incorrect or bad lead.
  3. Inspect the suggested source and View evidence and record IDs. Compare the evidence with what actually generated the lead. Keep identifiers and personal details out of public screenshots or copied explanations.
  4. Choose Use [suggested source] only when the suggestion is supported. If another offered source is better supported, choose it and use Apply. These actions save a resolution; there is no separate final page-wide Save step.
  5. Refresh the queue and inspect the resulting attribution in the relevant report. Leave an item unchanged when the evidence does not establish a reliable choice.

Check the result

Success means the chosen source can be explained from the evidence and the updated view reflects the saved decision. A source confirmation does not prove an advertisement caused a purchase or that a conversion was successfully reported to an external platform.

If something goes wrong

Troubleshooting

If the queue cannot load, resolve the service notice before changing records. If the correct source is uncertain, preserve that uncertainty rather than choosing the first plausible option. After a failed Apply action, refresh before retrying; check whether the record already changed. Compare reporting periods and filters when a later aggregate appears different from the item reviewed.

More guides

Dashboard, Communication.

Screenshots

The screenshot for this guide is shown above, under “What you’ll see”.