Send events
Identifiers
Tell BreezeIQ who an event is about: email, phone, cookie and device id.
Identifiers are how BreezeIQ knows two events belong to the same person. Put every identifier you know in properties.identifiers: the more you send, the better events stitch together.
Identifier types#
Strong identifiers name a person. Weak ones name a device, which may be shared.
| Type | Strength | How it's matched |
|---|---|---|
email | Strong | Trimmed and lowercased, so [email protected] equals [email protected]. |
phone | Strong | Normalised to E.164. Numbers without a country code are treated as Indian (9812345678 → +919812345678). |
cookie | Weak | Browser cookie id. Allowed from browser events. |
device_id | Weak | App or device id. Allowed from browser events. |
A shared device can never glue two known customers together. See Profiles & identity for how matching and merging work.
Sending identifiers#
Each type takes a single value, a list, or objects with a value:
"identifiers": {
"email": "[email protected]", // a single value
"phone": ["+919812345678", "+919900112233"], // several values
"cookie": [{ "value": "3f9a1c7e" }], // object form
"device_id": "a1b2c3d4-e5f6-4711-9c2d-1f2e3d4c5b6a"
}Rules#
| Rule | What happens |
|---|---|
| Only declared types count | Each tenant has a list of identifier types. Unknown types in an event are ignored; if nothing usable is left, the event is rejected. |
| At most 10 values | Per event, across all types. |
| Placeholders are ignored | Values configured as "noise" (such as [email protected]) never link anyone. Ask the BreezeIQ team to add yours. |
Identifiers are protected
Identifier values are encrypted at rest and never appear in webhooks. See Data & privacy.