What happens when a lead is submitted
When a Meta Lead Form submission is received, SideKick captures the lead, normalizes the available contact and campaign data, and associates it with the correct workspace and campaign context.
That normalized lead record is then delivered to the connected CRM providers for the workspace.
- 1Meta lead is received by webhook or recovery sync.
- 2SideKick normalizes the lead fields and campaign context.
- 3The workspace's connected CRM providers are identified.
- 4SideKick attempts delivery to each connected provider.
- 5Delivery success or failure is logged independently per provider.
What lead data is included
The internal delivery model keeps enough context for safe delivery and troubleshooting without adding unnecessary CRM complexity to the campaign workspace.
- Workspace ID
- Campaign ID
- Template ID when available
- Meta lead ID
- Meta form ID
- Meta page ID
- Name, email, and phone when available
- Custom answers
- Source and created time
How multi-CRM delivery works
If a workspace has multiple CRM connections, SideKick attempts delivery to all connected CRM providers instead of forcing a single default selection.
A delivery failure in one CRM does not block successful delivery in another. Each provider keeps its own delivery record and retry status.
Retries, failures, and recovery
If delivery fails for a provider, SideKick logs the failure and keeps it retryable. This prevents silent lead loss and makes it easier to recover from temporary provider or auth issues.
Recovery sync and recent delivery status in Workspace Settings help you monitor whether lead-form handoff is working as expected.