Disclaimer · Comparison

Exclaimer and Conbool compared.

Both apply signatures centrally, on the server and while composing in Outlook, and both offer data centres in Germany. The clear difference is breadth: Conbool brings eight more modules in the same console. On top come legal details for German company forms, building blocks with their own schedule and operation right up to your own data centre.

6 points level8 additional modules

One discipline in common, eight only at Conbool.

Nine modules, one platform, one contract. Exclaimer specialises in email signatures and covers one of them.

CoverageConboolExclaimer
bothnot statedConbool only

Based on the portfolio publicly described on exclaimer.com, home page and pricing page, retrieved in September 2026. It lists email signatures with campaigns, analytics, directory sync and integrations. What your contract includes is set by the offer.

Level

Where neither has the edge.

A fair comparison starts with what both share. Both vendors offer these six points; the implementation differs in the details.

  • Server-side signatureConbool:Applied at the gateway on sending, identical on every device and mail client.Exclaimer:Server-side deployment on Microsoft Azure, included in all plans according to the pricing page.
  • Signature while composingConbool:Outlook add-in from Microsoft AppSource for Windows, Mac and web, even without changing the mail flow.Exclaimer:Client-side deployment where the signature is applied in Outlook or Gmail.
  • Signature in Sent ItemsConbool:Added to the sender's copy after delivery, with a separate consent. The original is never deleted.Exclaimer:Sent Items Update for Microsoft 365 mailboxes, not for Exchange on-premises according to the knowledge base.
  • Located in GermanyConbool:Servers in Frankfurt am Main, data held in the EU. The contracting party is Conbool GmbH, based in Hamburg.Exclaimer:Azure data centres Germany West Central and Germany North for customers in Germany. Exclaimer is headquartered in the United Kingdom.
  • Campaigns and clicksConbool:Campaigns and banners with their own time window, click counting in the portal or fixed campaign parameters for your own analytics tool.Exclaimer:Campaigns with schedules and target groups, click analytics in the Pro plan according to the pricing page.
  • Directory dataConbool:Microsoft Entra ID, LDAP and on-premises Active Directory through an outbound agent.Exclaimer:Sync with Microsoft Entra ID and Google Directory, plus integrations such as Workday.

In detail

Eight things Conbool brings.

Each point is described on a linked page and can be checked in a demo. Where we have no documented information about the other vendor, we claim no difference.

Anatomy of a message

Four building blocks, maintained separately.

Marketing maintains the campaign, legal the notice, IT the rules. Nobody touches anyone else's template, and a trade fair banner expires on its end date by itself.

To
Subject
1Banner

Message body

2Signature
3Campaign
Time window per block
4Legal notice

Quoted thread

  1. 1

    Banner

    Always at the top. Room for an event or a notice about external senders.

  2. 2

    Signature

    Name, title, direct line and photo from the directory. Empty fields hide their line.

  3. 3

    Campaign

    Its own block with its own time window. It follows the block before it, at the top below the banner or at the bottom below the signature.

  4. 4

    Legal notice

    Legal details from the central company data, either right after the signature or after the whole thread.

Time window per blockPosition per blockShort version for repliesTemplate per language

Deployment modes

Three ways to a signature.

Your environment decides which way fits. All three use the same templates in the same console. Moving from the add-in to the mail flow later needs no rebuild.

On the server in the mail flow

The message travels through a send connector to Conbool and receives its building blocks there. This applies to every device and mail client.

  • Enforceable, with all building blocks and rules
  • Requires changing the outbound mail flow
Outlook, phone, any client
Microsoft 365 or Exchange
Signature added hereConbool
Recipient

In the mailbox via add-in

The Outlook add-in inserts the signature while composing. The message content stays in Microsoft 365.

  • No change to MX, SPF or DKIM
  • Outlook with Exchange Online only, no banners or rule set, editable in the mailbox
Signature added hereOutlook with add-in
Microsoft 365
Recipient

Template and directory data come from Conbool, the message content does not go there

In your own data centre

Conbool runs as an installation at the customer between mail server and internet. Same templates, same rules, no third-party service in the mail flow.

  • Messages leave the building only towards the recipient
  • The installation is operated in-house
Mail server in-house
Signature added hereConbool in your data centre
Recipient

At Exclaimer

Exclaimer describes a server-side deployment on Microsoft Azure and a client-side one where the signature is applied in Outlook or Gmail. The pricing page lists Microsoft 365, Google Workspace and Microsoft Exchange as environments. By its own account, the service is built for Microsoft Azure.

Measuring campaigns

Count clicks without tracking recipients.

If you need to prove reach, switch on counting per template. The banner link then points to a Conbool address that counts and redirects immediately. If you prefer measuring in your own analytics tool, append fixed campaign parameters instead.

  1. 1

    Recipient clicks the banner or campaign

  2. 2

    Conbool verifies the signed link

  3. 3

    Automatic fetches by security filters are flagged

  4. 4

    Redirect to the target page

Stored

  • Building block
  • Target address
  • Time
  • Automated fetch yes or no

Not stored

  • Recipient address
  • Message identifier
  • IP address and browser string
  • Opens via tracking pixel

The portal report shows clicks per building block, automated fetches separately. There are deliberately no open rates, as they would require a tracking pixel.

Sent Items

Your own copy looks like the recipient's.

Exchange stores the copy when you hit send, before any server-side signature can be added. That affects every server-side signature, whichever the vendor. Conbool therefore adds the signature in the mailbox after delivery.

  1. 1

    Send in Outlook

  2. 2

    Exchange stores the copy in Sent Items, still without signature

  3. 3

    Conbool adds the building blocks and delivers

  4. 4

    The copy receives the same signature

The original is never deleted
Separate consent, apart from the connection
Only delivered messages are updated

Exclaimer offers a comparable update for Microsoft 365 mailboxes with Sent Items Update. At Conbool, the feature is available for Microsoft 365 mailboxes.

Switching

From Exclaimer to Conbool in four steps.

A switch starts with a pilot group. To avoid duplicate signatures, never leave both services active for the same senders, including the previous vendor's add-in.

  1. 1

    Review what exists

    Record active signatures, banners and rules from Exclaimer as a blueprint and save previous reports first.

  2. 2

    Connect the directory

    Connect Entra ID, LDAP or on-premises Active Directory and check which attribute fills which field.

  3. 3

    Templates and legal details

    Maintain company data centrally, pick starter templates and assign building blocks per rule.

  4. 4

    Pilot, then switch

    One department first, then switch off the Exclaimer rules and add-in and release the Conbool mail flow or add-in for everyone.

Our view

When Conbool is the right choice.

  • If you want to manage legal details under German law centrally, up to the GmbH & Co. KG with two register entries.
  • If you want signatures, email security, encryption and archiving from one contract instead of several.
  • If you want to choose how it runs, from the cloud with servers in Frankfurt to an installation in your own data centre.
  • If your directory stays in-house and you still need signatures from its attributes.
  • If you want to measure campaigns without capturing recipients through a tracking pixel.

To be fair

When Exclaimer is the right choice.

  • If you run Google Workspace alongside Microsoft 365 and want one signature solution for both.
  • If you want to target signatures at recipient lists from Salesforce or HubSpot, available in the Pro plan.
  • If you expect certifications of the vendor itself: Exclaimer lists ISO/IEC 27001, ISO/IEC 27018 and SOC 2 Type II.
  • If you want one-click satisfaction surveys in the signature, through a Customer Thermometer integration according to the pricing page.
  • If you only need signatures and already cover email security, archiving and backup elsewhere.

What prospects ask us.

Where the information comes from.

Statements about Exclaimer rely solely on publicly available sources, retrieved in September 2026: home page with the integrations overview and pricing page on exclaimer.com, the description of security and operations in the Email Signature Handbook, the press release on data centres in Germany and the Sent Items Update article in the knowledge base. Where a source is silent, we claim nothing. Statements about Conbool rely on our own documentation and contractual commitments. Products change, so we recommend asking both vendors about the points that matter to you and getting the answers in writing.

Exclaimer is a trademark of Exclaimer Ltd. Google Workspace is a trademark of Google LLC. Microsoft 365, Outlook, Exchange and Entra are trademarks of the Microsoft group of companies. This page is an editorial comparison by Conbool GmbH and not material of the vendors named.

See both in one demo.

We show a message with all four building blocks, the legal details for your company form and click counting, with your own template if you like.