Send logged in signals with the API

Send a logged in signal to Connect with the createSignals mutation. For authentication, contact mapping, consent and the response, see Send signals with the API (GraphQL).

Triggers when a user successfully authenticates on your website or app.

mutation {
  createSignals(
    signals: [
      {
        appKey: "{YOUR_APP_KEY}"
        sessionId: "SESS-789456123AB"
        audience: [
          { name: "Email", value: "[email protected]" }
        ]
        signalContent: {
          signalType: "loggedIn"
          category: "Behavior"
          name: "Logged in from website"
          effect: "positive"
          loginMethod: "sso"
          ssoProvider: "google"
          mfaUsed: true
          mfaMethod: "totp"
          signalTimestamp: "2026-02-28T16:22:15.001Z"
        }
      }
    ]
  ) {
    signalIds
  }
}

Required fields

• loginMethod : String - Authentication method used. Examples: email, password, passwordless, sso.
• signalType : String - Signal type. Valid value: loggedIn.

Optional fields

• category : String - Signal category. Valid value: Behavior.
• description : String - Description of the signal.
• effect : String - Signal engagement effect. Valid values: negative, positive. Use positive for login signals.
• mfaMethod : String - MFA method used when mfaUsed is true. Examples: SMS, email, TOTP, biometric.
• mfaUsed : Boolean - Whether MFA was used during login.
• name : String (up to 256 characters) - Signal name to differentiate from other signals.
• signalCustomAttributes : Array of objects - Additional custom attributes (each object needs name and value string 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 when loginMethod is sso. Examples: Google, Microsoft, Facebook.