Tracking
Identity
Site, visitor, session, browser — four ideas. One saner dashboard.
Identity
Velora does not smash everything into one mushy "user" cookie and pray.
The cast
| Identity | Lifespan vibe | Job |
|---|---|---|
| Site | Forever (your record) | Installs, queries, revenue links |
| Visitor | Long-lived browser id | Returning humans |
| Session | Short browsing burst | Group actions in one visit |
| Browser | Device/browser signal | Extra stitching evidence |
Plus identify hints when you tell Velora who logged in.
identify
On web, after login:
window.velora("identify", {
user_id: "user_123",
name: "Ada",
email: "ada@example.com",
});
That feeds the actor graph — aliases, evidence, timelines — so purchases and sessions can collapse into one person when the evidence is good.
Names you will see
Visitors get adjective+animal names and avatars. Rename them in the live feed. Your brain will thank you during incident hour.
Prompt
Add Velora identify() to my auth success path on YOUR_DOMAIN.
Call window.velora("identify", { user_id, name, email }) when the Velora script is ready.
Guard SSR. Show the diff. Do not send passwords or tokens.