# Zepto Keyword Rank Tracker (`ikmal_suzali_atr/rank-zepto`) Actor

Organic + sponsored (ad) rank per keyword x store location on zepto. Dual-mode: the same capture\_many() runs in the ATR rank-zepto service on our servers.

- **URL**: https://apify.com/ikmal\_suzali\_atr/rank-zepto.md
- **Developed by:** [AtTheRate AI](https://apify.com/ikmal_suzali_atr) (community)
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Zepto Keyword Rank Tracker

Captures the full Zepto search results slate for a keyword in a specific Indian location, with every product's rank, the sponsored slots marked, and the brand sponsoring each one. Quick commerce is store level, so each pincode resolves to the store serving that area.

### What you get

- One row per search result position: `position`, `product_id`, `name`, `brand`, `price`, `mrp`, `in_stock` and `inventory`.
- `is_sponsored` on paid slots, read from Zepto's own sponsored marker, with `ad_campaign_id` carrying the sponsoring brand Zepto names on the tile.
- Full location context on every row: `location_label`, `pincode` and `store_id`.
- `captured_at` on every row, so a time series can be built by appending runs.
- Ranks for the whole slate, not just one brand, so competitor rank and ad share stay derivable.

### Input

Give the keywords and at least one Indian pincode.

```json
{
  "keywords": ["atta"],
  "locations": [
    {
      "lat": 28.4595,
      "lon": 77.0266,
      "label": "Gurgaon-DLF",
      "pincode": "122002"
    }
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  },
  "pages": 1
}
```

- `keywords` (required): search terms to rank. Duplicates are ignored.
- `pincodes`: Indian 6-digit pincodes, for example `["122002"]`. Each is resolved to coordinates and Zepto picks the store serving that point.
- `locations` (advanced): exact store targets as `{"label","lat","lon","pincode"}`.
- `pages`: accepted for consistency with the other rank trackers. Zepto returns the whole slate in one response, so raising it does not fetch more.
- `proxyConfiguration`: egress for the run. An Indian residential proxy is the default and is required.

### Output

One dataset row per search result position, per keyword and location.

```json
{
  "captured_at": "2026-09-11T09:02:23+00:00",
  "platform": "zepto",
  "keyword": "atta",
  "location_label": "Gurgaon-DLF",
  "pincode": "122002",
  "store_id": "b4dc8d65-ed2e-4142-81b6-373982b13500",
  "position": 1,
  "is_sponsored": true,
  "ad_campaign_id": "Aashirvaad",
  "product_id": "1ea1cff7-e7e1-529c-b74f-08e9a60ea4a6",
  "name": "Aashirvaad Select | Pure MP Sharbati Wheat Atta for Soft Makhmali Rotis",
  "brand": "Aashirvaad",
  "price": 310,
  "mrp": 412,
  "in_stock": true,
  "inventory": 2
}
```

Live runs of one keyword returned 34 rows with 4 sponsored in Gurgaon, and 37 rows with 7 sponsored for pincode 122002. `ad_campaign_id` is null on organic rows, and on Zepto it carries the sponsoring brand from the "Sponsored by" line.

### Use cases

- Keyword rank tracking for your own SKUs, city by city, from `keyword`, `position` and `location_label`.
- Ad-slot share: how many of the top positions carry `is_sponsored` true, and which brands hold them.
- Competitor share of search, counting `brand` across the slate.
- Price and MRP monitoring at rank, plus availability alerts from `in_stock` and `inventory`.

### Notes and limits

- An Indian residential proxy is required. Zepto's protection layer rejects datacenter and foreign addresses outright, and there is no direct mode.
- Only about one residential exit in three clears Zepto's challenge, so the actor retries a location on fresh sessions several times before calling it blocked. A capture can take a minute or two.
- The whole result slate for a keyword arrives in one response, so `pages` has no effect.
- If a session dies part way through a keyword list, the remaining keywords resume on the next session, so a mid-run failure does not truncate your data.
- A keyword that matches nothing is reported as an empty capture with a warning, never as a clean zero.
- India only.

### FAQ

**Do I need a proxy?** Yes, an Indian residential one, which is the actor default. Nothing else works here.

**How many results can I get?** The full slate Zepto returns for the keyword at that store. Live tests returned 34 and 37 rows for a grocery term.

**Does it need a login or an API key?** No.

**How does a pincode pick a store?** The pincode is resolved to coordinates, the storefront is loaded at that point, and Zepto's own session decides the serving store. That store comes back in `store_id`.

**Why is a run slower than other trackers?** Zepto challenges most exit addresses, so the actor spends time finding one that clears. That is the difference between a real local slate and an empty run.

# Actor input Schema

## `keywords` (type: `array`):

Search keywords to rank (required). Duplicates are ignored.

## `pincodes` (type: `array`):

Indian 6-digit pincodes to capture ranks for, e.g. 122002. Each is resolved to coordinates and the platform picks the store serving it; pincodes with no store nearby fail loudly rather than logging another city's ranks.

## `pages` (type: `integer`):

Result pages to walk per keyword.

## `proxyConfiguration` (type: `object`):

On the Apify platform this decides egress (residential IN recommended; these platforms block datacenter IPs). On our servers it is ignored and our own residential proxy is used.

## `locations` (type: `array`):

Optional instead of pincodes: exact store targets \[{"label":"Gurgaon-DLF","lat":28.4595,"lon":77.0266,"pincode":"122002"}].

## Actor input object example

```json
{
  "keywords": [
    "shampoo",
    "atta"
  ],
  "pincodes": [
    "122002"
  ],
  "pages": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "IN"
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One row per search result position.

## `summary` (type: `string`):

Counts for the run: what was requested, captured, skipped and failed.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "shampoo",
        "atta"
    ],
    "pincodes": [
        "122002"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ikmal_suzali_atr/rank-zepto").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "shampoo",
        "atta",
    ],
    "pincodes": ["122002"],
}

# Run the Actor and wait for it to finish
run = client.actor("ikmal_suzali_atr/rank-zepto").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "shampoo",
    "atta"
  ],
  "pincodes": [
    "122002"
  ]
}' |
apify call ikmal_suzali_atr/rank-zepto --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ikmal_suzali_atr/rank-zepto"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/6GNGDCxScW3dml9bb/builds/ahSWdaYdLUSmZBm7U/openapi.json