01 · Foundations
How Hyros stitches identity, the 6-axis connector evaluation framework, and the can-we/can't-we framing.
How Hyros stitches identity
Hyros ties every touch — ad click, page view, call, sale — back to a single person using four identifiers: email, phone, IP address, and session id. Email (or phone) is the primary join key when a connector sends an action: same email/phone = same lead, updated in place. IP and session id let Hyros stitch a person even before they hand over an email. If we can't supply at least one reliable identifier, we can't attribute the action.
The 6-axis connector evaluation framework
Before answering any client request, walk these six axes. They turn a vague ask ("can we sync GHL?") into a concrete yes/no/how. Identity and field mapping are where most requests fail — if the source can't give us an email, the rest doesn't matter.
- 1
Identity
What identity key ties this action to a lead (email, phone)?
e.g. A booking page passes email via a redirect param → we can stitch.
- 2
Direction
Is data pushed INTO Hyros (API) or pulled OUT (webhooks)?
e.g. “Send the sale to Hyros” = API in. “Export to a sheet” = webhook out.
- 3
Trigger
What event in the source platform should fire the action?
e.g. GHL workflow “Opportunity → Won” triggers POST /orders.
- 4
Field mapping
Which fields map to Hyros' required inputs (and which are missing)?
e.g. Map deal total → amount, deal close date → date, contact email → email.
- 5
Real-time vs batch
Does it need to happen live, or is a periodic sync / CSV fine?
e.g. Live call tracking = real-time; historical backfill = CSV upload.
- 6
Attribution impact
How badly does getting this wrong corrupt attribution?
e.g. A bad sale event (Critical) is worse than a missing tag (Low).
The can-we / can't-we framing
Every client ask resolves to one of three answers: (1) Yes via API — we push the action in with the right fields. (2) Partial — possible but with a caveat (e.g. tag behavior, or only via CRM trigger). (3) No — typically when they want to pull data OUT of Hyros (that's webhooks, not the API) or when no identity key exists. Use the Capability Matrix for the fast lookup and the Request Explorer to prove it.