# Component Tracking for Conversions

**URL:** <https://forum.builder.io/t/component-tracking-for-conversions/15888>\
**Category:** Bugs\
**Tags:** visual-editor, feature, api\
**Created:** [October 23, 2025, 12:18am UTC](https://forum.builder.io/t/component-tracking-for-conversions/15888 "2025-10-23T00:18:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matandessaur](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.builder.io/matandessaur/32/4905_2.png) [@Matandessaur](https://forum.builder.io/u/Matandessaur)\
**Post date:** [October 23, 2025, 12:18am UTC](https://forum.builder.io/t/component-tracking-for-conversions/15888/1 "2025-10-23T00:18:54Z")

</div>

### The Problem Today

[Builder.io](http://Builder.io) currently tracks clicks and impressions **for everything** — headers, nav bars, footers, all the boring stuff — not just conversion elements like CTAs or forms.  
That makes the analytics full of noise and hard to use.

* * *

### What the Solution Does

The proposal changes tracking from **“track everything” → “track only what we choose”**.

It adds a simple **on/off toggle** to each piece of content (like a section, symbol, component, data model) so that:

- Tracking is **off by default**

- Tracking only happens if someone enables the toggle

- Only those enabled components show up in Insights

* * *

### What Changes for Users

Inside the Builder UI, content editors will see a new boolean field (a checkbox) called something like:

> **Enable Conversion Tracking**

If they turn it ON — that component’s views and clicks are tracked.  
If they leave it OFF — it’s ignored by analytics.

* * *

### What Changes for Analytics Teams

Insights will now show **only the content marked for tracking** , so:

- No noise from headers, nav, footers, etc.

- Cleaner funnels and conversion attribution

- Better signal for what actually drives conversions

* * *

### Key Benefits

**Cleaner data** — no accidental tracking  
**Opt-in model** — privacy-friendly, controlled, intentional  
**Backwards-safe** — nothing breaks and existing content still works  
**Editor-friendly** — just one toggle per component

* * *

### In One Sentence

Instead of tracking everything automatically, we add one checkbox to each piece of content so only conversion-critical components get tracked and appear in analytics.

---

<div class="post-metadata">

**Author:** ![manish-sharma](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@manish-sharma](https://forum.builder.io/u/manish-sharma)\
**Post date:** [October 23, 2025, 6:37pm UTC](https://forum.builder.io/t/component-tracking-for-conversions/15888/2 "2025-10-23T18:37:08Z")

</div>

Hello @Matandessaur,

Thank you for sharing this idea! We understand that tracking everything by default — headers, nav bars, footers, and other non-conversion elements — can make analytics noisy and harder to interpret.

Your suggestion of an **“Enable Conversion Tracking”** toggle per component is a thoughtful approach. This would allow teams to track only conversion-critical elements in Insights while leaving visual views and billing metrics unaffected.

As an alternative, we currently provide SDK and page-level options to control tracking:

- **Gen 2 SDK:** `<Content canTrack={false} />`
- **Gen 1 SDK:** `builder.canTrack = false`
- **HTML API:** `window.builderNoTrack = true`

> **[GDPR and US Compliance](https://www.builder.io/c/docs/gdpr#disable-tracking)**
>
> Builder is an AI-Powered Visual Development Platform that helps teams generate, iterate, and optimize web and mobile experiences in seconds instead of sprints.

These can be combined with a per-component opt-in approach to give fine-grained control over analytics.

We’ll **submit this as a feature request** for our product team to review. While we can’t provide a timeline for implementation, your feedback helps us prioritize improvements that make [Builder.io](http://Builder.io) more actionable and privacy-conscious.

Thanks again for taking the time to share your input!