Why are custom attributes displayed incorrectly in Google Workspace signature?

Scenario

You are using Exclaimer Cloud to create and apply signatures to messages sent from Gmail.

Within Google Workspace, you are using custom attributes to store user data and have created signatures to include these attributes. However, when these signatures are applied, you notice that custom attribute information is displayed oddly - typically, a numbered name for the field is displayed (for example: {Custom.1000.883.1}).

Reason

When defining custom attributes, Google Workspace allows you to create them with whatever name you wish, including special characters and symbols. However, the API provided by Google (which we use to integrate Exclaimer Cloud) only allows:

• alphanumeric characters
• underscores
• hyphens

This is documented here.

Therefore, there is a conflict between data that Google allows you to define in Google Workspace and data that they allow Exclaimer Cloud to handle.

Resolution

This is a Google support issue, and we hope it will be addressed in due course. In the meantime, please ensure that only alphanumeric characters, underscores, and hyphens are used when creating signatures in Exclaimer Cloud.