Send an identification (legacy) signal to Connect with the createSignals mutation. For authentication, contact mapping, consent and the response, see Send signals with the API (GraphQL).
To send it from your website or app instead, use Log signal: web.
Captures visitors' emails or customer IDs as they browse your website. This signal is still supported but is no longer necessary — starting from the March 2026 release, all signals include contact mapping via the audience object.
mutation {
createSignals(
signals: [
{
appKey: "{YOUR_APP_KEY}"
audience: [{ name: "Customer ID", value: "AAUN-1417508" }]
sessionId: "SESS-789456123AB"
signalContent: {
signalType: "identification"
category: "Behavior"
name: "Identification from login"
effect: "positive"
identifierName: "email"
identifierValue: "[email protected]"
identificationFromLogin: true
signalTimestamp: "2026-02-22T08:29:30.001Z"
}
}
]
) {
signalIds
}
}Required fields
identifierName: String - Identifier type (valid values:email,sms,contactKey)identifierValue: String - Contact information associated with visitor (type depends onidentifierNamevalue)signalType: String - Signal type (valid value:identification)
Optional fields
category: String - Signal category (valid value:Behavior)description: String - Description of the signaleffect: String - Signal interpretation for engagement index scoring (valid values:negative,positive)identificationFromLogin: Boolean - Set totrueifidentifierValuederives from user authentication,falseif from cookie/query string (separates explicit vs implicit identification)name: String (up to 256 characters) - Signal name to differentiate from other signalssignalTimestamp: Date - When signal happened (if omitted, Connect uses time when signal was received). Valid values: DateTime strings (ISO 8601). Example:2026-02-28T16:22:15.001Z.
