Odd behaviour with custom attributes in Exclaimer Cloud - Signatures for G Suite

Scenario

You are using Exclaimer Cloud - Signatures for G Suite, to create and apply signatures to messages sent from Gmail.

Within G Suite, 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, G Suite 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 - Signatures for G Suite) only allows:

  • alphanumeric characters
  • underscores
  • hyphens

This is documented, here.

Therefore, there is a conflict between data that Google allows you to define in G Suite, and data that they allow Exclaimer Cloud - Signatures for G Suite, to handle. 

Solution

This is a Google support issue, and we hope that 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 - Signatures for G Suite.

Haven't found a solution to your problem?

Please click the button below, login to the Exclaimer Cloud portal and raise a support ticket. A member of the Exclaimer Support team will then be in touch.

Raise a support ticket