Give each source a clear role
Advertising provides spend and campaign identifiers. Forms or a CRM supply leads and their origins. Stripe supplies available payment and refund records. A tool such as Fathom supplies a recording or transcript, not proof of collected revenue.
The connector catalog lists supported tools. Availability depends on configuration and account permissions. Assisted setup validates the journey rather than assuming that a logo means a connection is already operational.
Identity is as important as connectivity
Keep a consistent email from form to payment when possible. Preserve lead, contact and payment identifiers. Check phone formats and country codes. Two people can share a name, and one person can use several emails.
When a payment uses a different email, verify the match against source records. A similar first name or a nearby date should not be enough to present attribution as certain.
Check a complete journey before onboarding a team
Use an authorized test journey with clearly labelled test data. Inspect each step and check for duplicates before relying on aggregate reports.
- Create or import a test lead with a known origin.
- Verify the identifiers and contact details retained after booking.
- Check that the available call belongs to the correct person.
- Check payment in the appropriate test mode without mixing test and production.
- Inspect match evidence and amounts, then exclude test data from business reporting.
Check freshness beyond connection status
Check the last synchronization and errors too. Provider delays, expired permissions or a missing event can interrupt the journey. Distinguish a connected source, a completed import and a successfully matched record.
A temporary provider limit and a revoked permission need different responses. Read the connection message before retrying or reconnecting; reconnecting cannot replace missing origin evidence.
Find the missing link without reconnecting every tool
Start with one person whose journey you know and inspect sources in order. This separates collection problems, synchronization delays and missing attribution evidence.
- The lead is missing in the source: check the form and its destination before investigating WhoBuys.
- The lead exists but its origin is missing: check the ad identifiers and parameters supplied with that lead.
- The payment is in Stripe but absent from WhoBuys: check the connected account, scope and last synchronization.
- The payment is imported but unmatched: compare identifiers and contact details, then resolve ambiguities.
- Totals differ: check dates, refunds and the exclusion of test data.