Connect Meta and Google Ads to CRM outcomes without confusing stages

Define the business stages before the connector

A platform choice such as Salesforce or HubSpot cannot resolve inconsistent stage definitions. Document transition criteria, responsible owners and the time each outcome happened. A website visit or WhatsApp click does not establish a conversation or qualification.

Reservations, signed contracts and cash collections may be different milestones in the business. Preserve those distinctions rather than reporting the first action as collected revenue.

On smaller screens, scroll the table horizontally to read all columns.

Preserve the fields needed for a decision

Keep a stable internal inquiry identifier, acquisition time, source, campaign, landing page, language, market, stage dates and rejection reasons. Separate a person from multiple inquiries where one individual asks about several projects.

Retain click identifiers and UTM values when available and permitted. Do not invent a GCLID or reconstruct identity from missing data. Names, phone numbers and conversation text should not be sent to Analytics merely because they exist in CRM.

Primary reference: Google Analytics: avoid sending personally identifiable information

Map milestones instead of copying every field

For each destination, specify the source state, supported event, timestamp source, outcome identity and retry behavior. GA4 event names are not automatically interchangeable with Meta events. A documented qualify_lead event does not mean a CRM feed is already operational.

Google Ads supports qualified and converted lead goals using offline outcomes. The available connector, fields and account configuration determine the implementation; do not assume the same integration is active for every business.

Primary reference: Google Ads: qualified leads and converted leads

Make retries preserve outcome identity

If a connector retries after a network failure, retain the identity of that stage transition and the delivery result. A new timestamp or an unrelated CRM record update must not manufacture another business outcome.

Qualification followed by a contract represents two different transitions with separate identities. Retrying the qualification is not a new contract. Keep delivery failures, exclusions and corrections in an auditable operational log.

Connect spend to the acquisition cohort

This month’s contracts may come from people acquired months earlier. Group inquiries by registration period and source, then evaluate their progress after a defined follow-up interval. Retain counts of cases still being worked.

Two advertising platforms may both attribute the same contract under their respective windows and models. Adding those values does not create additional contracts, and attributed sales do not establish that advertising alone caused the outcome.

Validate the reporting path before using it for budget decisions

In a test environment, trace an inquiry through receipt, qualification and contract stages. Test a retry and an unchanged stage update. Check timestamps, currency and the absence of personal data in Analytics requests.

After release, reconcile stage totals against their source systems and explain scope, consent and processing differences. Sessions, inquiries and people are different units and should not be expected to match one for one.