Connection
Where the Qinto worker answers. When this page is hosted on the same domain as the worker, that domain is the answer. It is remembered for next time.
How this works
- Connect — the worker creates an anonymous profile for this browser and stores a visitor ID in a secure cookie.
- Say who they are — an email, a phone number, or your own customer ID turns that anonymous browser into a person profile.
- Send events and consent — everything lands on that person and follows them to their other devices.
The guided run connects, views a page, invents a person, buys something, saves consent, and reads the consent back — about ten seconds end to end.
Good to know
- The visitor cookie is deliberately unreadable by this page, so the anonymous ID is not shown here.
- To arrive as a brand-new visitor, open this page in a private window.
- Sending the same email from two browsers links both to one person — that is the point of the graph.
- Everything you send is real. Point this at a test deployment, not one carrying live customer data.
Ready-made events
One click each. The purchase also counts as a conversion, because it carries an amount and an order number.
Make up your own
Details are sent as text unless they look like a number or true/false.
Details
Say who the visitor is
An email address or phone number turns the anonymous browser profile into a person profile — the record that follows this person across their devices. Leave anything blank that you do not want to send.
How to reach them
Name
Where they are
Where they came from
Sending this person also sends whatever custom properties are listed below.
Custom properties
Anything the graph does not know by name is kept as your own property on the person — a plan, a loyalty tier, a
lifetime value. Values that look like a number or true/false are sent as such; write null to remove a
property that is already stored.
Link another ID
Attach an extra identifier — a loyalty number, a CRM ID, a second email. Anything sent later with that ID lands on this same person.
What this person agreed to
Consent is remembered per person, so it follows them to their other devices. “Strictly necessary” is always on and cannot be switched off.
Individual apps (optional)
Record a decision for a single named app, on top of the categories above. Name any app you like.
Send a raw message
Messages are validated strictly: unknown fields are rejected. A ref is added automatically if you leave
it out, so replies can be matched to what you sent.
Read data back over HTTP
These endpoints need a worker access token from the Qinto platform. Without one the worker answers
unauthenticated — itself a valid thing to see here. The visitor is taken from the cookie set when you
connected.
Kept for this browser tab only and forgotten when you close it — the platform shows a token once, so this page never writes it to long-term storage.