Flipkart
Connect Flipkart Ads and the Seller API so Meerkats has your PLA and PCA campaigns, wallet, performance, orders, returns, settlements and FBF stock.
The Flipkart connection has two sides. Flipkart Ads gives Meerkats your Product Listing Ads (PLA), Product Contextual Ads (PCA) and display campaigns, keywords, search terms, placements and the ad wallet. The Seller side gives it listings, orders, returns and RTO, settlements and Flipkart Fulfilment (FBF) stock.
Flipkart Ads has no public API, so Meerkats reads it through the Meerkats browser extension using your signed-in Ads Manager session. The Integrations page marks Flipkart Ads as Required for Flipkart sellers because it is their sales source.
| How it connects | Meerkats browser extension |
| Reads | Campaigns, Ad groups and FSNs, Keywords and search terms, PCA creatives, Daily reports, Wallet and billing, Listings, Orders, returns, settlements, FBF inventory |
| Can change | Pause or enable a campaign or FSN; Change a campaign budget; Add or change keywords and bids; Create a PLA or PCA campaign; Price, stock or listing content |
| Refresh | On your plan's schedule, plus Resync anytime |
Before you start#
- Google Chrome or another Chromium browser with the Meerkats extension installed. Select Download extension at the top of the Integrations page.
- A Flipkart Ads Manager login for the seller account.
- Seller API credentials from the Flipkart Seller Hub (Manage Profile › API), for orders, returns, settlements and stock.
Permissions#
What Meerkats needs, and why.
| Permission | Why Meerkats needs it |
|---|---|
Flipkart Ads Manager session | Read campaigns, ad groups, FSNs, keywords, search terms, placements, wallet and reports through the extension |
Seller API: Listings | Read FSN, title, category, brand, MRP and selling price, stock, listing status |
Seller API: Orders and Returns | Read order items, cancellations, customer returns and courier RTO |
Seller API: Payments | Read settlement reports with per-order fee lines |
Seller API: Inventory | Read FBF and seller-warehouse stock per FSN |
Connect#
1. Install the extension#
- Download it
On the Integrations page, select Download extension and add it to your browser.
- Sign in to Flipkart Ads Manager
Open Flipkart Ads Manager in the same browser and sign in as usual.
2. Sync Flipkart Ads#
- Choose Flipkart Ads
In Meerkats, find Flipkart Ads under Available connectors and select Sync via extension.
- Confirm in the extension
The extension detects your Ads Manager session and asks you to confirm the seller account. Meerkats never sees your Flipkart password; the extension reads the pages your session can see.
- Wait for the first sync
Go to Data Hub › Bronze Layer, pick Flipkart and watch Sync History. Search terms sync last and take longest.
3. Add the Seller API#
- Create API credentials
In Seller Hub, go to Manage Profile › API and generate an application ID and secret.
- Paste them in Meerkats
On the Flipkart connection, open Seller API and paste the credentials. Meerkats stores them encrypted.
- Resync
Orders, returns, settlements and FBF stock arrive on the next sync. Reports and Charts › Product Revenue then shows Flipkart revenue per product.
What syncs#
| Flipkart | In Meerkats |
|---|---|
| Campaigns | Type (PLA, PCA, Display), status, budget and type, bidding (CPC or SmartROI with its target), auto or manual targeting, surface (Flipkart, Grocery, Minutes), schedule |
| Ad groups and FSNs | Ad groups, the FSNs in each, per-FSN status |
| Keywords and search terms | Keyword, match type, bid, suggested bid, status; negatives where supported; the search terms that triggered ads |
| PCA creatives | Banner asset, featured FSNs, landing target |
| Daily reports | Consolidated daily, campaign, ad group, keyword, search term, placement, FSN (consolidated and attributed), product page and display reports |
| Wallet and billing | Ad wallet balance, credits, invoices (billed vs reported spend, GST) |
| Listings | FSN, title, category, brand, MRP and selling price, stock, listing status (snapshotted each sync, so price changes become events) |
| Orders, returns, settlements | Order items with FSN, quantity, price and status; customer returns vs courier RTO with reasons; settlement fee lines (commission, collection, fixed, shipping) and payouts |
| FBF inventory | Sellable, in-transit and QC-rejected units per FSN |
Raw data lands in Data Hub › Bronze Layer. Modelled tables, with metrics defined once, are in Data Hub › Gold Layer. Every number in a report or an agent’s answer comes from a query on these tables, never from the model’s own arithmetic.
Metrics you get#
The metrics people ask for most, named as Flipkart names them. The full list, with each definition, is in the metric catalog.
Ad spendDirect revenueIndirect revenueROIViewsClicksCTRCPCConversion rateUnits soldWallet balanceRTO rateSettlement feesDays of cover
How often it syncs#
Meerkats syncs on your plan's schedule: daily on Free, hourly on the $49 plan, every 30 minutes on $149 and every 15 minutes on $399. You can run a sync at any time with Resync in Data Hub › Bronze Layer.
- Flipkart reports ROI as a multiplier (for example 4.2), not a percentage. Meerkats shows it as ROI in Flipkart reports and as ROAS in cross-platform views.
- Flipkart has no change-history API. Meerkats derives changes by comparing each sync's snapshot with the last, so a change's time is the sync that first saw it.
- The extension syncs while your browser is open and signed in. If the session expires, the connection shows needs attention until you sign in again.
What Meerkats can change#
In every connected tool, Meerkats can create, read, update and delete records, within the permissions you grant and the permissions the tool allows. These are the changes it proposes for Flipkart, and the limit that applies to each.
| Change | Limit |
|---|---|
| Pause or enable a campaign or FSN | Medium risk: always proposed for approval |
| Change a campaign budget | Down up to 20% per change; up to 50% per week |
| Add or change keywords and bids | Bid up to 15% per change; proposed for approval |
| Create a PLA or PCA campaign | Created paused; a second approval switches it on |
| Price, stock or listing content | Staged as a task for the seller-side owner, never changed by the ads flow |
How every change is governed
Every change starts as a proposal in your Inbox. Nothing changes in the connected tool until a person approves it, unless you set that rule to act on its own.
Before it runs an approved change, Meerkats re-reads the live value. If the value moved since the proposal, it asks again instead of acting on stale data.
Meerkats stores the value it replaced, so every change can be undone from Agents run history.
Anything Meerkats creates starts paused. Switching it on is a second, separate approval.
Example automations#
Type any of these on the New automation page (Automation Agents › + New Agent).
- “Email me Flipkart campaigns with ROI below 2 every morning”
- “Pause any Flipkart campaign whose ROI drops under 1.5 for three days, after I approve”
- “Alert me on Slack when the Flipkart ad wallet goes below ₹5,000”
Troubleshooting#
Sync via extension does nothing
The extension must be installed in the same browser you're using for Meerkats, and Flipkart Ads Manager must be signed in there. Reload both pages and try again.
Search terms are stale
Flipkart's search-term report is the slowest to generate. Sync History shows when it last completed. Agents that need fresh search terms wait for it rather than using old data.
Revenue differs from Seller Hub
Ads reports count attributed revenue; Seller Hub counts all orders. Compare Direct revenue in Flipkart reports to Ads Manager, and Product Revenue to Seller Hub.
Settlements are missing
Settlement reports arrive on Flipkart's payment cycle and need the Seller API connected. Check Seller API on the Flipkart connection.