How to run a Facebook ad campaign for a Bangladesh constituency election
Step-by-step playbook for setting up a constituency-targeted Meta ads campaign for a Bangladeshi political candidate — from audience build to compliance to budget pacing.
How to run a Facebook ad campaign for a Bangladesh constituency election
Tools
- · Meta Ads Manager
- · Meta Business Suite
- · Meta Conversions API
- · Meta Ad Library
Prerequisites
- · Verified Meta Business Page for the candidate
- · Ability to complete Meta political-ad authorization (ID + in-country location)
- · Ad account with BDT payment method on file
- · Constituency boundary coordinates (lat/lng polygon)
Step-by-step
Authorize the ad account + register the “Paid for by” disclaimer
Before any spend: complete Meta’s political-ad authorization (verified identity + in-country location) and register the disclaimer naming who pays. This can take days — do it early, because unauthorized political ads are rejected and pages get restricted. See /political-facebook-ads-bangladesh for the full compliance regime.
Build the constituency-pinned audience
In Meta Ads Manager → Audiences → Create a custom audience with a geo-radius drawn over the constituency. Layer in age 18+ and language=Bangla. Save this audience by name — you'll reuse it for every ad in the cycle.
Set up Conversions API (CAPI) for the campaign site
Server-side event tracking from the candidate's microsite to Meta — recovers signal lost to iOS ATT and ad blockers, which is critical during a campaign's final week when click-noise spikes.
Author Bangla-first creative (image + video variants)
Test 3 image and 2 video variants on a BDT 5,000 micro-budget. Winning variants by reach + CTR move to the main campaign.
Configure budget pacing for the cycle
Heavy-weight the final 14 days. Recommended split: 20% pre-narrative (T-60 to T-30), 30% sustained (T-30 to T-14), 50% closing window (T-14 to polling day).
Stay inside Special Ad Category + Ad Library, then archive
Keep every ad within Meta's Special Ad Category — no protected-trait targeting — and remember all political ads are archived in Meta's public Ad Library for years, so write and target assuming full visibility. Save all creative, targeting, and spend to a candidate archive; BD has no BCRA-equivalent disclosure yet, but expect a request from the EC — have it ready.
In the glossary
Terms used.
Ad Authorization
Ad authorization is Meta’s identity and location verification that an advertiser must complete before running ads about elections, politics or social issues. The advertiser confirms a verified identity and an in-country location and registers who is paying. Without it political ads are rejected, and it can take days to complete.
Open
“Paid for by” Disclaimer
The “Paid for by” disclaimer is the mandatory label on every political ad naming who paid for it. Registered once during authorization on an authorized account, it is then applied automatically to every ad the campaign runs, and it feeds the public Ad Library where anyone can see what a candidate is running.
Open
Special Ad Category
Special Ad Category is Meta’s restricted classification for political, electoral and social-issue ads. It limits targeting, so advertisers cannot narrow by age, gender, detailed demographics or many interest traits the way commercial ads allow. Campaigns instead build reach on geography and legitimate affinity, and must be designed to perform inside these limits.
Open
Constituency Targeting
Constituency targeting focuses paid Facebook reach on a specific electoral seat using Meta’s geography and affinity layers, within Special Ad Category limits. It tunes the location radius to union, ward and upazila lines and weights spend toward the pockets that decide the seat, targeting the voters who decide the margin rather than vanity reach.
Open
Meta Conversions API (CAPI)
Meta Conversions API (CAPI) is server-to-server event tracking that sends conversions from a site or CRM to Meta's ad platform, recovering signal lost to iOS ATT and ad blockers. Because browser-side pixel firing drops 30–50% or more of events after iOS 14.5, sending the same events from the server gives Meta's bidding a more complete signal.
Open
FAQ
Frequently asked.
- How long does How to run… typically take?
- Roughly 2h30m for the steps in this playbook end-to-end, assuming the prerequisites are already in place.
- What do I need before I start?
- Verified Meta Business Page for the candidate; Ability to complete Meta political-ad authorization (ID + in-country location); Ad account with BDT payment method on file; Constituency boundary coordinates (lat/lng polygon)
- Can Public Pulse run this for me?
- Yes. This playbook is open documentation but we do this work for clients. Free 30-minute consultation to scope.