Send an account registered signal to Connect with the createSignals mutation. For authentication, contact mapping, consent and the response, see Send signals with the API (GraphQL).
Other ways to send this signalWeb · Android (identify) · iOS (identify)
All signals and methods: Signals overview
Triggers when a user successfully completes account registration on your website or app.
mutation {
createSignals(
signals: [
{
appKey: "{YOUR_APP_KEY}"
sessionId: "SESS-789456123AB"
audience: [
{ name: "Email", value: "[email protected]" }
]
signalContent: {
signalType: "accountRegistered"
category: "Behavior"
name: "Account registered from website"
effect: "positive"
registrationMethod: "sso"
ssoProvider: "google"
registrationSource: "checkout"
mfaEnabled: true
signalTimestamp: "2026-02-28T16:22:15.001Z"
}
}
]
) {
signalIds
}
}Required fields
registrationMethod: String - Method used to register. Examples:email,sso,passwordless.signalType: String - Signal type. Valid value:accountRegistered.
Optional fields
category: String - Signal category. Valid value:Behavior.description: String - Description of the signal.effect: String - Signal engagement effect. Valid values:negative,positive. Usepositivefor account registrations.mfaEnabled: Boolean - Whether MFA was enabled during registration.name: String (up to 256 characters) - Signal name to differentiate from other signals.registrationSource: String - Page or campaign that initiated registration. Examples:homepage,checkout,promotion.signalCustomAttributes: Array of objects - Additional custom attributes (each object needsnameandvaluestring fields).signalTimestamp: Date - When the signal happened (if omitted, Connect uses the time the signal was received). Valid values: DateTime strings (ISO 8601). Example:2026-02-28T16:22:15.001Z.ssoProvider: String - SSO provider whenregistrationMethodissso. Examples:google,facebook,apple.
