In Pakistan, a placed order is not a sale. Many online stores take most of their orders as cash on delivery, and a share of those orders are cancelled on the confirmation call, refused at the door or returned. Yet most GA4 and Meta setups send every placed order as a purchase. The result is revenue reports that look better than the bank account and ad campaigns that learn from the wrong people.
This guide explains how to track cash on delivery orders in GA4, Meta Ads and Google Ads so your reports and your campaigns reflect what was actually paid.
Why COD breaks standard ecommerce tracking
Standard ecommerce tracking was designed for card payments. The customer pays, lands on the thank-you page, and the purchase event fires. Money and event arrive at the same moment.
With COD, the thank-you page only means the customer promised to pay. The money arrives days later, if at all. When that promise is reported as a purchase, three things go wrong:
- GA4 revenue is inflated. Refused and returned orders stay in your revenue reports.
- ROAS looks better than it is. Meta and Google Ads report returns on orders that never paid.
- Campaigns optimise for the wrong buyers. Meta looks for more people like the ones who place orders and refuse them.
Step 1: Record the payment method on every purchase
Start by sending the payment method with each purchase event. In Shopify and WooCommerce the payment method is available on the order, so it can be pushed to the dataLayer and sent to GA4 as an event parameter such as payment_type with values like cod, card, jazzcash, easypaisa or bank_transfer.
Register payment_type as a custom dimension in GA4. You can now split revenue into prepaid and COD in any report, which is often the first time a store owner sees how much of their revenue depends on delivery.
Step 2: Separate placed orders from confirmed sales
The next step is to stop treating every placed order as the same kind of event. A practical structure for a Pakistani store looks like this:
| Stage | Event | Used for |
|---|---|---|
| Order placed (COD) | purchase with payment_type = cod, or a separate order_placed event | Reporting only |
| Order confirmed by call or WhatsApp | order_confirmed | Optional optimisation event |
| Order delivered, or prepaid order | The main purchase conversion in Meta and Google Ads | Bidding and ROAS |
Prepaid orders through cards, JazzCash or Easypaisa can count as purchases straight away, because the money has moved. COD orders only become a bidding conversion when they are delivered.
Step 3: Send delivered orders back to Meta and Google Ads
Delivery happens days after the website visit, so it cannot be tracked by a browser pixel. It has to be sent from the server. There are two common ways to do this:
- Meta Conversions API. When the order status changes to delivered in your store, a server event is sent to Meta with the order ID, value and hashed customer details such as phone number. Meta matches it to the person who clicked your ad.
- Google Ads offline conversions. The Google click ID (gclid) is saved with the order, and delivered orders are uploaded to Google Ads, either automatically through an integration or as a scheduled file.
If your courier updates delivery status in your store, this can run automatically. If delivery is marked by hand, a daily routine works too. What matters is that the event campaigns optimise on is the one that means money received.
Step 4: Deduplicate browser and server events
Most stores run the Meta Pixel in the browser and the Conversions API on the server. If both send a purchase for the same order without a shared ID, Meta counts it twice. Use the order ID as the event_id in both the browser and server event, and Meta will keep only one. The same rule applies to TikTok and Snapchat if you advertise there.
Step 5: Fix wallet and bank redirects
Prepaid buyers who pay through JazzCash, Easypaisa or a bank payment page leave your site and come back. If those domains are not on GA4’s list of unwanted referrals, GA4 starts a new session and credits the sale to the payment page instead of your campaign. Add each payment domain to the referral exclusion list and test a real payment before relying on the data.
What to report each month
Once COD is tracked properly, three numbers become useful for every campaign: orders placed, orders delivered and the delivery rate between them. A campaign with cheap orders and a low delivery rate is often worse than a campaign with expensive orders that are almost all delivered. Without this split, you cannot see the difference.
Frequently asked questions
Should I stop sending COD orders to Meta completely?
No. Send them as a separate event for reporting, so you can see volume. Just do not make them the main conversion your campaigns optimise for.
Will Meta have enough data if I only send delivered orders?
Delivered orders arrive later and in smaller numbers. If volume is low, an order_confirmed event after the confirmation call can be a good middle step for optimisation.
Does this work on Shopify and WooCommerce?
Yes. Both platforms store the payment method and order status, which is all this setup needs. Custom stores need the same two fields available to the tracking setup.
We set up COD, prepaid and WhatsApp tracking for stores across Pakistan. See our performance tracking services in Pakistan for Meta CAPI and Google Ads, or our GA4 consultant service in Pakistan if your GA4 reports are the starting point. You can also send us your store for a free review.



