Your ROAS is wrong if RTO never reaches Meta

Tell me what’s your ROAS after RTO(rendered).mp4

📦 For anyone running COD in India, this one is worth five minutes.

Ads Manager says ROAS 3. If 35 percent of those orders come back undelivered, your real ROAS is closer to 1.9.

The reporting gap is the smaller problem. The bigger one is what Meta does with it.

Meta counts an order the moment it is placed, not after it is paid. RTO never gets reported back to the ad platform. So the algorithm registers a conversion, concludes that audience was a good bet, and goes looking for more people exactly like them. More COD orders, more refused deliveries, more packets riding back to your warehouse at your cost.

It is not a bad campaign. It is a campaign trained on the wrong outcome.

The fix sits at the data layer:

Track RTO at the product level, because some SKUs return far more than others and blended RTO hides which ones.

Send delivery-confirmed or RTO-adjusted events back to Meta instead of just “order placed”, so the signal the algorithm optimises against is money that actually landed.

Then run reported ROAS and ROAS after RTO side by side. The gap between those two columns is your real margin leak, and most brands have never put them next to each other.

Start free: https://app.customerlabs.com/signup/?utm_source=circle&utm_medium=community&utm_campaign=rto_roas_reel

Two questions for the group: what is your current RTO rate, and has anyone here already moved to a delivery-confirmed event? Curious how much your CPA shifted after the switch.

#RTO #CODOrders #MetaAds #1PDOps #EcommerceMarketing