When an advertising platform shows leads but the CRM does not, trace each handoff before reconnecting everything. A reported conversion, a submitted form, a delivered integration message, and a created CRM record are separate pieces of evidence.
Find the first boundary where the expected record is missing. That is more reliable than repeatedly refreshing connections and hoping the count changes.
Confirm the source outcome exists
Identify whether the source is a website form, a platform form, a call, or an imported event. A campaign's conversion count may include an interaction that was never intended to create a CRM record.
For a website, confirm that the server accepted the inquiry. For a platform form, use the authorized source interface to verify the actual submission. Avoid treating an aggregate chart as proof that a particular customer's record exists.
Use a labeled test record where possible. Record non-sensitive identifiers and timestamps rather than copying personal details into a shared debugging document.
Trace the handoff in order
| Boundary | Evidence to request |
|---|---|
| Source acceptance | A successful submitted record or request receipt |
| Integration receipt | An acknowledged message or delivery log |
| Field validation | Accepted required values or a clear rejection reason |
| CRM creation | The resulting record identifier |
| Assignment | Correct workspace, pipeline, and owner |
| Notification | Delivery status to the responsible team |
A notification failure is different from a missing CRM record. A record assigned to the wrong pipeline is different from an integration that never received it. Search the appropriate authorized view before assuming the data was lost.
Check configuration without exposing secrets
Confirm the selected account, form, workspace, and destination. Review whether permissions expired or the integration was configured for an older form. Check required-field mappings and whether a newly required CRM field is causing rejections.
Do not paste tokens into support chats or public logs. Use the provider's supported connection process, and have an authorized administrator handle permission changes. Available access is not permission to move leads into an unrelated workspace.
For measurement diagnostics, a tag test may help verify the expected website event, but it does not verify the downstream CRM handoff. Google's Tag Assistant troubleshooting guidance.
Recover records carefully
Before replaying a failed batch, establish which records were already created. Match on stable source identifiers where supported and retain the original outcome time separately from the recovery time.
If delivery status is unknown, inspect the destination first. Blind retries can create duplicate inquiries and multiple sales follow-ups. Use the connector's documented retry or backfill process, with an owner-approved scope and a verification sample.
Record how many source inquiries were expected, recovered, already present, or still unresolved. Do not claim complete recovery from a single successful test. If the source no longer retains the missing records, explain that limitation instead of inventing them.
Prevent a silent recurrence
Choose an owner for the handoff and an alert for failed delivery or unexplained inactivity. An empty day can be normal, so the alert should provide context rather than automatically declaring an outage.
Include the integration in the weekly audit and repeat a controlled test after form, permission, or routing changes. Keep a short recovery runbook with the relevant system owners.
How Omesta helps with checking the boundary between ads and your CRM
Use Omesta’s integration settings to confirm the sources and account context available for review. That can help narrow the investigation before anyone changes a campaign. It does not prove that every lead was delivered, nor does it authorize a bulk replay. Follow the source-to-destination checks above and recover missing records with appropriate access and deduplication.
Explore the AI ad-management workflow for current capabilities and the pricing page for plan limits.
Frequently asked questions
Should I disconnect and reconnect first?
Not automatically. Reconnection may not repair rejected fields or wrong routing, and it can complicate diagnosis. Identify the failing boundary first.
Does a successful webhook mean the sales team received the lead?
No. It may confirm one delivery step. Verify CRM creation, assignment, and the notification or task the team relies on.
Can I resend every historical lead to be safe?
That risks duplicates and unnecessary exposure. Use a bounded, authorized recovery process that checks what already arrived.
