Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ocular.dev/llms.txt

Use this file to discover all available pages before exploring further.

Ocular pulls Blinkit seller-reporting and ads-reporting data into your unified commerce stack — orders, GMV, listings, and inventory on the seller side, and campaigns, spend, impressions, and ROAS on the ads side. The connector is provisioned by the Ocular team because Blinkit does not expose a self-serve API for partner access.

What you get

Seller reporting (orders, GMV, listings, inventory) and ads reporting (campaigns, spend, impressions, ROAS).

How it is set up

CSM-assisted onboarding — credentials and account IDs are exchanged securely with your Ocular CSM.

​
How to enable the Blinkit integration

Blinkit does not expose a self-serve OAuth or API-key flow, so Ocular provisions the connector for you.

Reach out to your CSM

Ping your CSM in your shared Slack channel (Enterprise) or email support@ocular.dev with the subject Blinkit integration request.

Share account access

Your CSM walks you through which Blinkit seller credentials and ad-account IDs to share, and the secure channel to share them on.

Confirm data is flowing

Once provisioned, your CSM confirms Blinkit data is landing in your workspace — usually within 1–2 business days. The first full historical load can take 24–48 hours.

​
What lands in Ocular

Seller reporting

Orders, GMV, listings, inventory, fulfilment status, and city/dark-store splits.

Ads reporting

Campaigns, ad groups, spend, impressions, clicks, ROAS, and share-of-voice.
Blinkit data flows into the same models your other connectors populate — Sales Performance, P&L, and Ads Performance — so you can compare Blinkit alongside Shopify, Meta, and Google Ads without extra modeling work.
Haven’t heard back? See Working with the Ocular team for response-time SLAs and escalation paths.