Skip to content

chore(Tracking): Remove the unused Capterra conversion pixel - #8712

Draft
Holmus wants to merge 1 commit into
mainfrom
chore/remove-capterra-pixel
Draft

Holmus wants to merge 1 commit into
mainfrom
chore/remove-capterra-pixel

Conversation

@Holmus

@Holmus Holmus commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Thanks for submitting a PR! Please check the boxes below:

  • I have read the Contributing Guide.
  • I have added information to docs/ if required so people know about the feature. (Not required: the setting isn't documented.)
  • I have filled in the "Changes" section below.
  • I have filled in the "How did you test this code" section below.

Changes

The Capterra conversion pixel fired when an organisation was created, and it was added to the page as a visible image. Browsers that block trackers showed it as broken-image icons under the page. Capterra tracking isn't used any more.

  • Remove the pixel from both organisation-creation forms.
  • Remove the image helper that only the pixel used, and the capterraKey project setting.

After merging, the CAPTERRA_API_KEY environment variable can be removed wherever it's set.

Review effort: 1/5

How did you test this code?

  • Locally: CI=true lint on changed lines and the full unit test suite pass. Type errors are unchanged from main.
  • Create an organisation (from the organisation modal and from /create) with a tracker blocker on, and confirm no broken images appear.

🤖 Generated with Claude Code

The Capterra pixel fired on organisation creation as a visible image, so
browsers that block trackers showed broken-image icons on the page. Capterra
tracking is no longer used, so the pixel, its image helper and the
capterraKey project setting are removed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
flagsmith-frontend-preview Building Building Preview Oct 9, 2026 3:16pm UTC
flagsmith-frontend-staging Ready Ready Preview Oct 9, 2026 3:16pm UTC
1 Skipped Deployment
Project Deployment Actions Updated
docs Ignored Ignored Oct 9, 2026 3:16pm UTC

Request Review

@coderabbitai

coderabbitai Bot commented Oct 9, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

This branch was successfully deployed

2 active deployments
Preview – flagsmith-frontend-staging — be9b4fc8 Deployed Oct 9, 2026 by vercel[bot]
Preview – flagsmith-frontend-preview — be9b4fc8 Deployed Oct 9, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore front-end Issue related to the React Front End Dashboard

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant