Tracking and conversion events

Tracking and conversion events let you measure traffic, attribute donations to ads, and feed donation data into analytics platforms. Code you paste here runs inside the form itself, separate from any analytics already installed on your website. Most teams running paid campaigns will need to configure this. Teams that don't run paid campaigns can still install basic analytics here to understand what's working.

Open the Tracking tab

Click the Form Settings tab at the bottom of the left sidebar in the editor, then switch to the Tracking tab. The panel has three code-paste areas, each serving a different purpose.

The three fields

Google Analytics

For analytics scripts that should run throughout the donation flow, from the form through the thank you screen. Paste the entire snippet, not just the property or container ID. JavaScript and non-JavaScript code are both accepted.

Typical content for this field:

• Google Analytics 4 (GA4): your full GA4 snippet
• Google Tag Manager (GTM): your GTM container snippet
• Other analytics platforms: Plausible, Fathom, Mixpanel, and similar

If you can only install one thing in this field, install Google Tag Manager. GTM is a tag-management layer that lets you add and update every other pixel (Meta, Google Ads, LinkedIn, TikTok) from a single dashboard, without touching GiveForms again.

Form Views

Fires the first time a visitor opens your donation form. This is for top-of-funnel conversion-tracking pixels, the ones ad platforms use to measure who from your campaigns opened the form.

Typical content: the Meta (Facebook) Pixel base code, a Google Ads page-view conversion event, and the LinkedIn, X, or TikTok base pixels. If you're using Google Tag Manager for everything, you don't need to paste pixels here; GTM handles the firing logic for you.

Donations

Fires on the thank you screen after a successful donation. This is your conversion event, the moment a visitor became a donor. Ad platforms use it to attribute donations back to the ads that drove them.

Typical content: the Meta Pixel Purchase event, a Google Ads conversion tracking snippet, and LinkedIn or TikTok conversion events.

The Form Views and Donations pair gives you a funnel: how many people opened the form, how many converted, and how that breaks down by ad campaign and traffic source.

Testing

Pixels and analytics scripts don't visibly do anything on the form, which makes verification tricky. Tools that help:

• Tag Assistant (Google): verifies Google Analytics, GTM, and Google Ads conversion tracking
• Meta Pixel Helper: Chrome extension that shows whether the Meta Pixel is firing and which events
• Browser developer tools (Network tab): confirms the pixel's request is being made to the ad platform's domain

You can't fully test conversion-event firing without a real donation. Once pixels are installed, run a small live donation on the published popup and verify in the ad platform's dashboard that the conversion appears within a few hours.

Consent and privacy

Tracking scripts may have legal implications depending on your jurisdiction and your donor base. If you have donors in the EU, UK, California, or other regions with strict privacy laws, you may need:

• A cookie or consent banner giving donors the choice to opt into tracking
• A privacy policy disclosing what tracking you use
• Conditional script loading based on consent

GiveForms doesn't provide consent management; you'll need to set that up separately, through your tag manager (GTM has a consent mode), a dedicated consent tool, or custom code. We're not lawyers; if you have compliance questions, ask one.