WooCommerce draft orders are useful during checkout, but Google Ads purchase attribution should not treat every draft, failed payment, abandoned checkout, or pending order as final revenue. The conversion should be tied to the completed order state and a stable transaction ID.
Use this for WooCommerce stores where Google Ads shows extra purchases, missing purchases, wrong revenue, or a mismatch between checkout attempts and paid orders.
Quick answer
WooCommerce Draft Order Google Ads Purchase Attribution should be handled with a narrow evidence-first workflow: separate draft from paid order, choose stable transaction id, gate upload by order state, then verify the result before making broader changes.
What to check first
- Compare draft, pending payment, processing, completed, cancelled, and failed order counts for the same date range.
- Confirm the purchase tag or server upload waits for a paid order state instead of firing at the first checkout draft.
- Use the WooCommerce order ID or transaction ID consistently between browser tags, server uploads, and refunds.
- Keep consent state, click IDs, order currency, coupon, and net value with the order record.
- Reconcile Google Ads purchase count against WooCommerce paid orders, not all orders created during checkout.
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 |
|---|---|---|
| Separate draft from paid order | Compare draft, pending payment, processing, completed, cancelled, and failed order counts for the same date range. | Draft and failed orders do not create purchase conversions. |
| Choose stable transaction ID | Confirm the purchase tag or server upload waits for a paid order state instead of firing at the first checkout draft. | Paid processing and completed orders produce one conversion each. |
| Gate upload by order state | Use the WooCommerce order ID or transaction ID consistently between browser tags, server uploads, and refunds. | Google Ads transaction IDs match WooCommerce order or payment IDs. |
| Preserve consent and click IDs | Keep consent state, click IDs, order currency, coupon, and net value with the order record. | Refund or cancellation handling can find the original conversion. |
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
purchase_attribution_record:
order_id: WC-18742
checkout_state: draft_created
payment_state: processing
transaction_id: pi_3R8example
google_ads_action: purchase
upload_allowed: true
reason: paid_order_state_confirmed
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.
- Separate draft from paid order
- Choose stable transaction ID
- Gate upload by order state
- Preserve consent and click IDs
- Reconcile paid revenue
Production verification checklist
- Draft and failed orders do not create purchase conversions.
- Paid processing and completed orders produce one conversion each.
- Google Ads transaction IDs match WooCommerce order or payment IDs.
- Refund or cancellation handling can find the original conversion.
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 purchase tracking.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.