Events, tags, attributes, and ping

These APIs require an initialized SDK and, except where noted, a current user from setUser. If no user is set, tag/attribute/ping methods return without sending a request.

Tags

• addTags(_ tags: [String], completion: ((Result<Void, Error>) -> Void)? = nil) — POST to add tags for the current user.
• removeTags(_ tags: [String], completion: ((Result<Void, Error>) -> Void)? = nil) — DELETE to remove tags.

Attributes

• setAttributes(_ attributes: [String: Any], completion: …) — JSON-encodable values are wrapped for the wire format.
• addOrUpdateAttributes(_ attributes: [String: Any], completion: …) — convenience alias aligned with other MotiSig SDKs.
• removeAttributes(keys: [String], completion: …) — DELETE selected keys.

Values must be encodable in practice for your payloads; unsupported types may fail at encode time and be logged.

ping()

Sends a heartbeat-style request for the current user (POST /users/{id}/ping). Useful for presence or liveness if your backend uses it.

triggerEvent(eventName:data:completion:)

Sends POST /events for the current user.

• eventName: server-defined event name.
• data: optional [String: Any] JSON-serializable payload; omitted when nil.
• completion: optional; on success, called with Result.success carrying the server message string. On failure (including no user), called with Result.failure.

If there is no current user, the completion is invoked immediately with MotiSigError.userNotSet (and no request is enqueued).

If the SDK is not initialized or the instance is unavailable when the queued work runs, the completion may receive MotiSigError.notInitialized.

The completion runs on the Swift concurrency cooperative thread pool (not guaranteed to be the main queue). Dispatch to the main actor yourself if you update UI.

Related

• User and profile
• MotiSigError in the SDK source for error cases