B2B Lead Generation Under DPDP: How to Choose Consent Management Software for Marketing Teams

    DPDP lead generation for B2B teams: how the law treats cold email, purchased lists and event leads, plus what to check in consent management software.

    OneConsentBlog
    10 min read
    Thursday, 19 November 2026
    B2B Lead Generation Under DPDP: How to Choose Consent Management

    Your B2B pipeline runs on personal data. A prospect's name, work email address and mobile number arrive through web forms, webinars, events and purchased files. The Digital Personal Data Protection Act, 2023 (the Act, commonly called DPDP) and the Digital Personal Data Protection Rules, 2025 (the Rules) apply to personal data about any identifiable individual. They create no separate category for business contacts. Duties on notice and consent apply from 13 May 2027. Sales and marketing teams have until then to build DPDP lead generation processes they can evidence.

    How Does DPDP Treat Business Contact Details?

    Business contact details can be personal data. The Act covers any data about an individual who can be identified from it, whatever the professional setting. A named work email address, a direct mobile number or a profile link qualifies.

    The Act calls the individual the Data Principal. The Data Fiduciary decides why and how the data is used. For its own leads, that is the company running the campaign. An agency that sends emails on the company's behalf is a Data Processor in most arrangements. The classification follows the agency's role and decision making authority, and the contract label does not decide it.

    Generic company information and a shared sales address that identifies no individual fall outside the definition. The Act also excludes data that the individual has made public herself, or that another person has published under a legal obligation. The exclusion turns on who published the data and why. Ask counsel about details taken from an employer's website or a third party directory.

    From 13 May 2027, a breach of a provision with no separate entry in the Schedule to the Act can attract a penalty of up to ₹50 crore. A failure to take reasonable security safeguards can attract up to ₹250 crore. These are maximum amounts.

    Cold Email Under DPDP: What Does the Law Allow?

    Legal position. The Act regulates the processing of personal data and leaves the channel open. Sending a cold email processes the recipient's address, so the business needs a ground for processing: consent, or one of the nine legitimate uses listed in the Act. The Act has no general legitimate interest ground, and none of the listed uses mentions sales prospecting.

    Voluntary provision comes closest. The Act lets a business process data for the specified purpose for which the individual voluntarily provided it, unless she has said she does not consent. The Act does not define voluntary provision, and its limits remain unsettled. A reply to an enquiry that the prospect submitted may rest on this ground. Later sales messages may or may not share that purpose, depending on the notice, the context and the prospect's expectations. Treat the enquiry as a basis for the reply only.

    Recommended practice. Run outbound email on consent for individuals the business sourced itself. Before your sequence starts, confirm that the recipient saw a notice naming the business and email marketing. Add a working unsubscribe link to every message and route each withdrawal to all sending tools. The Act expects withdrawal to be as easy as giving consent, and expects processing to stop within a reasonable time after withdrawal.

    Can You Use a Purchased Email List in India?

    The Act has no provision on lead lists, so its general duties decide the answer. A business that uses purchased data for its own campaigns becomes the Data Fiduciary for that use. The buyer owes the individual a notice with or before any consent request. Where the buyer relies on consent, it must also prove that notice was given and consent obtained if either is disputed. The individuals on the list gave their data to the seller, and a notice that described only the seller's services may not extend consent to the buyer's outreach.

    An initial email asking for permission is itself processing, so it gives no shortcut for an unverified list. A seller's assurance does not replace the notice and consent the buyer must show. A notice issued after collection may not validate earlier processing. Counsel should approve any approach to purchased contacts.

    Recommended practice. Before any purchase, ask the list provider for written evidence:

    • Source: where and when each record was collected.

    • Notice and consent wording: the text the individual saw, with its date and version.

    • Named recipients: whether the wording covered third party marketing by the business or its category.

    • Withdrawal and deletion terms: how an objection raised with the seller reaches the buyer, and the clauses for correction and deletion.

    If a provider cannot supply record level evidence, the buyer cannot prove consent for those records, and the file should stay out of outreach.

    Webinar, Event, Business Card, Advertising and Referral Leads

    In each of these cases, the individual shares data for one specific purpose, such as attending a session or receiving a brochure. The Act requires a notice with or before any request for consent, and the Rules set what the notice must contain. Recommended practice is to give clear information at every collection point, including where you rely on voluntary provision.

    • Webinar registration. Delivering the session needs only a name and a work email address. Offer follow-up marketing as a separate, unticked choice, since the Act expects consent to be unconditional and limited to necessary data.

    • Event badge scans. Post a short notice at the booth or in the scanning app and record what the visitor asked for, such as a brochure. Enrolment in a newsletter the visitor did not ask for needs consent. When an organiser shares attendee lists, ask for the registration notice and consent log first.

    • Business cards. A card handed over for a requested follow-up may support that follow-up. Recurring promotions need their own ground.

    • Advertising platform lead forms. Record the form wording, the stated purpose and the marketing choices before importing data into the CRM.

    • Referral leads. Check what the individual was told and whether that purpose covers your business.

    • Co-registration forms. The Act defines a Data Fiduciary as anyone who, alone or with others, decides the purpose and means of processing, so each brand on a joint form may carry its own duties. Naming each brand, listing the data and offering a separate marketing choice per brand are recommended practices that support specific, informed consent.

    Which Communication Rules Apply Alongside DPDP Consent for Marketing?

    DPDP consent for marketing governs the processing of personal data. Telecom and platform rules govern the delivery channel, and they apply in parallel.

    Channel

    Separate rule

    Recommended practice

    Email

    Email platforms and mailbox providers set their own sender and unsubscribe requirements, which apply in addition to the Act

    Keep one suppression list across sending tools

    SMS and calls

    TRAI's commercial communication rules cover sender registration, message templates, Do Not Disturb checks and the DLT platform. The Third Amendment of 18 September 2026 commences in stages, so check the current stage. TRAI consent covers calls and SMS only

    Log telecom consent and DPDP consent separately

    WhatsApp

    Meta's Business Messaging Policy requires an opt-in naming the business

    Word the opt-in to name the business and the message types

    A Do Not Disturb check, a DLT record or a platform opt-in does not authorise processing under the Act, and DPDP consent does not authorise promotional calls or SMS.

    Who Is Responsible for Lead Data Across Teams, Agencies and Partners?

    Enterprise lead data often passes through websites, regional teams, distributors, agencies and a CRM, and each hand-off needs an accountable owner. Suppose a prospect registers for a webinar, the lead moves to sales and the record syncs to email automation. If the prospect later withdraws consent, that withdrawal must reach the CRM, the automation tool and any agency list, or campaigns continue against the individual's choice.

    The Act holds the Data Fiduciary responsible for compliance, including for processing that a Data Processor carries out on its behalf and requires a valid contract with the processor. As recommended practice, each agency or partner agreement also settles who sets the purpose, who controls the form and notice, who keeps consent records, how withdrawals pass between parties and what happens to data when the contract ends.

    How Does a Lead Source Ledger Support DPDP Lead Generation?

    A lead source ledger is a register with one row for each route by which leads enter the business, from web forms to purchased files. It is recommended practice with no statutory status. If consent is disputed, the business must prove notice and consent, and the ledger points to that proof. Each row holds eight items:

    1. Source and owner: the source name and the responsible team.

    2. Collection method: form, scan, purchase or partner transfer, with dates.

    3. Data fields: each field collected, matched to its purpose.

    4. Notice version: the notice text shown and the dates it applied.

    5. Ground for processing: consent, or a listed legitimate use with the reason.

    6. Purposes and channels: the channels consented to, with partner names.

    7. Sharing and processors: agencies and tools, with the contract for each.

    8. Retention and withdrawal: the review date, the withdrawal route and the last suppression sync.

    Marketing operations can maintain the ledger, with legal reviewing it on a fixed schedule. Treat legacy databases the same way: give each old source a row and send records without a traceable notice or ground to counsel.

    Five internal indicators help track progress. They are management measures with no statutory status:

    1. Share of lead sources mapped in the ledger.

    2. Share of lead records with a traceable source.

    3. Share of consent records linked to a notice version.

    4. Share of connected systems that receive preference updates.

    5. Time taken to propagate a withdrawal.

    Read next: campaign level consent and marketing data governance in our guide to DPDPA for marketing leaders

    What Should Enterprises Ask Before Choosing Consent Management Software?

    Consent management software keeps the notice, consent and withdrawal for each lead together and applies them across connected tools. The term consent management platform describes this software category. A registered Consent Manager is a separate type of entity: a regulated body that helps individuals give, manage and withdraw consent, with a registration framework that took effect on 13 November 2026. You can use consent management software without engaging a registered Consent Manager. For DPDP lead generation, buyers should see each of the following demonstrated:

    Evaluation area

    What to see demonstrated

    Purpose specific capture

    Separate choices on web, app and offline channels

    Notice versions

    Retrieval of the notice version each lead saw

    Consent evidence

    Timestamped export with source and collection context

    CRM, customer data platform and automation

    Consent status on each lead record, checked before campaigns or audience activation

    Withdrawal propagation

    A withdrawal reaching CRM, email, SMS and WhatsApp tools, and the time taken

    Multi-brand control

    Each brand or business unit managing its own notices and purposes

    Access and APIs

    Role based access, APIs and webhooks

    Partner and imported data

    Records from agencies or files traced to their source

    Retention

    Configurable and monitored deletion workflows

    Audit readiness

    Record retrieval without depending on the vendor

    Treat a demonstration that stops at consent capture and cannot show a withdrawal reaching the CRM, email automation and other connected systems as a warning sign.

    OneConsent's consent preference management module captures purpose specific consent, records every withdrawal and syncs preferences across connected systems. Its notice module lets teams create, version, approve and publish notices across web, app, email and kiosk channels, and each notice version links to its consent records. The Consent Audit Trail lets teams search consent history and trace notice versions and withdrawals.

    Software records and applies the choices a business makes. The ground for processing, the origin of a purchased file and the final wording of notices stay with the business and its counsel. Confirm the integrations with your CRM, webinar and email platforms during evaluation.

    How Can You Verify Lead Consent With OneConsent?

    To prepare your DPDP lead generation process before 13 May 2027, you can verify the consent behind each lead with OneConsent. In a consultation, the team reviews the forms and event flows that collect leads and checks the notices and consent records behind each source, including partner arrangements and purchased files. You receive findings for each source, with the gaps listed. These DPDP consulting services work alongside software that applies the agreed choices across connected tools. You can visit the OneConsent website for the platform overview and book a OneConsent demo to see the modules against your own lead sources.

    Rohit Sharma
    Marketing Manager, Oneconsent

    Rohit Sharma is a Marketing Manager at OneConsent with over 7 years of experience across digital marketing, and digital transformation. His work spans content research, planning, and marketing, with a focus on DPDP compliance, data protection, privacy, AI, and emerging technologies. At OneConsent, he focuses on researching and writing about data privacy, consent management, and the DPDP Act, making complex topics clear, practical, and relevant for businesses while helping audiences understand how privacy and technology are shaping the future of digital experiences.

    See all articles by Rohit Sharma

    Frequently Asked Questions

    Have more questions?

    Search our full DPDP knowledge base for more answers.

    See it live

    See OneConsent in action

    Get a personalised walkthrough of how OneConsent helps your teams stay DPDPA compliant.

    • 30-minute walkthrough
    • DPDPA-ready by design
    • Tailored to your stack