Review a job’s correction before you send it
Reconcile canceled jobs, refunds and later value corrections against the original Google Ads import. Keep uncertain records visible.
Runs entirely in this browser. Input stays in memory until you reset or close the page. Downloaded review files include your supplied data. This tool sends nothing to Google.
1. Load the original imports and dated events
Start with the synthetic eight-job example, or load your ledger JSON. For CSV, load both supplied schemas. Use IDs rather than customer names, emails or phone numbers.
Load originals and events from CSV instead
CSV fields are this tool’s input schema, separate from Google’s adjustment template. See the included README and originals / events examples.
Review rules and supported scope
- Original status must be
imported. Each proposed event must beapprovedand repeat the original action, identity and conversion time. - A missing amount is unknown. Zero is valid. More than two decimals are held; choose your accounting rounding rule before entering the amount.
- Supported currencies: USD, EUR, GBP, CAD, AUD, NZD. Each has separate totals. Currency changes are held for a separate FX review.
- Whole-job safety rule: any bad event holds all proposed adjustments for that original. Exact retries are suppressed; conflicting retries are held.
- Events are sorted by actual time. Retraction or a zero restatement is terminal. The original import is never overwritten.
- Local safety holds: less than 24 hours since supplied import time, or at least 54 days since conversion. Confirm the actual current limits in Google; local eligibility is not checked.
- GCLID without an Order ID works only for the matching offline review path. It produces review JSON, not a CSV. WBRAID, unsupported action types and missing required Order IDs are held.
2. Check the totals and every held job
Reviewed final totals exclude held originals. They are projections for this input batch, not your live Google Ads or accounting balance.
| Local job ID | Conversion action | Original | Reviewed final | State |
|---|
Held and rejected records
Proposed correction rows in chronological order
| Event | Original | Time (UTC) | Type | Absolute value | Route |
|---|
3. Save your review, then check the native template
The review JSON contains the original ledger, proposed rows and all holds. Each CSV contains only its adjustment type and eligible Order ID rows. New conversions belong in a separate file.