NGO Website Development in India: Building a Campaign Landing Page for Festival and Year-End Giving Seasons

NGO Website Development in India: Building a Campaign Landing Page for Festival and Year-End Giving Seasons

A campaign page for a festival or year-end giving season is a separate, time-boxed page on your NGO's website with one goal, one story, a short list of fixed giving amounts, its own tracked URL and a planned shutdown date. In NGO website development in India, the work that decides the result happens in the eight weeks before launch: agreeing what the money will do, building the page, wiring up tracking, testing under load and preparing the follow-up. A page assembled the week before Diwali, or on 28 March, usually raises less than the same page prepared properly, and it leaves the NGO with messy data and no way to thank donors well.

This guide is for founders, fundraising managers and communications leads who already have a working donation form and want a seasonal push. It does not repeat the general advice in our guide to donation page design; read that for the form itself. Nothing here is tax or legal advice. Where 80G, FCRA or accounting treatment matters, check with your CA.

Why a separate campaign page

Your permanent donate page serves everyone: the monthly donor, the person checking your registration, the CSR officer. A campaign page serves one moment and one message. A visitor arriving from a festival WhatsApp message should see the festival appeal, not a menu of twelve programmes. A dedicated URL also gives you a clean bucket of traffic and donations to analyse, lets you edit the headline and amounts without touching pages your search traffic depends on, and makes it easy to retire the page on a date you chose in advance.

Which seasons suit it

Choose one or two seasons a year. A small team that runs five campaign pages runs all of them thinly.

The eight-week countdown

This assumes a team of two to four people and a donation flow that already works. A campaign page cannot compensate for a broken checkout. Week 0 is launch day.

• Weeks 8 to 7, goal and offer. Write one sentence that finishes "This campaign exists so that ______." Set the outcome in programme terms first and the money target second. Get unit costs from your finance lead in writing, from your own books. Fix the launch, soft-launch and shutdown dates, and name one owner each for content, build, tracking, messaging, donor care and reporting.
• Weeks 6 to 5, content and build. Collect one story with consent, three to five photographs and the thank-you copy. Brief your developer with the page anatomy below. For an experienced team on an existing site this is typically a few days of work, but it depends on your theme, donation platform and custom elements, so confirm with quotes.
• Week 4, tracking and receipts. Set up the URL, UTM links and GA4 events. Make a small real test donation and check what arrives and when. Submit WhatsApp templates for approval now, since approval is not always instant.
• Week 3, staging review. Test on a real mid-range Android phone over mobile data. Watch someone who has never seen the page try to donate, without helping them. Freeze content at the end of the week.
• Week 2, load and failure testing. Run the checks described below and confirm who to call at the host and the gateway on launch day.
• Week 1, soft launch. Send the page to the board, staff and a few trusted donors. Early gifts test the whole chain with real money and give the goal meter an honest non-zero start.
• Week 0, public launch. Launch when your team is at work, not at 11 pm on a Friday. Check numbers daily for three days, then weekly.

Anatomy of the campaign page

Headline and one primary button

State who is helped, what changes and by when, in plain words. The button should say what the donor will do ("Give now"). Repeat it lower on the page and do not add competing calls to action above the fold.

A goal meter that is honest

A progress bar helps only when it is accurate.

• Pull the raised amount from donation records, not a number someone types. If it must be manual, update at fixed times and say "updated daily".
• Say what is counted. If bank-transfer gifts or pledges are included, label them.
• Set the target from the cost of the planned outcome, not from a number chosen to look ambitious.
• Do not start the bar at money you have not received, and do not reset it to look closer to the goal.
• State what happens if you exceed or miss the target, for example which programme receives surplus funds. Check the wording against your restricted-fund policy with your CA or auditor.

The story

One story, told briefly: the person or place, the problem, what a gift changes. A reader should grasp the whole appeal in about thirty seconds of scrolling. Use a photograph with consent and a first name or agreed alias, never detail precise enough to identify a child or a vulnerable person.

Fixed amounts tied to real outcomes

Pages usually convert better with a few suggested amounts, each linked to a concrete outcome, plus a "choose your own" field. The amounts must come from your own unit costs, not from this article. Fill every bracket from your finance records.

• Every figure must survive the question "how did you arrive at that?"
• State openly whether administration is built into each unit or funded separately.
• Do not write "100% reaches the beneficiary" unless it is exactly true after gateway charges and all costs.
• Offer a monthly option beside the one-time amounts, but do not pre-tick recurring or "cover the fees" boxes. Our article on recurring monthly giving covers the mechanics.

Trust block, real proof and an honest date

Add registration details, how receipts work, a phone number someone answers and a link to your latest report; our donation transparency checklist lists what donors look for. Use donor comments only with permission, and never invented counters such as "127 people are viewing this page". If the campaign ends on a date, say it in plain words and in IST. A countdown timer that resets for each visitor is a false deadline.

Campaign URL, UTM links and GA4 tracking

You want to answer one question afterwards: which messages produced which donations. That needs a plan before launch. Our article on campaign attribution for NGOs goes deeper.

The URL. Use a short, readable path such as /give/diwali-2026, lowercase, with the year in it. Share this URL, not the general donate page. Decide now what it will do afterwards.

UTM parameters. These are tags on a link that tell analytics where a visit came from. Write the convention down, because inconsistent tags are the commonest reason campaign reports are unusable.

Use lowercase and hyphens everywhere, keep one master sheet of every tagged link, use a separate QR code per placement, and do not tag internal links (a homepage banner pointing at the page), which overwrites the true source.

GA4 events. Record the page view, a click on an amount (with the amount), the start of checkout, and a completed donation fired only after the gateway confirms success, with value and transaction ID. Mark the completed donation as a key event; our guide to GA4 conversion tracking setup shows how. Two cautions: a reloadable thank-you page will fire the event repeatedly unless guarded, and an event fired on the "pay" click overstates donations. Never send a name, phone number, email or PAN to GA4. Reconcile GA4 against gateway records weekly; they will not match exactly, but a growing gap means something is broken.

If you use analytics cookies, show a consent banner that works and respect the choice. Our article on the DPDP Act and donor data covers the wider obligations.

WhatsApp and email follow-up

Message only people who have given permission on that channel, and keep a record of how and when. If consent records are weak, fix that in the weeks before launch.

One idea and one link per message. Filter out people who have already given before every reminder. Our article on the NGO donor welcome journey covers the first days after a gift. On the WhatsApp Business Platform, marketing messages are pre-approved templates and recipients can opt out; check current rules and charges with your provider before budgeting. A WhatsApp flow can answer repeat questions about receipts and offline giving so your team is not typing the same reply two hundred times. Name one person to handle donor queries during campaign hours, with a script for the common four: payment deducted but no receipt, wrong name on a receipt, a change or cancellation, and offline giving details.

Load testing and failure planning

A campaign page meets its sudden spike within minutes of a WhatsApp or email send. A site that is fine on a normal Tuesday can fail then.

What to test.

• The page itself: static, cached pages cope far better than pages that query the database per visit. Ask whether caching is on and whether it still works with the goal meter.
• The donation hand-off: several small test donations in quick succession from different devices, one on weak mobile data, watching for double charges, missing receipts and stuck "processing" screens.
• Email delivery: do ten confirmations at once reach the inbox rather than spam?
• Mobile weight: most traffic will be on phones; see our articles on Core Web Vitals and low-bandwidth donors.
• Third-party scripts: remove chat widgets and pop-ups that do not serve the campaign.

How. Run a load tool against a staging copy, never against your live payment gateway, whose terms and fraud checks may object. Use the gateway's sandbox plus a handful of real small payments. Estimate peak from past sends, your list size and usual click rates, and plan for a multiple of it. With no history, ask your host what the plan handles and treat that as the ceiling.

Failure plan. Write down before launch who contacts the host if the site slows, whether a "high traffic" holding page exists, what the second payment route is if the gateway declines many payments (and how you will reconcile and receipt it), who can edit and who approves a wrong figure, and how to restore a backup taken before launch.

Content and consent hygiene

• Get informed consent for stories and photographs, ideally in writing and in the person's language, with a parent or guardian for children and a way to withdraw.
• Describe what people are doing and wanting, not only what they lack.
• Trace every figure on the page to a record; remove claims you cannot trace.
• Use only images, music and fonts you have the right to use.
• Collect only what you need to process the gift and issue the receipt, and keep the donor list in your donor system, not an open spreadsheet.
• Have your CA approve the exact wording about 80G and receipts. If you hold FCRA registration, take advice before promoting the campaign abroad.
• Check colour contrast, alt text and keyboard use so assistive technology users can give.

What to do with the page after the campaign

Close on the date you promised. Choose one option in advance and tell your developer.

1. Convert it to a thank-you and results page. Keep the URL, replace the appeal with outcomes and a gentle link to ongoing giving. Usually best if the page earned links or visits.
2. Redirect permanently (301) to the main donate page or the relevant programme page, not the homepage by default.
3. Archive it as a read-only record with the form removed and a note that the campaign ended.

Remove it from menus, banners and any sitemap entry that promoted it. Within two to four weeks, send every donor a short report: the real total, what it funded, what was not achieved and what is next. Donors forgive an honest shortfall more readily than silence. Then reconcile every donation against gateway and bank, confirm each eligible donor has the correct receipt, deduplicate records, tag them with campaign and source, and mark test donations clearly. A few weeks after a first gift, invite the donor to a next step such as a monthly gift or a field update, and do not repeat the same one-time ask within a fortnight.

Post-campaign review sheet

Hold the review within three weeks of the end and write the answers down.

The cost line is the one most often skipped. Count your team's time honestly so you can compare this campaign with the next. For the metrics trustees usually want, see our article on the NGO fundraising dashboard.

Working with Govindani Infotech

Govindani Infotech Pvt. Ltd. is a web design and development company in Pune, and we have built more than 500 NGO websites. If you want help planning or building a campaign page on your existing site, with tracking, a donation flow and WhatsApp follow-up wired in, we can review your setup and tell you what is needed and what is not. See how we approach NGO sites on our NGO website page, and how projects are scoped on our NGO website pricing page.

To talk it through, message us on WhatsApp or use the contact page. If your campaign date is within eight weeks, say so at the start and we will tell you honestly whether the timeline is realistic.

Before the campaign goes live, also check that the site can take the load: see how to prepare a donation site for a viral appeal or year-end traffic spike.

Frequently Asked Questions

How long before a festival or year-end campaign should an NGO start building the page?

Eight weeks is a comfortable lead time, and six is workable if the donation flow already works and the content is ready. Under four weeks usually means skipping testing or the follow-up plan, which is where most avoidable problems arise.

Should an NGO use a separate campaign page or the main donate page?

A separate page is usually better for a seasonal appeal because it carries one message, gives clean tracking and can be closed on a planned date. Keep the main donate page for permanent giving and link the two.

Is it acceptable to show a goal meter if we have not raised much yet?

Yes, as long as the figure is real and labelled honestly. A few genuine early gifts from the board and close supporters before the public launch give the meter an honest, non-zero start.

How do we track which WhatsApp or email message led to a donation?

Use a dedicated campaign URL with consistent UTM parameters on every link, then record a completed-donation event in GA4 only after payment is confirmed. Compare GA4 with your gateway records weekly and keep personal data out of the tags.

What should we do with the campaign page after it ends?

Choose one option in advance: turn it into a thank-you and results page, redirect it permanently to a relevant page, or archive it with the form removed. Whichever you pick, send donors a report within a few weeks saying what was raised and what it did.