06 · Capabilities
Opt-in

Advertising

Run click-to-WhatsApp ad campaigns inside Neev — create a campaign, attach a price-accurate creative, connect a Meta ad account by reference, and capture the leads that click through into your pipeline.

5 min read · updated 28/05/2026

Opt-in Capability · off

Advertising is switched offAdvertising

You can read the guide. An owner or manager flips this Capability on in settings — it then lights up across the app.

Overview

Advertising turns Neev into the place you run your click-to-WhatsApp (CTWA) campaigns from — instead of bouncing between Meta Ads Manager, a spreadsheet of what you spent, and a separate chase for the leads that came in. You set up a campaign with a budget and a target geography, attach a creative, push it live to Meta, and the people who tap your ad and message you on WhatsApp land straight in your leads pipeline.

Opt-in Capability · off

Advertising is switched offAdvertising

You can read the guide. An owner or manager flips this Capability on in settings — it then lights up across the app.

This is an opt-in, paid Capability — the Owner turns it on. Honest status: the data model and the campaign screens are built, but the suite ships dark. It is not yet a switch you can flip in Settings, and the Meta-publishing path is held behind external Meta App Review + Business Verification. Treat this page as how it works once enabled.

Where to find it

Advertising is an Owner-only area. There is no live sidebar route yet — it ships behind the Capability toggle in a later release. It is built for both web and the field app, so you can launch a campaign at your desk and watch leads arrive on your phone.

Key concepts

  • Campaign — one ad effort: a name, an objective, a budget, and a target geography. It moves through Draft → PendingApproval → Live → Optimizing → Paused → Ended.
  • Creative — the ad itself: the copy plus a generated background image, with the rupee price burned in by Neev, not by the image model. Prices are drawn deterministically so the number on your ad is always exactly right.
  • Ad account connection — the link to your Meta ad account. Neev never holds your Meta token — it is referenced through your own Business Manager, which you control and can revoke.
  • CTWA lead — a person who tapped your ad and messaged you on WhatsApp. Neev captures them as a lead so the campaign feeds your pipeline.
  • Recommendation — an optimize proposal (pause a weak creative, shift budget). Neev only proposes — nothing changes your live campaign until you apply it.

How money and tokens are handled

  • Token by reference. Connecting an ad account stores a reference to your Meta credential, never a copy of the token. The secret stays in your Business Manager.
  • The price is never guessed. The price on a creative comes from a real number you set, rendered by a deterministic overlay — an image model never draws a digit. A wrong price on your own ad is a trust failure Neev refuses to risk.
  • Nothing auto-spends. The optimize engine proposes; only you (an Owner action) apply a change to a live campaign.

Connecting an account and going live

  • Connect first. Connecting checks the ad account is reachable, then stores the reference to your Meta credential plus the page and WhatsApp number your CTWA ad points at. The token itself stays in your Business Manager.
  • Publish needs a connected account. A campaign only goes Live once an account is connected — that is what tells Neev which page and WhatsApp number the ad routes to. Publishing moves the campaign from PendingApproval → Live and records the Meta campaign reference against it.
  • The live switch is platform-wide, not per-tenant. Real Meta spend turns on once — when Neev's Meta App Review clears and the platform is wired with Meta credentials — not through your own settings. Until then, publishing runs against a safe stand-in that spends nothing, which is why the publish action stays out of the live UI for now.

Measuring and optimizing

  • Performance is pulled for you. Once a campaign is Live, Neev fetches its spend, impressions, clicks, and CTWA leads from Meta on a schedule and stores them as time-bucketed metrics you can read on the campaign — no exporting from Ads Manager. The numbers you see are the cached figures from the last fetch, not a live call every time you open the screen.
  • The optimize engine only proposes. On a regular sweep Neev looks at each Live campaign's recent spend and cost-per-lead and, when something looks off — money spent with no leads, or a cost-per-lead over the ceiling — it raises a recommendation (pause a weak creative, shift budget). Raising one moves the campaign to Optimizing. Nothing about your live ad changes at this point.
  • You apply the change. A recommendation sits open until an Owner applies it. Applying it is the only thing that pushes a change back to your live Meta campaign, and it returns the campaign to Live. Every apply is recorded in the audit trail with who did it. The engine never applies its own proposals.

Compliance note

WhatsApp messaging here is over-the-top (OTT) — the ad is gated by Meta's own review and your Business Verification, not by a telecom DLT registration. Lead follow-up over WhatsApp still passes Neev's consent gate before any message is sent.