Align
Confirm time zones, attribution windows, event definitions and export coverage.
LEAD DATA · EVIDENCE · NEXT STEPS
Compare lead and CRM exports. See duplicates, missing matches and value differences in one clear evidence log.
For small performance agencies. A new service in validation.
01 / THE SAMPLE
Real checks. Constructed records.
Synthetic data · USD · 1–7 Sep 2026 UTC
| Event | Finding | Observed difference | Next check |
|---|
Original synthetic exports. No customer records, account access or uploads are used.
An unmatched record is a question to investigate. It does not establish a lost sale, wasted ad spend or a broken tracking system.
These exports describe the same event type with a shared account and event ID. Different attribution models or export definitions would need review before comparison.
The sample contains one implicit account; records match on event_id within that account. The delivery tool uses account_id + event_id for multiple accounts. Duplicate keys are excluded from one-to-one comparisons. Unique shared events are compared by amount in USD. Source-only and CRM-only records are counted separately.
The original sample has 7 source rows, 6 CRM rows, 1 duplicate key, 1 source-only key, 1 CRM-only key and 1 amount mismatch. The corrected sample is a separate synthetic fixture: a duplicate is removed, missing records are added and a value is aligned. It is not a customer outcome.
02 / THE PILOT
Start with one account.
Decide what comes next from the evidence.
$500USD · one time
First report within five business days after scope, authorizations and usable data are confirmed.
Start with an email scope review. The brief is not an order or booking. No payment is collected here.
Live tag testing, test form submissions, ad-account changes, production fixes, extra connectors and ongoing monitoring. Export reconciliation alone does not certify GA4, Ads or a CRM implementation.
Proposed monitoring: $790/month for up to five standardized accounts, four scheduled reviews per month and up to three hours of review work. Offered only if the pilot establishes a repeat need. Extra work requires a separate scope.
03 / THE PROCESS
Confirm time zones, attribution windows, event definitions and export coverage.
Find duplicates and compare records with the same stable identifier.
Separate verified issues from expected differences and open questions.
Agree the next check. Production changes require explicit client approval.
BEFORE WE START
Pseudonymous event identifiers, dates, status and values. Exclude names, email addresses, phone numbers, recordings and sensitive fields. A secure transfer method and processing terms must be agreed before customer data is shared. Pseudonymous data may still be personal data.
Not always. Consent, attribution rules, time zones, interaction dates, processing delays and event definitions can produce valid differences. The report records these limits and does not treat every discrepancy as an error.
No. It demonstrates a narrow reconciliation method with constructed data. There are no customer case studies or revenue results yet. A paid pilot must establish usefulness and delivery cost.
The service works with agreed exports from your existing tools. Tool subscriptions remain yours. API connections and production access are outside the initial export pilot.
LET’S START WITH SCOPE
Share your lead source, CRM, approximate row count and the question you need answered. A website link or field names are enough to start.
Our email contact is being updated. Please check back shortly.
Sample report · PDF