For a lot of Indian manufacturers, distributors and B2B service firms, IndiaMART is the biggest lead source after referrals, with JustDial and TradeIndia close behind. Yet when I ask what those subscriptions return, the answer is usually a feeling. Leads arrive in the seller app, get called from someone's personal phone, and the few that close are recorded in Tally or a spreadsheet with no link to where they came from. Meanwhile the Google Ads and website leads sit in Zoho CRM with full attribution. This is how I bring portal leads into the same CRM, keep them clean, and measure them against what you pay, so the renewal decision is based on revenue.
Why portal leads need their own pipeline design
Marketplace leads behave differently from your own inbound leads. The same buyer often sends enquiries to several sellers at once, so speed of response matters more than usual. A single buyer may come through IndiaMART and JustDial in the same week for the same requirement, which creates duplicates. Lead quality varies widely, from serious bulk buyers to students and competitors checking prices. And there is no click ID or UTM to tie a lead to a specific ad, because the cost is a subscription or lead package, not a per-click auction. That means the tracking goal is different from paid media. You are not trying to attribute to a keyword. You are trying to answer three questions: how many genuine leads did each portal produce, how many became customers, and what revenue did those customers bring compared with the annual cost of the portal. Everything in the setup below serves those three questions.
Getting leads into Zoho automatically
Manual entry is the root of most bad portal data, because reps copy only the leads they like. The leads need to flow in on their own. IndiaMART offers a lead API for sellers, usually accessed through the Lead Manager section of the seller panel, which returns enquiries with buyer name, mobile, email where given, product, and message. Check what your subscription includes, as access and terms are set by IndiaMART. There are also ready-made connectors for Zoho CRM listed on the Zoho Marketplace, and integration platforms like Zoho Flow can poll the API on a schedule and create leads. JustDial and TradeIndia have their own lead delivery options, from email notifications to APIs depending on plan, and email-to-lead parsing in Zoho is a workable fallback where no API exists. Whatever the route, test it with real enquiries, check that the mobile number arrives in a consistent format, and confirm the original enquiry time is stored, not just the time the record was created.
Source tagging that survives reporting
Every portal lead needs two fields set at creation: Lead Source with a fixed value per portal, IndiaMART, JustDial or TradeIndia, and a second field for the lead type the portal reports, such as direct enquiry, buy-lead purchased, or call. IndiaMART distinguishes enquiries a buyer sent to you from buy-leads you purchased or consumed, and those two often perform very differently, so I keep them apart. I lock the Lead Source picklist so nobody can type variations, and I make sure the value carries over when a lead converts to a contact, account and deal. That last step is where most Zoho setups break: Lead Source is set on the lead, then lost on conversion because field mapping was never configured. Use Zoho's lead conversion mapping so the source flows into the deal, because the deal is where revenue lives. If you also run Google Ads and Meta, align the picklist with those sources so the same report can compare all channels side by side.
Deduplication and routing
Portal buyers repeat themselves, so deduplication is not optional. I use the mobile number as the primary key, normalised to a single format with the country code, and email as a secondary key where present. On each new record, the integration checks for an existing lead or contact with the same number. If one exists and is still open, the new enquiry is logged as a note or activity on the existing record instead of a new lead, and the portal is added to a multi-select field so you can see that the buyer came through more than one portal. If the existing contact is an old customer, the enquiry routes to their account owner. Routing for new leads is usually by product category or region, both of which arrive in the portal payload. Zoho's assignment rules handle this well. Add a response-time SLA: a workflow that alerts the manager if a portal lead has not been called within the agreed window, since slow response on a lead the buyer sent to five sellers is the most common reason portal ROI looks weak.
Qualification stages your team will actually use
Portal leads need a quick triage stage that your own inbound leads might not. I add a short set of statuses: junk or not a buyer, not a fit, genuine requirement, quoted, and then the normal deal stages. Junk and not-a-fit should require a reason from a picklist, such as student, competitor, wrong product, location not served, or price shopper. That reason field turns out to be one of the most useful things in the whole setup, because it tells you whether a portal is sending poor leads or whether you are listed in the wrong categories. Keep the stages few and the required fields minimal. If logging a lead takes longer than calling it, reps will stop logging. Where a rep works mostly on the phone, Zoho's mobile app and telephony integrations can log calls against the lead automatically, which gives you response-time data without asking anyone to type it.
Measuring portals against spend
With leads flowing in, tagged and staged, the ROI report is straightforward. In Zoho Analytics or a Zoho CRM report, group deals by Lead Source and show leads created, genuine leads, quotes sent, deals won and won revenue for the subscription period. Add the portal cost as a manual figure per period, since portal subscriptions do not come from an ad API, and divide to get cost per genuine lead and revenue per rupee of subscription. Look at it over a full renewal cycle rather than monthly, because B2B deal cycles from portals can run weeks or months. Compare buy-leads against direct enquiries, and compare portal performance against your Google Ads search campaigns for the same product categories. Sometimes the conclusion is that the portal is the cheapest source you have. Sometimes it is that a higher subscription tier is buying visibility without buyers. Either way, the decision is now based on closed revenue from your own CRM, not the portal's own dashboard of enquiries delivered.
FAQ
Yes. IndiaMART provides a lead API for sellers through its Lead Manager, and connectors for Zoho CRM exist on the Zoho Marketplace. Zoho Flow or a custom integration can also poll the API and create leads. Confirm API access with IndiaMART for your subscription.
Normalise mobile numbers to one format and check for an existing lead or contact before creating a record. If a match exists, log the new enquiry as an activity on that record and note the additional portal, rather than creating a second lead.
Tag every portal lead with its source, carry that source through to the deal on conversion, then report won revenue by source over the subscription period and compare it with what you paid the portal. Cost per genuine lead and revenue per rupee spent are the two numbers I use.