Automatic Lead Attribution: Keep the Source Connected
Understand how Convertly retains available campaign context on incoming leads, why original source matters, and what to test before trusting attribution reports.
An enquiry can start with an ad, continue through a phone call, and end in a WhatsApp conversation. If the original source disappears along the way, marketing sees the beginning and sales sees the ending without a dependable connection between them.
Convertly’s supported intake can retain valid attribution supplied with the lead. That gives the sales record a better starting point, but it is important to distinguish information captured automatically from information that was never available.
Understand the layers of source information
A source label explains a broad origin, such as a website or advertising channel. Campaign parameters can describe the campaign, medium, or creative context. Supported advertising identifiers can help connect an eligible later outcome to the relevant platform.
These fields serve different purposes. A record labelled “Google Ads” does not necessarily contain everything required for a conversion upload. Likewise, a landing-page address alone may not identify the campaign that brought the visitor there.
Keep built-in source and advertising fields in their intended places instead of creating competing custom-field versions of the same information.
Check attribution at the point of entry
Leads can enter through native forms, connected Meta Lead Ads, the API, compatible webhooks, imports, or manual entry. Each route has different information available to it.
For a website form, review the embed and tracking setup. For an external connection, check what the sender supplies and what the integration retains. Capture can depend on visitor consent, browser or platform restrictions, and configuration.
Missing identifiers cannot always be reconstructed after the enquiry arrives. Do not fill them with guessed values to make a report appear complete.
Keep the original source through follow-up
When a teammate calls or messages a lead, record that activity without rewriting a known original source.
For example, a lead may arrive from an advertising campaign and later ask a question through WhatsApp. WhatsApp is then part of the conversation history; it does not automatically become the acquisition source.
This distinction makes source comparisons more useful. You can examine what happened after acquisition without losing how the relationship began.
Test more than one intake path
Choose a controlled test for each important source. Inspect the resulting lead for contact details, owner, source, available campaign values, landing page, and relevant identifiers or consent context.
Repeat the check after changing a landing page, form embed, or external connection. An integration that still creates leads can nevertheless stop passing useful attribution fields if its input changes.
If reports suddenly shift, review a few individual records before deciding the campaign itself changed performance.
Separate attribution from sending conversions
Retaining source context is one job. Sending an eligible qualified-lead or won-sale event back to an ad platform is another. The second requires its own enabled connection, mappings, and eligible data.
Start with the attribution guide. When intake is dependable, read connecting Google and Meta to sales outcomes to build the return path. Better-connected records make analysis more useful without pretending every journey can be measured completely.