Skip to content

Connect ad clicks to sales outcomes

Convertly connects the source of an enquiry with what the sales team records afterward. There are two different jobs: capture attribution and send outcomes back.

A lead may arrive from a native form, Meta Lead Ads, an API, a webhook, an import, or manual entry.

Supported intake automatically retains valid attribution when it is supplied: source, click identifiers, UTM values, campaign context, landing page, referrer, and applicable consent information.

A source label alone is not complete attribution. Missing click or campaign data cannot always be reconstructed later.

Review a test lead before relying on a source. Confirm the contact, source, available advertising fields, and ownership. Do not overwrite a known original source simply because the sales team later called or messaged the customer.

Capture coverage depends on the sender, website/embed configuration, consent, and browser or platform restrictions.

Agree on what Qualified, Won, and other stages mean in your business. Record genuine sales outcomes and meaningful values.

An Admin maps the appropriate stages to conversion destinations in:

Meta Lead Ads is a separate inbound connection. Importing a Meta lead is not the same as sending a later conversion event.

When a configured milestone occurs, Convertly can queue the corresponding conversion event. Sending depends on the connection being enabled, its mapping, the required identifiers, and the event’s eligibility.

Not every lead or stage change creates a valid advertising event.

Check each integration’s logs. Queued, attempted, failed, and accepted are different states. CRM counts and advertising-platform reports can differ because of eligibility, matching, attribution windows, timing, and the metric being compared.

These signals can help ad platforms optimize toward useful outcomes rather than form fills alone. They do not guarantee lower costs, higher returns, or a particular conversion rate.

  • Use an agreed test workflow and the provider’s supported testing controls.
  • Confirm the intake retained the expected source context.
  • Confirm the mapped milestone means the event you intend to send.
  • Review identifiers, values, currency, and consent.
  • Verify the delivery result before depending on it in a live campaign.

Do not upload real customer data solely to create a website demonstration.