First, compare the two exports for the same days and time zone
Do not compare totals from two dashboards. Export the leads from Campaign Manager for a closed range of days, and export the CRM records with a LinkedIn source for the same range, with both expressed in one time zone. Match the rows on email address, falling back to name and company where the address differs. Three groups appear: leads present in both, leads only in Campaign Manager, and records only in the CRM.
If every Campaign Manager lead has a partner in the CRM, the sync works, and the difference sits in how the totals are drawn; the last row of the table applies. If specific leads are missing from the CRM, look at what they have in common: one form, one ad account, a start date, a blank field. That shared trait points to the row. Then submit a live test lead through the affected form from a member account you control, note the time, and watch for it in the CRM. The targeting and Lead Gen Forms guide recommends this test before any campaign spends; here it becomes the probe that finds the break.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| All leads from one form or one ad account are missing; others arrive | Which ad accounts and forms the integration covers | Integration not connected to this form or ad account | Extend the integration's scope to the account and form |
| Some leads missing, all with a blank or unusual value in one field | CRM import or error log for rejected records; required fields | Field mapping misses a field the CRM requires | Map the field, or relax the requirement for this source |
| Every lead stopped arriving from a date | Who authorised the connection; user, permission and CRM changes around that date | Connection broken after a user, permission or CRM change | Reconnect under a durable owner and backfill the gap |
| Test lead arrives, then vanishes or lands on an old record | CRM duplicate and merge rules; the record history | Duplicate rules merging or discarding new records | Let new submissions create an activity or a linked record |
| No lead missing row by row, totals still differ | Time zone and day boundaries of each export | Date boundaries and time zones | Report both systems on one time zone and closed days |
Fix, verify and prevent each cause
An integration that does not cover this form
Integrations are set up for particular ad accounts and, in some CRMs, for particular forms. A new ad account, a form created after the integration, or a campaign moved between accounts can sit outside that scope, so its leads stay in Campaign Manager while everything else syncs.
Fix: open the integration's settings and add the missing account or form, using the native integrations or automation route that the targeting and Lead Gen Forms guide describes.
Verify: a live test lead from the previously missing form reaches the CRM with its campaign and form recorded.
Prevent: make "integration covers this form" a step in building any new form or ad account, and keep a list of covered forms beside the campaign plan.
A record the CRM refuses
CRMs reject records that lack a required field or carry a value in the wrong format, often silently from the marketer's side. A form that omits the company field, a phone number in an unexpected format, or a picklist value the CRM does not recognise can each stop specific leads.
Fix: read the CRM's import or error log for rejected records, then either add the field to the form and map it, or make the field optional for records from this source. The targeting and Lead Gen Forms guide lists the profile fields a form can request.
Verify: a test lead with the previously failing value arrives complete, and the error log stays empty for a week.
Prevent: when a form is edited, compare its fields with the CRM's required fields before republishing it. Where a field has to accept free text, such as job title or country, the tutorial on standardising CRM field values keeps the raw value and maps it to the CRM's picklist with a workflow instead.
A connection that died with someone's access
Many integrations authorise as a person. When that person leaves, loses their role in Campaign Manager or the CRM, changes a password under single sign-on, or the CRM's own permissions are tightened, the connection can stop without any warning in the ad account. The tell is a clean cut-off date after which nothing arrives.
Fix: reconnect the integration under an owner whose access will last, then download the leads from the gap in Campaign Manager and import them with their original submission times, within the documented retention period.
Verify: a test lead arrives, and the backfilled rows match the Campaign Manager export for the gap.
Prevent: record who owns each integration, and include the integration in the offboarding checklist for marketing and sales operations staff. The Campaign Manager setup tutorial names that owner, with the ad account's other owners and access, before any campaign spends.
A CRM that swallows new submissions
Duplicate rules exist to keep the database clean, and they can undo a sync. A new submission from someone already in the CRM may be merged into the old record, overwriting the source and date, or discarded as a duplicate, so the lead exists but no one sees a new one. The recommended lead generation setup explains why each submission needs its campaign and offer to survive the hand-off.
Fix: configure the rules so a repeat submission updates the existing contact and adds an activity or a linked lead record carrying the new campaign, rather than replacing the original.
Verify: a test lead from an address already in the CRM produces a visible new activity with the LinkedIn campaign attached.
Prevent: have the CRM owner review duplicate rules whenever a new lead source is connected.
Totals cut on different clocks
When every lead appears on both sides but the weekly totals still differ, the systems are counting on different boundaries. Campaign Manager and the CRM may use different time zones, one may date a lead by submission and the other by creation, and a report that includes today counts a day still in progress. The platform versus analytics discrepancies guide describes the same effect between ad platforms and analytics tools.
Fix: report both on one time zone, by submission date, for closed days only.
Verify: totals for the same closed range match, or differ only by leads you can name.
Prevent: write the counting rules into the reporting definition, including which date field is used and which system holds the official count.
Prevention: a live test lead before spend and a daily count check
Sync failures are cheap to catch early and expensive to discover late, because leads cool in hours and expire from Campaign Manager after the documented period. Before any new form or campaign spends, send a live test lead and confirm it arrives complete, with campaign, form and consent status. Each morning, compare yesterday's Campaign Manager lead count with yesterday's CRM records from LinkedIn, on the same time zone; any shortfall triggers a row-by-row match the same day, while the gap is small. Keep a register of integrations with their owner, scope and last test date. Where leads pass on from the CRM to a separate marketing automation platform, the guide to syncing the CRM and the marketing platform gives each synced field one owner and sets a routine for reading that second connection's error queue. Make the matched count, not either system's own total, the figure behind the programme's key indicator (KPIA metric tied directly to an objective.), and keep the campaign identifier on every record so that customer acquisition cost (CACCost to acquire one new customer.) can later be calculated by campaign. Agree with sales that the CRM is the record of truth for counting, while Campaign Manager's own AttributionAssigning conversion credit to touchpoints. figures stay an input for bidding. The recommended lead generation setup shows how same-day sync fits the wider plan, and the LinkedIn troubleshooting hub covers the separate question of whether the leads that do arrive are any good. When the counts that disagree are website conversions recorded by the Insight Tag rather than form leads, the diagnosis of LinkedIn conversions higher than the CRM shows separates view-through credit, windows, duplicate conversions and shared credit.
An accounting firm missing a fortnight of leads
An accounting firm runs Lead Gen Form campaigns for its advisory service and syncs leads to its CRM. In September the marketing report shows 64 leads in Campaign Manager and 41 in the CRM. The row-by-row match finds all 23 missing leads came from a form created on 9 September for a new tax guide; every lead from the two older forms arrived. The integration was set up in spring for named forms only. Adding the new form to the integration and sending a test lead fixes new submissions, and the 23 missing rows are exported and imported with their original timestamps. The same match turns up 3 leads present in both systems but dated a day apart, because Campaign Manager was reporting in UTC and the CRM in local time. Reporting both on one time zone closes that difference, and the morning count check is added to the operations routine.
Common mistakes
Comparing dashboard totals instead of matching rows. Assuming "connected" means every form is covered. Letting an integration depend on one person's login. Allowing merge rules to overwrite the source of a returning lead. Waiting for the monthly report to notice a gap that started on a Tuesday.
