Google and Meta Ads: Connect Campaigns to Sales Outcomes
Use Convertly to connect eligible qualified-lead and sales outcomes to Google Ads and Meta, with clear milestone definitions, tested mappings, and delivery checks.
A submitted form tells you someone enquired. It does not tell you whether the lead was suitable, whether a conversation happened, or whether the opportunity became a sale.
Convertly can connect those later CRM outcomes back to Google Ads and Meta through configured conversion integrations. The purpose is to give the platforms useful feedback about what happened after the enquiry—not simply count every stage change as another success.
Agree on the outcome before connecting the platform
Choose a meaningful sales milestone and define it in plain language. A qualified lead might require a confirmed need and a completed conversation in your business. A won stage should reflect the actual event your team uses to recognize a sale.
Keep those definitions consistent. If one teammate qualifies a lead after an unanswered call while another waits for a detailed discussion, the same event label carries different meanings.
Start with a small number of milestones your team can apply reliably.
Connect the appropriate return path
A workspace Admin manages the setup under Integrations:
- Google Ads Offline Conversions connects the Google account and maps relevant CRM milestones to the appropriate conversion actions.
- Meta Conversions API connects the intended dataset and maps CRM milestones to the intended Meta events.
Meta Lead Ads is a separate inbound connection for enquiries from instant forms. Importing those enquiries does not, by itself, configure the return of later sales outcomes.
Use the product setup guides for account-specific values rather than copying another workspace’s configuration.
Preserve the information needed for eligible events
The lead needs the identifiers and other information required by the configured delivery and matching strategy. Applicable consent, event time, value, and currency also need attention.
A lead source label alone does not guarantee eligibility. Not every lead or stage transition will create a valid platform event, and missing information should not be invented.
Record a meaningful value when it is known. An arbitrary value chosen merely to populate a field can make later comparisons less useful.
Validate before enabling production delivery
Keep the supported test controls enabled while checking setup. Use a controlled event and review the relevant integration’s logs and provider-side test result where available.
Confirm the connected account or dataset, event mapping, lead context, timestamp, and any value or currency. Google and Meta maintain separate integration logs in Convertly, so investigate the return path you actually tested.
Where the same event is also sent through browser measurement, review the provider’s deduplication requirements as part of the setup. Do not assume two deliveries should count as two separate outcomes.
Distinguish delivery from advertising results
Queued, attempted, failed, and accepted are different states. A successful delivery does not guarantee that a platform will attribute the event exactly as the CRM does or improve campaign performance by a particular amount.
When comparing reports, align the period and metric and consider eligibility, matching, timing, and attribution differences. Use accepted outcomes and genuine sales results to inform your review rather than expecting identical totals everywhere.
Follow the Google Ads guide and Meta Conversions API guide to configure the return path. The foundation is the same for both: clear outcomes, sound source data, and a verified connection.