TY Bridge is intentionally narrow in scope. It exists to solve one problem well: restoring reliable post-purchase tracking after Shopify’s checkout changes.
This page explains how TY Bridge works at a system level — not as a feature list, but as an architectural flow.
The core idea
Under Shopify’s current rules, no single layer can do everything. Browser scripts are constrained. Pixels are sandboxed. Server-side systems must respect consent.
TY Bridge connects these layers cleanly instead of fighting them.
Step 1: Capture with an App Pixel
TY Bridge uses a Shopify App Pixel to observe checkout and purchase events that Shopify explicitly allows.
The pixel does not scrape the DOM or execute arbitrary logic. It listens for standardized events and extracts permitted context such as order ID, value, currency, and consent state.
Step 2: Sign and forward the event
Each captured event is signed and forwarded to TY Bridge’s backend. This prevents spoofing and ensures the event came from the correct shop.
Signed payloads are queued for reliable, async delivery with retries when destinations are slow or unavailable.
No customer-identifying data is invented or enhanced at this stage. Only what Shopify permits is forwarded.
IP address and user agent are forwarded only when Enhanced Matching is enabled and marketing consent is granted, and are never stored.
Step 3: Server-side evaluation
On the server, TY Bridge evaluates:
- Which destinations are enabled for the shop
- Whether marketing consent was granted
- What identifiers may legally be included
This step ensures downstream platforms receive only consent-permitted data.
Raw customer contact data (email or phone) is never stored. Hashed email or phone may be forwarded only when Enhanced Matching is enabled and marketing consent is granted.
Step 4: Deduplication and reliability
TY Bridge assigns deterministic event identifiers so that browser and server deliveries can be reconciled by ad platforms.
Events are delivered with retries and backoff, reducing loss caused by network failures or transient platform issues.
Step 5: Observability
Every delivery attempt is logged. Merchants and agencies can see:
- What events were captured
- What was sent to each destination
- Whether delivery succeeded or failed
This visibility replaces guesswork with evidence.
What TY Bridge deliberately avoids
To remain stable and consent-aligned, TY Bridge does not:
- Inject arbitrary JavaScript into checkout pages
- Bypass Shopify’s pixel sandbox
- Fingerprint customers
- Fabricate identifiers when consent is denied
These boundaries are intentional. They keep the system aligned with Shopify’s platform direction.
Why this architecture holds up
TY Bridge works because it accepts the constraints of the platform and designs within them.
By separating capture, evaluation, delivery, and observability, the system remains resilient as Shopify continues to evolve.
The takeaway
TY Bridge is not magic. It is careful system design applied to a forced platform transition.
If you want to understand why it works, this architecture is the answer.