# TSActionEventOptions

Options for reporting an action event via [`triggerAction()`](/sdk-ref/flutter-ts-accountprotection/drs#triggeraction).

## Properties

### correlationId

• `Optional` **correlationId**: `String`

Any ID that could help relate the action with external context or session. To link actions that belong to the same flow across devices, pass the same ID with every action in the flow. See [Cross-session correlation](/guides/risk/cross_session_correlation). If cross-device correlation is enabled for your tenant, the ID must be up to 128 characters and contain only letters, digits, `.`, `_`, `:`, and `-` (no spaces). Standard base64 (with `+`, `/`, or `=`) isn't supported, so use a UUID or base64url instead. An ID in a different format isn't used for correlation, but the action is still evaluated.

### claimedUserId

• `Optional` **claimedUserId**: `String`

User ID of the not yet authenticated user, used to enhance risk and trust assessments. Should not contain any sensitive data in plain text. Once the user is authenticated, [`setAuthenticatedUser()`](/sdk-ref/flutter-ts-accountprotection/drs#setauthenticateduser) should be called.

### claimedUserIdType

• `Optional` **claimedUserIdType**: [`TSClaimedUserIdType`](/sdk-ref/flutter-ts-accountprotection/enums/tsclaimeduseridtype)

The type of the claimed user ID (for example, email, username, or phone number). Helps Mosaic correctly interpret and correlate the identifier across sessions.

### referenceUserId

• `Optional` **referenceUserId**: `String`

A secondary user identifier that can help correlate the action with an internal reference

### transactionData

• `Optional` **transactionData**: [`TSTransactionData`](/sdk-ref/flutter-ts-accountprotection/interfaces/tstransactiondata)

Transaction data-points object for transaction monitoring