WooCommerce Conversion Value Adjustments for Google Ads Refunds
Google Ads purchase tracking often records the original WooCommerce order value, but refunds, cancellations, partial refunds, and chargebacks change the actual value. Conversion value adjustments can keep reporting and bidding closer to real revenue.
Use this for WooCommerce stores that import purchase conversions into Google Ads and later issue refunds, partial refunds, cancellations, exchanges, or post-purchase value changes.
Quick answer
WooCommerce Conversion Value Adjustments for Google Ads Refunds should be handled with a narrow evidence-first workflow: match order id, classify adjustment, build upload row, then verify the result before making broader changes.
What to check first
- Use a stable order ID or transaction ID that matches the original Google Ads conversion.
- Record refund amount, refund time, original value, currency, and conversion action.
- Separate full retractions from value restatements for partial refunds.
- Run uploads with partial failure handling so one bad row does not hide the rest.
- Compare adjusted Google Ads revenue to WooCommerce net order revenue.
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 order ID | Use a stable order ID or transaction ID that matches the original Google Ads conversion. | Every adjustment maps back to a real WooCommerce order. |
| Classify adjustment | Record refund amount, refund time, original value, currency, and conversion action. | Partial refunds reduce value instead of retracting the whole conversion. |
| Build upload row | Separate full retractions from value restatements for partial refunds. | Upload diagnostics show accepted rows and rejected rows. |
| Handle partial failures | Run uploads with partial failure handling so one bad row does not hide the rest. | Adjusted ad revenue is closer to net store revenue. |
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
adjustment_event:
order_id: WC-10452
conversion_action: purchase
adjustment_type: RESTATEMENT
original_value: 249.00
adjusted_value: 129.00
currency: USD
reason: partial_refund
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 order ID
- Classify adjustment
- Build upload row
- Handle partial failures
- Reconcile revenue
Production verification checklist
- Every adjustment maps back to a real WooCommerce order.
- Partial refunds reduce value instead of retracting the whole conversion.
- Upload diagnostics show accepted rows and rejected rows.
- Adjusted ad revenue is closer to net store revenue.
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 Google Ads revenue tracking.