TY Bridge was built to solve a very specific problem. Because of that, it also has very deliberate boundaries.
This page explains what TY Bridge does not do — not as a disclaimer, but as a statement of intent.
TY Bridge is not a full analytics suite
TY Bridge does not aim to replace platforms that focus on:
- Attribution modeling
- Customer journey analysis
- Session replay or heatmaps
- Long-term data warehousing
Its purpose is narrower: restoring accurate post-purchase events under Shopify’s new checkout model.
TY Bridge does not bypass Shopify’s platform rules
TY Bridge does not attempt to:
- Inject arbitrary JavaScript into checkout pages
- Work around pixel sandbox restrictions
- Re-enable deprecated script surfaces
Any solution that depends on bypassing these rules is fragile and likely to break again.
TY Bridge does not ignore customer consent
TY Bridge does not:
- Fingerprint customers
- Fabricate identifiers when consent is denied
- Send marketing data without permission
- Collect or send IP address or user agent without explicit consent
We do not store raw customer contact data (email or phone). When Enhanced Matching is enabled, hashed email or phone may be forwarded only when marketing consent is granted.
If Enhanced Matching is enabled, IP address and user agent may be forwarded only when marketing consent is granted, and are never stored.
Consent enforcement is not a limitation to work around. It is a requirement to design around.
TY Bridge does not promise perfect attribution
No system can guarantee perfect attribution — especially in a privacy-constrained environment.
TY Bridge focuses on delivering the best possible signal quality that Shopify allows, with transparency about what was sent and why.
TY Bridge does not require agencies to resell software
Agencies using TY Bridge are not required to:
- Manage licenses
- Handle billing
- Provide first-line technical support
Agencies remain advisors. TY Bridge remains infrastructure.
Why these boundaries matter
Clear boundaries reduce complexity, prevent hidden failure modes, and keep expectations aligned.
TY Bridge is designed to coexist with other tools — not replace everything in a merchant’s stack.
The takeaway
What TY Bridge does not do is as important as what it does.
These constraints are what make the system stable, consent-aligned, and trustworthy over time.