Google Ads Offline Conversion Adjustments for WooCommerce Refunds
If Google Ads receives the original WooCommerce purchase but never receives refunds or cancellations, bidding and reporting can overstate value. Offline conversion adjustments need a reliable match to the original transaction.
Use this for WooCommerce stores with refunds, partial refunds, cancelled orders, post-purchase value changes, or offline Google Ads purchase uploads.
Quick answer
Google Ads Offline Conversion Adjustments for WooCommerce Refunds should be handled with a narrow evidence-first workflow: match original conversion, classify refund, build adjustment row, then verify the result before making broader changes.
What to check first
- Use the same order ID, transaction ID, or conversion identifier that created the original purchase conversion.
- Separate full retractions from partial value restatements.
- Record refund amount, adjusted order value, currency, refund time, and reason.
- Do not upload an adjustment until the original conversion is known and matched.
- Compare adjusted Google Ads revenue to WooCommerce net revenue by date range.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|---|---|
| Match original conversion | Use the same order ID, transaction ID, or conversion identifier that created the original purchase conversion. | Every adjustment maps to a real WooCommerce order and original conversion. |
| Classify refund | Separate full retractions from partial value restatements. | Partial refunds reduce value instead of retracting the whole sale. |
| Build adjustment row | Record refund amount, adjusted order value, currency, refund time, and reason. | Full cancellations retract or zero out value as intended. |
| Upload after match | Do not upload an adjustment until the original conversion is known and matched. | Google Ads adjusted value matches WooCommerce net revenue more closely. |
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
conversion_adjustment:
order_id: WC-20391
original_value: 299.00
adjusted_value: 179.00
currency: USD
adjustment_type: RESTATEMENT
refund_time: 2026-06-30T15:18:00Z
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Match original conversion
- Classify refund
- Build adjustment row
- Upload after match
- Reconcile net value
Production verification checklist
- Every adjustment maps to a real WooCommerce order and original conversion.
- Partial refunds reduce value instead of retracting the whole sale.
- Full cancellations retract or zero out value as intended.
- Google Ads adjusted value matches WooCommerce net revenue more closely.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, fix WooCommerce refund attribution.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
- WooCommerce draft order Google Ads purchase attribution
- WooCommerce purchase event deduplication GA4 Ads