Key takeaway
If your ROAS is calculated on page views, you do not have ROAS. Indian D2C brands need one purchase event, server-side or enhanced conversions where possible, and a weekly check that Ads, Analytics and the shop agree on order count.
IdeaRevive has worked with eCommerce brands in India and abroad. The accounts that scale have boring tracking. The accounts that stall have three pixels firing on the same thank-you page and a dashboard nobody trusts. This is the minimum we put in before we scale Shopping or Meta catalogue ads.
Which events actually matter?
| Event | Why it exists | Common failure |
|---|---|---|
| View item | Tells the catalogue which products are seen | Fires on the collection page for every card |
| Add to cart | Shows intent | Fires twice because two apps inject it |
| Begin checkout | Separates browsers from buyers | Missing on buy-now buttons |
| Purchase | The only number ROAS should use | Fires on thank-you reloads or not at all |
What should match every week?
- Orders in the shop admin.
- Purchase events in Analytics.
- Conversions in Google Ads and Meta, after you allow for attribution windows.
If those three disagree by a wide margin, do not scale. Fix the event, the domain, or the duplicate tag. We would rather pause a week than buy fake ROAS.
What about iOS, WhatsApp and UPI checkouts?
A lot of Indian checkout journeys leave the site: WhatsApp, UPI apps, or a payment page on another domain. Browser pixels miss those. That is why we use enhanced conversions or a server-side event where the platform allows it, and why we still reconcile against the order list rather than trusting the ad manager alone.
When is catalogue advertising worth turning on?
When titles, prices and availability in the feed match the site, and purchase tracking has been clean for at least a couple of weeks. A broken feed plus a broken pixel is how you pay to advertise products you cannot fulfil.
What we will not do
- Report ROAS from view-through clicks alone as if they were sales.
- Leave two Meta pixels racing on the same shop.
- Promise a platform-average ROAS for a brand we have not measured.
What does a clean purchase event look like?
One fire per paid order, with value in the same currency as the ads account, and an order ID you can look up in the shop. If the customer lands on thank-you twice, the event must not double. If they pay on a Razorpay or PayU page and come back, the event should still fire once when the shop marks the order paid — not when the browser happens to load a pixel. That is the difference between a number you can take to a founder and a number you can only screenshot.
For India brands selling abroad, keep currency and tax rules explicit. A dollar order reported as rupees inflates ROAS until the first payout. We write the rule down in the tracking brief: which value, which ID, which refund handling. Refunds should reduce the conversion or be reconciled weekly, not ignored because the ad manager looks healthier without them.
How IdeaRevive starts an eCommerce account
- Export last month’s orders and last month’s reported purchases. If they do not roughly match, we fix tracking before we touch bids.
- Open the live thank-you page and the tag inspector. One purchase event, or we stop.
- Check the product feed titles against the site. If they differ, Shopping waits.
- Only then write the first search and shopping plan, with a 90-day review against actual orders.
This is unglamorous work. It is also why we can say we have run eCommerce for brands in India and abroad without inventing a ROAS trophy. If your current agency cannot show the three-way match, start there — not with another creative sprint.