[codex] Remove product-app marketing pixels#2716
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
e40bbd3 to
d1fec16
Compare
d1fec16 to
c56a1fb
Compare
claudfuen
pushed a commit
that referenced
this pull request
Apr 30, 2026
# [3.39.0](v3.38.1...v3.39.0) (2026-04-30) ### Bug Fixes * **api:** correct fileData max-length to 100MB and allow localhost in URL validation ([6d56a2d](6d56a2d)) * **api:** correct type casting for rawBody in main.ts ([7e624d4](7e624d4)) * **app:** remove product app marketing pixels ([#2716](#2716)) ([26d75be](26d75be)) * **background-checks:** fix 13 bugs across billing, webhooks, custom uploads, and UI ([d5df5db](d5df5db)) * **background-checks:** remove employee PII from sessionStorage ([ea082b3](ea082b3)), closes [#133](#133) * **background-checks:** security hardening across payment flow, validation, and logging ([8b3b39b](8b3b39b)) * **pentest:** bump split-view breakpoint from md to xl for tablet support ([efd1c85](efd1c85)) ### Features * **background-checks:** add employee background checks ([0456df6](0456df6))
Contributor
Author
|
🎉 This PR is included in version 3.39.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes product-app marketing tracking from
app.trycomp.aientirely. The app keeps PostHog product analytics, while GTM, Google Ads/GA4 conversion tracking, LinkedIn Insight, and LinkedIn conversion APIs stay out of the product app.What changed
@next/third-parties.conversionevent and ad conversion sends.purchase_completedevents are product analytics only; paid-media revenue, customer, and signed-deal measurement lives in HubSpot lifecycle imports.Conversion-source check
HubSpot - Lead(7210738292),HubSpot - Marketing Qualified Lead(7210866133), andHubSpot - Opportunity(7210867384) all have typeUPLOAD_CLICKS,include_in_conversions_metric=true, andprimary_for_goal=true.HubSpot - Customer(7210867654) is the CRM-side customer/purchase-class import; it is intentionally secondary today.Purchase (2)(7524378447) is a legacy web conversion action, but it is not primary, not included in Conversions, and has 0 all-time conversions in the account query. Removing product-app ad pixels does not remove a meaningful biddable app conversion path.Book a Call(7215323435) remains a primary web conversion from the marketing site/demo, not from the product app. So the practical biddable source mix is HubSpot imports plus marketing-site demo booking, not product-app pixels.Portal check
apps/portalfor GTM, Google Ads/GA4, LinkedIn Insight/CAPI,dataLayer,lintrk, and marketing-pixel envs.AnalyticsProviderandNEXT_PUBLIC_POSTHOG_*envs.Validation
git diff --checkandgit diff --cached --checkpassed.rg.rg.bun --filter @trycompai/app typecheckstill fails on existing generated DB/test/auth typing issues unrelated to this patch.