Skip to content

Coming soon The PBM campaign platform launches in Q1 2027. Register for a demo →

Campaign Platform
DE EN
Contact Book a demo
Book a demo

Platform

One campaign platform, nine functions – and control at every step

The PBM Campaign Platform is GDPR-compliant software for personalised, automated customer communication via email, letter, insert, SMS, landing page, customer portal and app – for banks, insurers, energy suppliers and SMEs. The provider is PBM Personal Business Machine AG from Cologne.

Book a demoHow the platform works
  1. Address individually
  2. Stay in control
  3. Organise & measure

What functions does the PBM Campaign Platform offer?

Nine functions in three groups. All work on the same customer base and in the same journey.

Address individually

  • Personalisation Core

    Text, image, argument, channel, timing and sender adapt to each customer – using only data approved for that purpose.

  • Journey Builder

    Build journeys visually: send, wait, branch, tasks for advisers, goals. Four checks before every entry.

  • Multichannel

    Email, letter, insert, SMS, landing page, customer portal and app in one journey. If there is no email consent, the letter is used instead.

Stay in control

  • AI with approval

    The AI develops content. You decide. Every suggestion is checked and approved.

  • Contact frequency management

    Upper limits, minimum intervals and quiet periods across all campaigns and channels. The more important message takes priority.

  • Consent & compliance

    Consent per channel checked before every send. A withdrawal stops running journeys immediately.

Organise & measure

  • Roles, permissions & approvals

    What someone is allowed to do and what someone can see are separate questions. Both are checked on every access.

  • Brands & locations

    Head office sets the framework, and every location speaks in its own brand.

  • Analytics & reporting

    Opens, clicks, landing page visits and conversions per campaign, brand and channel – without third-party cookies.

Architecture

What principles is the PBM Campaign Platform built on?

Five decisions shape every function. They are the reason why data protection, IT and business departments can all approve the same platform.

  1. Single-tenant: your own installation. Every company receives a fully isolated installation in its own Kubernetes cluster. No data shared with other companies. Hosting in Germany by default, optionally AWS, Microsoft Azure or your own environment.

  2. Rules decide, AI suggests. Which variant, which channel, which timing: this is determined by a deterministic rule engine. The AI is an optional layer on top – it drafts suggestions; no language model makes decisions in the sending path. The AI can be switched off.

  3. A compliance gate before every send. There is exactly one point that triggers a send. Before it, the platform checks consent, contact rules and mandatory information. This gate cannot be bypassed with a switch.

  4. Everything business-related in the interface. You configure attributes, segments, contact rules, approval policies and brand CI in the front end – without configuration files and without a new release.

  5. Openly connected. Versioned REST API, service accounts, events from your core systems. Free choice of email and SMS providers, letter handover via SFTP to your print service provider, optionally your own S3 storage. Export at any time.

Details for IT and data protection in the Trust Centre

Process

How does the PBM Campaign Platform work – from import to measurement?

Five steps. You define the rules once; after that, the campaign runs individually for each contact.

  1. Import

    Upload your customer base as a file or connect your core system via API. The AI suggests which column belongs to which attribute; you confirm. A repeat import updates – it never deletes.

    Import · AI mapping AI suggestions
    bestand_export_2026-09.csv 84,312 rows
    Source columnAttributeAI confidence
    VERTR_ENDE vertrag_ende 97 %
    KD_BERATER berater 91 %
    EMAIL_OK consent_email 88 %
    KZ_SONDER unclear – please assign

    Upsert via customer number · does not delete any contacts

    Example · demo dataImport with AI mapping: the AI suggests an attribute with a confidence score for each source column; you assign unclear columns yourself. An import does not delete any contacts.

  2. Segment

    Describe who is to be addressed, for example “Contract ends in 90 days”. The segment is dynamic: anyone who meets the condition today starts today.

  3. Journey

    Build the flow on the canvas: channel according to consent, waiting for the landing page visit, reminder, task for the adviser, goal. Before entry, the platform checks four things: matching journey, data and consent, re-entry, priority.

    Journey · Wiederanlage Leben 2026 Regionalbank Musterstadt eG
    1. Entry Segment: expiry ≤ 90 days
    2. Gate Consent per channel
      • Letter Announcement
    4. Wait for event LP login · 7 days
    5. No
      • Reminder Reminder letter
    6. Exit completed
    7. Yes
      1. Landing page Personal overview
      2. Condition Lead score ≥ 60
      3. Task Notify adviser C. Reuter
      4. Goal · macro Appointment arranged

    Properties

    Entry: segment

    Condition
    vertrag_ende ≤ today + 90 days
    Segment
    dynamic
    Example · demo dataExample journey ‘Wiederanlage Leben 2026’ in the Journey Builder: entry via a segment, consent check, channel switch between email and letter, waiting for the login, reminder, handover to the adviser and the goal ‘Appointment booked’. Fictitious example data.

  4. Approval

    Content and campaign go through review: AI compliance check, then human approval, by default according to the four-eyes principle. Every approval is recorded in the audit log.

    Content · Reinvestment · Introduction field

    AI suggestion · not yet accepted

    Your fixed-term deposit expires on 31 March – secure your terms now before it’s too late. You will find three options in your personal overview.

    Compliance & tone check

    • no return promises
    • Mandatory notice present

    Tone: “too urgent”

    Suggestion: “secure your terms now … before it’s too late” → “You can decide at your own pace how to proceed.”

    Created by: J. Neumann · Approval by: C. Reuter (four-eyes)

    Approved · C. Reuter · Four-eyes

    logged · 25 September 2026 10:42

    Example · demo dataAI suggestion in the content editor: the compliance check flags an overly urgent tone; approval follows the four-eyes principle and is logged. Fictitious example data.

  5. Delivery & measurement

    The campaign goes live. The compliance gate checks every send. You see participants, landing page logins, micro and macro goals per channel and brand.

    Journey Builder in detail →

    Campaigns · Overview
    CampaignListBrandsStatusParticipantsPriorityOwner
    Wiederanlage Leben 2026 Life portfolio All (3) Active 2.480 2 J. Neumann
    Tariff end Q4 Contracts Q4 2 brands Active 1.860 3 S. Albers
    Current account welcome series New customers 1 brand Approval 640 4 C. Reuter
    Autumn newsletter Newsletter subscribers All (3) Draft 12.480 5 M. Yilmaz
    Motor claim service Claims notifications All (3) Active 318 1 T. Krüger
    Example · demo dataCampaign overview: list, brands, status, participants, priority and owner per campaign. “Current account welcome series” is awaiting approval, “Motor claim service” runs as an ongoing campaign (∞).
    Insights · Life reinvestment 2026 Demo data

    Campaign Wiederanlage Leben 2026

    • Brand All
    • Channel All
    • Period 30 days
    • Participants2,480
    • LP logins1,116
    • Micro goals744
    • Macro goal “Appointment”298

    Funnel · micro → macro

    1. Participants
    2. LP logins
    3. Micro-goals
    4. Appointment arranged

    Channel comparison · LP logins

    All
    Email Letter

    Exit reasons

    Exits1,120
    • converted38%
    • completed · payout22%
    • completed · no response27%
    • left segment13%
    Example · demo dataInsights dashboard: funnel from micro to macro goals, channel comparison email vs. letter, exit reasons and the AI explanation ‘Explain your Campaign’. Demo data.
Import · AI mapping AI suggestions
bestand_export_2026-09.csv 84,312 rows
Source columnAttributeAI confidence
VERTR_ENDE vertrag_ende 97 %
KD_BERATER berater 91 %
EMAIL_OK consent_email 88 %
KZ_SONDER unclear – please assign

Upsert via customer number · does not delete any contacts

Example · demo dataImport with AI mapping: the AI suggests an attribute with a confidence score for each source column; you assign unclear columns yourself. An import does not delete any contacts.
Journey · Wiederanlage Leben 2026 Regionalbank Musterstadt eG
  1. Entry Segment: expiry ≤ 90 days
  2. Gate Consent per channel
    • Letter Announcement
  4. Wait for event LP login · 7 days
  5. No
    • Reminder Reminder letter
  6. Exit completed
  7. Yes
    1. Landing page Personal overview
    2. Condition Lead score ≥ 60
    3. Task Notify adviser C. Reuter
    4. Goal · macro Appointment arranged

Properties

Entry: segment

Condition
vertrag_ende ≤ today + 90 days
Segment
dynamic
Example · demo dataExample journey ‘Wiederanlage Leben 2026’ in the Journey Builder: entry via a segment, consent check, channel switch between email and letter, waiting for the login, reminder, handover to the adviser and the goal ‘Appointment booked’. Fictitious example data.
Content · Reinvestment · Introduction field

AI suggestion · not yet accepted

Your fixed-term deposit expires on 31 March – secure your terms now before it’s too late. You will find three options in your personal overview.

Compliance & tone check

  • no return promises
  • Mandatory notice present

Tone: “too urgent”

Suggestion: “secure your terms now … before it’s too late” → “You can decide at your own pace how to proceed.”

Created by: J. Neumann · Approval by: C. Reuter (four-eyes)

Approved · C. Reuter · Four-eyes

logged · 25 September 2026 10:42

Example · demo dataAI suggestion in the content editor: the compliance check flags an overly urgent tone; approval follows the four-eyes principle and is logged. Fictitious example data.
Campaigns · Overview
CampaignListBrandsStatusParticipantsPriorityOwner
Wiederanlage Leben 2026 Life portfolio All (3) Active 2.480 2 J. Neumann
Tariff end Q4 Contracts Q4 2 brands Active 1.860 3 S. Albers
Current account welcome series New customers 1 brand Approval 640 4 C. Reuter
Autumn newsletter Newsletter subscribers All (3) Draft 12.480 5 M. Yilmaz
Motor claim service Claims notifications All (3) Active 318 1 T. Krüger
Example · demo dataCampaign overview: list, brands, status, participants, priority and owner per campaign. “Current account welcome series” is awaiting approval, “Motor claim service” runs as an ongoing campaign (∞).
Insights · Life reinvestment 2026 Demo data

Campaign Wiederanlage Leben 2026

  • Brand All
  • Channel All
  • Period 30 days
  • Participants2,480
  • LP logins1,116
  • Micro goals744
  • Macro goal “Appointment”298

Funnel · micro → macro

  1. Participants
  2. LP logins
  3. Micro-goals
  4. Appointment arranged

Channel comparison · LP logins

All
Email Letter

Exit reasons

Exits1,120
  • converted38%
  • completed · payout22%
  • completed · no response27%
  • left segment13%
Example · demo dataInsights dashboard: funnel from micro to macro goals, channel comparison email vs. letter, exit reasons and the AI explanation ‘Explain your Campaign’. Demo data.

What the PBM Campaign Platform is not

Not an ad server. The platform does not place or bid for ads. Paid media is connected only for matching target groups with advertising consent.

Not a CRM replacement. Your CRM remains the leading system. Advisers do, however, receive a customer card with journey status and activities.

Frequently asked questions about the platform

Which channels does the PBM Campaign Platform support?

Email, letter, insert, SMS, personalised landing page, customer portal and app – all in the same journey. The letter is generated as a PDF per contact and handed over via SFTP to your print service provider.

Where does the PBM Campaign Platform run?

Every company receives its own isolated installation (single-tenant). The standard is hosting in Germany; on request AWS, Microsoft Azure or another environment.

Do we have to use the AI functions?

No. The AI layer is optional and can be switched off. The platform works with a rule-based engine; AI only provides suggestions, which people review and approve.

How do we connect our existing systems?

Via a versioned REST API with service accounts or by file import. Events from core systems, such as a contract expiry, can start a journey directly. Email and SMS providers can be chosen freely.

Next step

See the five steps with your use case.

Bring a real use case with you. In 45 minutes, you will experience the PBM Campaign Platform live – with high-performance customer journeys in action, tailored to your use case. Afterwards, you will know whether the PBM Campaign Platform is right for you.

Book a demo

Hosting in Germany · single-tenant · consent check before every send