Skip to main content

Analytics Settings in CamBuildr

Add Google Analytics, Tag Manager, FB Pixel, recruiter tracking & global JS to all your pages for full campaign tracking.

Alexander Lagger avatar
Written by Alexander Lagger
Updated this week

The Analytics settings in CamBuildr allow you to integrate external tracking tools and manage scripts across your campaign infrastructure. With support for Google Analytics, Facebook Pixel, custom JavaScript, and recruiter tracking, you can analyze engagement and optimize your outreach strategies effectively.

Where to Find It

Navigate to Settings → Analytics from the main menu to configure your analytics setup.

Available Configuration Options

1. Google Analytics ID

Add your Google Analytics tracking ID here. This ID will be automatically embedded in:

  • All Landing Pages

  • All Engagement Apps

  • All pages using the Generic Theme

CamBuildr uses anonymized IP tracking by default for privacy compliance.

2. Google Tag Manager ID

Insert your GTM container ID to deploy and manage multiple tags (including third-party tracking or conversion pixels) without modifying the page source.

Option available: You can also send default event data to Facebook, such as form submissions or visits to specific sections.

3. Facebook Pixel ID

Add your Facebook Pixel ID to track page views and conversion events for retargeting and campaign performance on Facebook. This ID will be included on every CamBuildr-generated page using the generic theme.

4. Recruiter Tracking

When enabled, CamBuildr will automatically append recruiter IDs to shared links—especially relevant in email share blocks and social media actions.

This allows you to:

  • Attribute new signups to existing supporters

  • Measure organic referral growth

  • Identify top-performing recruiters

For more details, see: "Using the Share Block in Emails".

Important: Before activating recruiter tracking, review your local privacy laws to ensure compliance.

5. Global JavaScript Injection

Insert JavaScript globally into:

  • Landing Pages

  • Engagement Apps

  • Utility Pages

You can define:

  • Head Scripts (for metadata or third-party integrations)

  • Body Scripts (for additional frontend functionality)

Caution: Invalid or untested scripts may cause layout or functionality issues.

Hint:

The Global Javascript section in CamBuildr is not limited to analytics—it can also be used to inject custom CSS and JavaScript across all your landing pages and engagement apps. This is useful for applying advanced styling rules, integrating third-party widgets, or adding custom logic without editing individual pages. You can add scripts either in the <head> (for styles, metadata, etc.) or in the <body> (for interactive behavior and event handling). Just make sure your code is valid and tested, as incorrect scripts may break functionality across your campaign pages.

Automated Tagging

CamBuildr offers a set of default events and automated tagging capabilities for commonly used blocks (e.g. form submissions, surveys, petitions). These are preconfigured and don’t require manual scripting.

To learn more about what’s automatically tracked and how to make use of it, refer to our article: Automated Tagging and Analytics in CamBuildr

Best Practices

  • Use Google Tag Manager if you’re working with multiple platforms or need flexible tag management.

  • Enable Recruiter Tracking for grassroots growth analysis.

  • Avoid using untested custom scripts in the global field.

  • Check that automated tagging already covers your use case before adding extra analytics.

Did this answer your question?