Check which Exclaimer product you use
This guide preserves the setup for the older Exclaimer Signature Manager products. It is not a verified setup for today’s Exclaimer cloud designer.
Exclaimer lists 30 September 2024 as the end of support for Signature Manager Exchange Edition and Outlook Edition in its product lifecycle information. Its current Signature Designer FAQ says you cannot edit a signature’s HTML directly.
If you use the current product, contact Hively support with the edition and designer you have before following the legacy paste-HTML steps. An Exclaimer label in Hively does not by itself establish compatibility with every Exclaimer product.
Existing Signature Manager mappings
For an existing compatible installation, open Configuration → Integrations → Exclaimer in Hively and match each person’s sender email address.
Use the address supplied by Exclaimer’s email field, which may differ from the person’s Hively sign-in address. Select Update, reopen Exclaimer from the integrations list, and copy the integration snippet using Show HTML. The standard field is {E-mail}; the standard Exclaimer snippet does not add a ticket field.
Maintain a legacy template
In the older Signature Manager source editor, the pasted email placeholders may need to be replaced with fields inserted by Exclaimer’s own field control.
Retain a copy of the existing template. At each {E-mail} placeholder in a rating-link destination, insert the actual E-mail field using the editor and remove the corresponding literal placeholder. Check every face and the text link; the number of links depends on your snippet style. Avoid replacing unrelated parts of a working URL.
These are maintenance instructions for the legacy editor. Do not convert a current cloud signature on the assumption that it offers the same source-editing workflow.
Check before changing a live rule
Test messages from two mapped senders and compare the email value in each received rating link with the Hively mapping.
Use the integration checklist. Unresolved fields, alias differences and a shared fixed address can send feedback to the wrong person. For a cloud migration or incompatible editor, email Hively support with the product/version and the workflow you need.