The form works. The CRM works. The dashboard works. Somehow, someone still spends Monday morning moving numbers between them. Your stack can contain capable tools and still fail to support a dependable business process.
Marketing stack integration is the work of making records, events and responsibilities agree across those tools. It starts with definitions and ownership. Another subscription is optional.
Different numbers are a clue, not a diagnosis
An analytics event, a form submission and a qualified CRM lead are different units. Advertising platforms may also use different attribution windows or modelling. A mismatch does not automatically prove tracking is broken, and integration does not make every platform report identical totals.
Write down what each number means before trying to reconcile it. Specify the event, date range, timezone, attribution basis, filters and duplicate rules. Then distinguish expected differences from missing or repeated records.
Google’s GA4 event documentation explains how events and parameters represent interactions. Business stages such as “sales-qualified lead” still need a consistent definition in your CRM and reporting process. Our marketing attribution guide covers the separate question of assigning credit.
Follow one lead through the entire journey
Submit a controlled test enquiry and follow it from the form to the CRM, notification, follow-up task and reporting view. Check each transition, including the source value, timestamp, owner and final status. A successful form confirmation does not prove the CRM handoff completed.
Repeat the test with a missing optional field, a duplicate delivery and an unsupported source value. The goal is to learn how the system behaves when input is ordinary and imperfect.
| Field | Example owner | Rule to document |
|---|---|---|
| Submission ID | Form/backend | Stable across integration retries |
| Original source | Acquisition capture | Do not overwrite with each later visit |
| Lead owner | CRM routing | Fallback queue when no rule matches |
| Lifecycle stage | Sales process | Allowed transitions and authorised updates |
Give each important field an owner
Two-way synchronisation sounds convenient until both systems overwrite the same field. Decide which application owns each value and which applications may read or update it. Document how conflicts are resolved.
Use a shared record identifier where appropriate, and explicitly map field types and allowed values. “UK,” “United Kingdom” and “GB” may be equivalent to a person but different inputs to a routing rule. Normalise them at a defined point.
Native connectors can be sufficient when they support the required fields, timing and controls. Custom orchestration is useful when the workflow needs logic they do not expose. Evaluate the gap instead of treating custom code as automatically superior.
Make failed handoffs visible
A connector marked “connected” is not evidence that today’s records arrived. Log delivery outcomes and monitor failures, unexpected volume changes and records left without owners. Assign someone to the exception queue.
n8n’s error-handling documentation describes workflows that respond to execution failures. Combine alerts with enough context to retry safely. Replaying an event should not create another contact or send the same acknowledgement twice.
Fix one commercially important path first
Start with the gap affecting an actual decision or customer handoff. A missing lead owner may matter more than a dashboard’s cosmetic inconsistency. Write an acceptance test: when this event occurs, this record should arrive with these fields and this owner within an agreed time.
Then measure completion rate, duplicate rate, unresolved exceptions and manual reconciliation time. If the path is stable, expand to another. A big integration diagram is not a result unless the journeys through it work.
For measurement failures, start with the conversion tracking diagnostic. For the operational handoff, explore OJC Labs’ CRM integration and email systems and automation and data integration.
Bring one broken journey to OJC Labs: what starts it, where it should end and the point where a person currently has to intervene.