If you’re encountering issues with setting up Identity Verification in Featurebase, there are typically two reasons: the user hash is missing from the request, or the provided user hash doesn’t match what Featurebase expects.

Diagnosing the issue

Start by checking your browser console for any errors related to the user hash. For example, you might encounter a 400 Bad Request error, which often indicates a problem with Identity Verification.

In this example, Identity Verification is required, but an invalid userHash is being sent. Without a valid userHash, Identity Verification will fail, and the user will not be identified in Featurebase.

Common Identity Verification Errors

Missing userHash

If the console reports a missing userHash, ensure that you're generating it correctly using the Identity Verification secret from your Featurebase workspace settings, along with a unique identifier (such as userId or email).

Invalid userHash

If you're sending a userHash but it’s deemed invalid by Featurebase, there are several things to verify:

Are you using the correct Identity Verification secret?

• Ensure you’re using the secret from Dashboard → Settings → Identity Verification when creating an HMAC for the user.

Are you including the correct user identifier with the userHash?

• For the Identity Verification check to succeed, you must send both the userHash and the identifier (e.g., userId or email) that you used to generate the hash. If you're hashing with userId, ensure that the userId is also included in the request.

Are you generating the hash with the right data?

• The hash must be generated using the same identifier you're sending with the request. Here’s what to check:

  If you send both userId and email, generate the userHash using userId.

• If you send just userId, generate the userHash using userId.

• If you send just email, generate the userHash using email.

Did you send the userHash with the correct key?
The hash should be sent as userHash (not user_hash, as in other platforms). Ensure the naming matches exactly in your request payload.

Additional Troubleshooting Steps

Use the hash checker at Dashboard → Settings → Identity Verification to verify you’re creating valid hashes.

Still having issues?

If the above steps didn’t resolve your problem, don’t hesitate to reach out to the Featurebase support team. Make sure to include:

• A sample user who is experiencing the issue

• The errors displayed in your browser console or IDE logs

Reach out to us via the live chat or by emailing team@featurebase.app