Send an error signal to Connect with the createSignals mutation. For authentication, contact mapping, consent and the response, see Send signals with the API (GraphQL).
To learn what this signal captures and how to use it in Connect, see Application error signal guide. To send it from your website or app instead, use Log signal: web, Android, iOS.
Sent when a user encounters an error on your site. Focus on payment, promo code, and account registration errors that lead users away from the happy path.
mutation {
createSignals(
signals: [
{
appKey: "{YOUR_APP_KEY}"
audience: [{ name: "Email", value: "[email protected]" }]
sessionId: "SESS-789456123AB"
signalContent: {
signalType: "error"
category: "Behavior"
name: "Shopping cart error"
effect: "negative"
errorText: "This promo code is invalid."
errorType: "USER"
errorIdentifier: "promoCode"
signalTimestamp: "2026-02-22T08:29:30.001Z"
}
}
]
) {
signalIds
}
}Required fields
errorText: String - Error message content receivederrorType: String - Error type (valid values:application,user) - Application errors are server-side/system errors; user errors occur when input doesn't pass validation.signalType: String - Signal type (valid value:error)
Optional fields
category: String - Signal category (valid value:Behavior)description: String - Description of the signaleffect: String - Signal engagement effect. Valid values:negative,positive. We suggestnegativefor all error signals.errorIdentifier: String - Error identifier (e.g., "promoCode")name: String (up to 256 characters) - Signal name to differentiate from other signalssignalCustomAttributes: Array of objects - Additional custom attributes (each object needsnameandvaluestring fields)signalTimestamp: 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.
