RERA Rules for Cross-State and National Ad Campaigns

A marketing lead at a developer with live projects in Bengaluru, Pune, and Hyderabad is briefing an agency on a single national brand campaign. The creative looks clean: one hero visual, one tagline, one media plan running across three metros simultaneously. Then someone on the compliance side asks the question that derails the timeline — "Which project's RERA number goes on this ad, and does it need three different disclosure blocks or one?"

This is the exact friction point that trips up developers scaling beyond a single city. RERA is a state-subject law — each state runs its own regulatory authority, its own portal, and its own registration numbers — but marketing increasingly operates at a national or multi-city level, especially as digital ad platforms make geo-targeting trivially easy. A campaign built for reach without a plan for per-project disclosure creates real compliance exposure, and the fix is far cheaper before launch than after a complaint is filed.

This article walks through how RERA's per-project, per-state disclosure obligation intersects with national and cross-state advertising, and gives developers a practical framework for scaling reach without multiplying risk.

Why RERA Disclosure Is Per-Project and Per-State

Unlike a single national regulator, RERA is implemented separately by each state under its own authority — Karnataka's K-RERA, Telangana's TG-RERA, Maharashtra's MahaRERA, and so on. A registration number issued in one state has no standing in another, and there is no single national RERA database that would let a national ad reference "the company's" registration in generic terms.

Crucially, the disclosure obligation attaches to the project, not the developer brand. A single builder group with five ongoing projects across three states holds five separate RERA registrations, each with its own number, validity period, and portal record. Any advertisement that promotes a specific project — even as one element of a larger multi-project creative — needs to carry that project's own registration details, not a generic corporate reference.

This creates a structural mismatch with how national brand marketing typically wants to work: one creative, one message, broad reach. The practical resolution is to separate brand-level advertising (which promotes the developer's reputation generally, without naming a specific project or making project-specific claims) from project-level advertising (which names a project, shows renders, or invites bookings) — because only the latter triggers the full per-project disclosure requirement.

Step-by-Step: Building a Compliant Multi-State Campaign

1. Classify each creative as brand-level or project-level before it goes into media planning. Project-level creatives need per-project RERA details; brand-level creatives generally do not name a specific project's registration.
2. Map every project-level creative to its specific state's registration number and portal URL — never reuse one project's number across a creative that could be interpreted as promoting a different project.
3. For multi-project creatives (e.g., a single ad showcasing three projects across three cities), include a disclosure block listing each project's individual RERA number, ideally linked to the relevant landing page where the full detail lives.
4. Check geo-targeting logic against project relevance — a digital ad geo-targeted to Chennai but promoting a Bengaluru project must still disclose the Bengaluru project's actual RERA details, not a Chennai one, even though the audience is in Chennai.
5. Route every project-level ad's "learn more" link to a page carrying that project's specific, current RERA number and as-of date — typically the project's own listing page rather than a generic company homepage.
6. Retain a compliance sign-off step for any creative going into a multi-state or national media buy, separate from the standard creative approval, since a single missed disclosure can appear in every city the campaign runs in simultaneously.

Campaign Type, Disclosure Required, and Per-State Notes

Multi-City Demand Context

Scaling a campaign nationally often follows genuine multi-city demand. According to NHB RESIDEX data for Q4 FY25 (2025, via ainvest), city-level year-on-year price movement varied meaningfully — Bengaluru rose approximately 13.1%, Hyderabad approximately 4.8%, alongside other tracked cities — a reminder that "national" demand is really a set of distinct city markets with their own price trajectories, not a single homogeneous trend. Developers should let that city-specific data inform city-specific messaging even within a shared campaign architecture, rather than flattening every market into one national narrative. Sector-wide, the IBEF Real Estate Industry in India report (February 2026) notes FY25 delivery of 406,889 units nationally (+33% YoY), underscoring why more developers are now operating — and advertising — across multiple cities at once.

Digital Geo-Targeting and Disclosure Mechanics

Digital platforms make it trivial to target an ad by city, pin code, or even a radius around a specific landmark — which is exactly why geo-targeting has become a common source of RERA disclosure gaps. The mechanics that matter:

• The disclosure follows the project, not the viewer. An ad served to a Mumbai audience promoting a Pune project must still show the Pune project's MahaRERA number — the fact that the viewer is in Mumbai is irrelevant to which registration applies.
• Dynamic creative (where ad copy or images change by audience segment) needs the same disclosure discipline as static creative — if the underlying project changes between segments, the disclosure block must change with it.
• Landing pages should carry the same registration details as the ad that drove the click — a mismatch between what an ad discloses and what the landing page shows is an easy, avoidable inconsistency.
• NRI-targeted geo-segments (Gulf, US, UK, Singapore audiences) carry additional considerations around currency framing and return claims, covered in depth in our companion piece on RERA advertising rules for NRI-targeted campaigns.

Mini Scenario: A Bengaluru + Pune Campaign Gets It Right

A developer with an active Bengaluru project and a newly launched Pune project wanted a single national digital push to build overall brand awareness ahead of a festive-season sales window. The initial creative concept used one hero visual with both project names layered into the same frame and a single "RERA registered" line at the bottom with no numbers.

During compliance review, the team restructured the creative into two linked variants sharing the same brand visual: the Bengaluru-facing variant carried the Bengaluru project's K-RERA number and a link to its DrawMagic listing page; the Pune-facing variant carried the Pune project's MahaRERA number and its own listing link. Media buying then geo-targeted each variant to its relevant city (plus a shared broader-reach segment showing both, each with its own disclosure line). The campaign kept its unified brand look while ensuring every viewer, regardless of which city's ad they saw, could trace the exact project being promoted back to its correct, current registration.

Pro Tips for Scaling Compliant National Campaigns

1. Build a disclosure template per project, not per campaign, so any creative team can drop in the correct RERA block without re-researching it each time.
2. Centralise RERA numbers and as-of dates in one internal reference (or better, in your project listings) so marketing never has to chase compliance for a number mid-campaign.
3. Treat brand-level and project-level creative as genuinely different approval tracks, with project-level ads requiring the extra disclosure sign-off.
4. Audit geo-targeted campaigns quarterly to confirm the served creative still matches the current registration status of the project it promotes, especially after an extension or status change.
5. Keep a single point of contact for multi-state compliance questions so a marketing lead planning a national push has one clear path to get disclosure requirements confirmed quickly.

Common Mistakes to Avoid

• Running a multi-project creative with a single generic "RERA registered" line instead of naming each project's actual number.
• Geo-targeting an ad by viewer location and assuming that determines which state's RERA number applies (it doesn't — the project's own state governs).
• Letting a landing page's RERA details drift out of sync with what the referring ad disclosed.
• Treating brand-level campaigns as a way to imply claims about a specific project's timeline or pricing without formal project-level disclosure.
• Skipping compliance review on paid social or programmatic buys because they "move too fast" for a sign-off step — these are exactly the channels where geo-targeting mistakes are most likely.

Integration with DrawMagic Features

DrawMagic's builder listings are built around this reality: each project's listing carries its own state RERA number and as-of date as structured data, so any geo-targeted campaign that links back to a specific listing automatically points to correctly disclosed inventory rather than a generic company page. When you register a new project profile, you create the disclosure source of truth for that state — one record that every downstream ad, listing, and landing page can reference consistently, rather than compliance details living only in a static PDF brochure that marketing teams copy from by hand.

Scale Reach Without Multiplying Risk

A national footprint doesn't have to mean fragmented compliance. The developers who scale cross-state campaigns most smoothly are the ones who treat per-project disclosure as a structured input to creative and media planning, not an afterthought bolted on before a legal sign-off. Set up your builder profile on DrawMagic to keep every project's public facts consistent as your portfolio and campaign footprint grow.

Key Takeaways

• RERA disclosure obligations attach to the specific project being advertised, not to the developer brand as a whole — every project-level ad needs that project's own RERA number.
• A national or multi-city campaign with several live projects needs a disclosure plan per project, not one generic "RERA registered" line.
• Digital geo-targeting does not change which state's RERA number applies — the project's registered state governs, regardless of where the ad is served.
• Separate brand-level advertising (no named project) from project-level advertising (named project, specific claims) early in creative development.
• Landing pages linked from ads should carry the same RERA details as the ad itself, to avoid inconsistency a diligent buyer would notice.
• City-level price data — such as Bengaluru's and Hyderabad's YoY movement per NHB RESIDEX — should inform city-specific messaging even within a shared national campaign.
• Centralising RERA numbers and as-of dates via structured project listings removes the recurring friction of marketing teams chasing compliance for numbers mid-campaign.
• Treat multi-state compliance sign-off as a distinct approval step for project-level creative, especially on fast-moving digital and programmatic buys.
• NRI-targeted geo-segments carry additional disclosure and claims considerations worth reviewing separately.

FAQ

Does a brand-level ad (no specific project named) need a RERA number? Generally, an ad that does not name a specific project or invite bookings for one does not need to display a project's RERA number, since the disclosure obligation is tied to promoting a specific registered project. Confirm the exact threshold with your state RERA authority and legal counsel, since interpretation can vary.

Can one RERA number cover multiple phases of the same project? Registration is typically tied to a specific project phase as filed with the authority; different phases may carry different registration numbers. Always confirm which number applies to the specific units or phase being advertised.

What happens if a geo-targeted ad accidentally shows the wrong project's RERA number? This is treated as a disclosure error and should be corrected immediately — pause the creative, fix the disclosure, and confirm the landing page matches before resuming the campaign. Repeated or uncorrected errors carry regulatory risk under the applicable state RERA framework.