We are using the Fivetran mParticle destination connector to send conversion events to Rokt via mParticle. As part of this integration we need to map a hashed email field to mParticle's other identity type for user matching on the Rokt side.

Currently the connector only supports email and customer_id identity types in the field mapping. The other identity type is not available as a mapping option, which is blocking our ability to complete the integration.

Requested change: Please add the other identity type as a mappable identity field in the mParticle destination connector.