How to Track Leads from Different Advertising Platforms
Combine paid-platform leads in one consistent ledger. Keep source data, remove duplicate enquiries and compare qualified leads and customers.
Track leads from different advertising platforms by sending website enquiries and native lead-form submissions into one controlled ledger or CRM. Keep each platform’s source, campaign and ad identifiers, give every genuine lead a stable record, and use the same qualification and sales stages across channels. Deduplicate people before comparing lead cost or paid outcomes.
Niwa helps visitors on your WordPress website understand products and services and reach an enquiry or booking step. That website assistance should feed the same measurement process as other lead routes. See how Niwa works to identify the customer actions you need to record, rather than treating every chat opening as a new lead.
Separate the lead route from the advertising source
An advertising source describes where someone came from. The lead route describes how they contacted you. A person may arrive from paid search and then use a website form. Another may submit a platform’s native form without visiting the site at all.
Keep both fields. Otherwise native-form leads vanish from website-only analytics, while website forms and phone calls appear to be competing sources even when the same campaign produced them.
Useful route values include website form, native lead form, phone call and completed website booking. Keep a conversation, a request and a confirmed reservation separate when they are different business actions.
Use a common record structure
You do not need to replace every platform report. You need a common business record that lets the team compare like with like.
| Field | Purpose |
|---|---|
| Lead ID | Stable reference through follow-up |
| Created date | When the enquiry entered the business |
| Source and route | Platform plus method of contact |
| Campaign and ad ID | Link to the creative and spend |
| Platform lead ID | Native-form identity, where available |
| Qualification status | Genuine, duplicate, unsuitable or qualified |
| Owner and next action | Accountability for follow-up |
| Payment reference and value | Connection to actual paid work |
Use appropriate access controls for private contact information. Shared reporting exports usually need campaign and outcome data rather than complete customer messages or phone numbers.
Bring in each route deliberately
For website leads, tag incoming ad links consistently and capture the applicable source fields in the lead record. Google’s UTM documentation explains the campaign fields. Confirm successful submission rather than recording every attempt as a lead.
For native platform forms, use the platform’s supported export or approved CRM connection. Preserve its lead and campaign identifiers. A UTM link on the website cannot label a native form that never opened that website.
For calls, use an eligible call-tracking implementation or a controlled manual record. For WhatsApp assistance that continues to a website booking, measure the confirmed reservation on the website. Do not infer a booking merely from a messaging conversation.
Test each route with a clearly marked sample. Check its arrival, owner assignment and source data in the destination system. Seeing a lead in the platform does not prove that your team received it.
Deduplicate without erasing the journey
The same person may submit a native form and later a website enquiry. Use a controlled identity match where appropriate, with human review of ambiguous cases. Retain both interactions under the appropriate person or opportunity record instead of counting two acquired customers.
Do not merge unrelated people simply because they share a company, surname or household phone. Repeat enquiries may also concern genuinely separate jobs. Keep a record of the match decision so a correction can be made later.
No language keyword detector is needed to decide whether an enquiry is useful. Qualification follows the business’s service, location, contactability and purchase requirements, applied with context across languages.
Compare qualified leads and paid customers
Suppose search produces 20 submissions and social produces 40. After removing duplicates and unsuitable requests, there are 12 qualified search leads and 10 qualified social leads. Those are illustrative figures, but they show why raw submissions alone can mislead.
Keep raw submissions, genuine leads, qualified opportunities and paying customers as separate columns. Use the same spend period and maturity window for each source. A campaign launched this week should not be compared with a six-month-old cohort as though both had equal time to close.
When a business uses offline conversion feedback, Google’s offline measurement guidance describes sending later outcomes through a supported connection. That feedback is a separate implementation. Putting records in a spreadsheet does not automatically send them to an advertising platform.
Give the team a weekly operating view
Review missing source fields, unassigned leads, overdue follow-up and paid outcomes. An unknown source should stay unknown until evidence resolves it. Guessing a platform makes the report tidier but weakens the next budget decision.
Niwa can support the website part of this workflow with accurate customer answers and a useful next step. Follow the Niwa setup guidance and test the actual enquiry or booking route.
Existing WordPress owners can install the standalone plugin. Niwa Business is USD 150 and includes a custom WordPress website or migration, hosting, maintenance and AI adaptation. Contact Niwa with your lead routes and current sales records to discuss the relevant website workflow and measurement requirements.
