How to Connect Ad Leads to CRM Sales and Collected Payments

Connect source leads to orders before comparing totals

Marketing wants to know which campaigns produced prospects worth pursuing. Sales wants to know which leads became orders. Management also needs to know what was collected. These questions should follow the same relationship chain, but they count different things. Start with original lead IDs, customer IDs, opportunity IDs, order IDs and payment records rather than lining up monthly totals from separate systems.

A customer may have several enquiries, opportunities and orders. Keep a relationship table so each order can identify its opportunity and originating leads. For many-to-many relationships, define an allocation method or explicitly retain links without allocating value. List unmatched orders separately. The closest date is not enough to assign an order to an advertisement.

Merge duplicates without losing source events

Distinguish an API retry importing the same record, one person submitting several enquiries, and an existing customer starting a new purchase. The first can be made idempotent using the source platform and original record ID. The other two require retaining the enquiry events before deciding whether to merge a customer, continue an opportunity or create another one.

Names, phone numbers and email addresses can support a review, but one matching field should not automatically establish the same buying entity. People may share contact details or represent different companies. Keep original records and merge mappings, with separate definitions for new enquiries, distinct customers and qualified opportunities.

Phone enquiries, offline events and manually entered sales leads also need event IDs and source evidence. If an ad touchpoint cannot be established, keep the source unconfirmed rather than inferring advertising credit from a later sale. A first phase can cover reliably linked forms while clearly identifying excluded lead sources.

Retain campaign, creative, landing-page parameters and collection time on the original event. Updating a customer's current source must not overwrite earlier touchpoints. Otherwise historical channel performance can change whenever a sales user edits a field.

Separate the lead cohort from the attribution window

“How many of this month's leads became orders?” follows leads acquired this month and their later outcomes. “How many orders closed this month?” groups by order date. Dividing one by the other does not produce a meaningful lead conversion rate. For long sales cycles, show the observation cutoff and distinguish recently acquired leads from cohorts with months of follow-up.

Google Ads defines a conversion window as the period after an ad interaction during which a conversion can be recorded. A CRM can retain a longer business history, while separately identifying platform attribution rules and the version of an internal first- or last-touch rule. A sale outside the platform window may still be a valid CRM order. Do not change its date just to make the totals agree.

Treat orders, receipts and refunds as different events

Order value describes sales booked; receipts describe money received; refunds describe money returned. Deposits, instalments and later refunds should reference the original order while keeping their own event dates. To report net collections for a lead cohort, total receipts less refunds for linked orders through the observation cutoff. To report cash movement in a period, group payment events by date. Keep the date basis and denominator explicit.

Conversion uploads also need a correction path. Google Ads distinguishes restatement from retraction: one changes conversion value, while the other removes the conversion. Check the supported conditions and time limits of the actual platform and retain upload status. An edited CRM order does not prove that the advertising platform has received a corresponding correction.

Validate relationships with representative records

Before release, have marketing, sales and finance select samples together and reconcile each against its original records. Channel totals should lead to the associated leads and orders, with unmatched, unpaid and unreported items visible. A single conversion-rate tile cannot replace these verification paths.