feat(telemetry): add Leadpipe tracking script

[tgberkeley]

Add get_leadpipe_trackers() to reflex-components-internal and wire it into the website pixel tracker list in reflex-site-shared.

All Submissions:

• Have you followed the guidelines stated in CONTRIBUTING.md file?
• Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

New Feature Submission:

• Does your submission pass the tests?
• Have you linted your code locally prior to submission?

Changes To Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

After these steps, you're ready to open a pull request.

a. Give a descriptive title to your PR.

b. Describe your changes.

c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).

[greptile-apps]

Greptile Summary

This PR adds a Leadpipe analytics tracking integration to the internal components library and wires it into the website's pixel tracker list. The implementation is minimal and consistent with the existing telemetry module conventions.

• leadpipe.py defines get_leadpipe_trackers() using rx.script(src=...) with the CDN URL extracted into a named constant LEADPIPE_SCRIPT_URL.
• The function is exported via __init__.py and added to the get_pixel_website_trackers() list in pixels.py.

Confidence Score: 5/5

Safe to merge — small, self-contained addition that follows the established telemetry module pattern.

The change adds a single new tracker function with a named URL constant, correct type annotation, and a docstring. It integrates cleanly into the existing pixel tracker list with no logic changes to surrounding code.

No files require special attention.

Important Files Changed

Filename	Overview
packages/reflex-components-internal/src/reflex_components_internal/blocks/telemetry/leadpipe.py	New Leadpipe tracking integration using rx.script(src=...) with the URL extracted into a named constant; consistent with the module's expected pattern.
packages/reflex-components-internal/src/reflex_components_internal/blocks/telemetry/init.py	Adds get_leadpipe_trackers to imports and all in alphabetical order; no issues.
packages/reflex-site-shared/src/reflex_site_shared/telemetry/pixels.py	Wires get_leadpipe_trackers() into the website pixel tracker list; straightforward addition with no issues.

_{Reviews (2): Last reviewed commit: "Update packages/reflex-components-intern..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 26 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing leadpipe-tracker (80763be) with main (767c111)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩