Data availability
Every insight in this product is limited to what the four ad platforms return through their reporting APIs, plus Shiprocket's own funding and seller feeds. This page is the contract.
Connected ad accounts
146
Accounts reporting revenue
123
Accounts without purchase tracking
23
Platforms integrated
4
What each platform returns
Field-level availability, granularity, attribution window and known limits
| Platform | API | Granularity | Revenue field | Attribution | Limits |
|---|---|---|---|---|---|
| Google Ads | Google Ads API (GAQL reporting) | Campaign, ad group, ad, keyword, search term | metrics.conversions_value (needs Google tag or GA4 import) | Data-driven or last click, 30-day click window by default | Revenue only for conversion actions the seller has configured. Search-term data is redacted below a volume threshold. |
| Meta Ads | Marketing API Insights | Campaign, ad set, ad, creative | action_values[omni_purchase] and purchase_roas (needs pixel or CAPI) | 7-day click / 1-day view by default, configurable per query | Modelled and view-through conversions are included, so revenue overlaps other platforms. Breakdowns cannot be combined freely. |
| Amazon Ads | Amazon Ads API (v3 reporting) | Campaign, ad group, targeting/keyword, ASIN | attributedSales (native marketplace attribution) | 7 or 14-day post-click windows depending on report type | Covers Amazon marketplace sales only, not the seller's own store. No creative-level view for Sponsored Products. |
| Flipkart Ads | Flipkart Ads / Seller reporting | Campaign, mostly campaign-level only | revenue and units sold (marketplace attribution) | Platform-defined click window, not configurable | Little sub-campaign detail, no creative or keyword parity with Google and Meta. Marketplace sales only. |
Revenue is each platform's own attributed conversion value, on its own attribution window. Platforms can claim the same order, so cross-platform totals are indicative planning figures, not verified order revenue.
Metric provenance
Every figure in the product carries one of these three tags
Returned directly by the ad platform reporting API
Computed from platform-reported fields only
From Shiprocket's own seller and funding feeds
- SpendPlatform
- Google metrics.cost_micros · Meta spend · Amazon cost · Flipkart spend
- ImpressionsPlatform
- metrics.impressions · impressions · views
- ClicksPlatform
- metrics.clicks · clicks (link clicks) · clicks
- ConversionsPlatform
- Google metrics.conversions · Meta actions[purchase] · Amazon purchases · Flipkart units sold
- Attributed revenuePlatform
- Google metrics.conversions_value · Meta action_values[purchase] · Amazon attributedSales · Flipkart revenue — each platform's own attribution
- Platform ROASDerived
- attributed revenue ÷ spend on tracked accounts (Meta also reports purchase_roas)
- Blended ROAS (indicative)Derived
- sum of platform-attributed revenue ÷ tracked spend — platforms can claim the same order, so treat as a planning ratio
- CTRDerived
- clicks ÷ impressions
- CPCDerived
- spend ÷ clicks
- CPMDerived
- spend ÷ impressions × 1000
- CPADerived
- tracked spend ÷ conversions
- Revenue coverageDerived
- share of spend on accounts where the platform reports conversion value
- Budget made availableShiprocket
- Shiprocket marketing funding feed
- Monthly planShiprocket
- Shiprocket seller plan feed
- Deployment rateDerived
- observed ad spend ÷ Shiprocket budget made available
Not available in Phase 1
No ad platform returns these, so the product does not claim them
- Verified order revenuePlatforms report their own attributed value. Confirmed order value needs the storefront or Shiprocket order feed (Phase 2).
- Delivered revenue, RTO and returnsRequires fulfilment data linkage, not available from any ad platform.
- Margin, contribution and profit ROASNeeds product cost data from the seller's catalogue.
- De-duplicated cross-platform revenueRequires a single source of truth for orders plus a pixel on the storefront; until then cross-platform revenue is additive and overstated.
- Traffic quality and invalid click validationNeeds the mFilterIt landing-page pixel (Phase 2).
Order-level truth
The storefront pixel plus the Shiprocket order and fulfilment feed replace platform attribution with confirmed, de-duplicated, delivered revenue — and unlock RTO, returns and contribution ROAS.