The ROAS your bank account agrees with
D2C brands — especially in India, where cash on delivery and return-to-origin are part of every order book — see ad platforms report revenue that never arrives. DataLens AI answers performance questions against your own orders, so ROAS, CAC and payback reflect delivered, paid revenue and real margin rather than what each platform claims.
What gets in the way today
- Google and Meta both claim the same order, so summed platform revenue is bigger than the bank deposit.
- COD orders that are refused or returned to origin still count as revenue in ad dashboards.
- Sale events inflate ROAS while discounts and post-sale demand dips quietly eat the margin.
What DataLens AI does for D2C brands
Revenue from your orders, not the platforms
Join Google Ads and Meta Ads spend to orders in BigQuery or a spreadsheet, so ROAS and CAC are counted once, on revenue you actually received.
RTO- and COD-aware questions
Ask for delivered ROAS, RTO rate by campaign or pincode, or prepaid versus COD mix — the SQL shows exactly which orders were counted.
Margin, not just revenue
Bring product cost, shipping and fees from a sheet or table and ask for contribution-margin ROAS and payback instead of revenue multiples.
Costs you can see
Every warehouse query shows its scan cost before it runs, with a cap that blocks expensive queries.
Questions you could ask on day one
- “What was delivered ROAS by campaign last month, excluding RTO orders?”
- “Which pincodes have RTO rates high enough that we should exclude them?”
- “How did the sale weekend affect contribution margin compared with the two weeks after it?”
- “What is our blended CAC for new customers, from our own orders?”
Which sources does it connect?
Try it on your own data
Sign in with Google to start a 7-day free trial in your own private project — no credit card. Bring your own model key (or request managed models), connect a source, and every answer arrives with its SQL.