1. Define the target audience
Campaigns can be prepared based on existing customer data, subscription data, booked products, options or other criteria.
For targeted customer communication and subscription actions
Create targeted campaigns based on customer, product and subscription data. tebio supports campaigns for communication, customer activation, option bookings, upgrades, retention and other subscription-related downstream processes — connected with the Business Portal, billing, Hosted Pages, API and Webhooks.
Instead of exporting customer groups manually, campaigns can build directly on tebio data. Target audiences, actions, scheduling, execution and results stay traceable in the context of your subscription processes.




Many campaigns start with exported lists, manual filters and separate e-mail tools. As a result, it is often unclear which customers are actually affected, which subscription is active, which product was booked and which follow-up action should happen after the communication.
With tebio, campaigns can be prepared, checked, scheduled and executed based on existing customer, product and subscription data. Campaigns can trigger messages or initiate subscription-related actions, for example booking an option or pointing a customer to a specific offer.
This keeps campaigns part of the platform logic. Target audience, action, execution status, statistics and downstream processes can be visible in the Business Portal and, if needed, connected with external systems via API and Webhooks.
Campaigns can be prepared based on existing customer data, subscription data, booked products, options or other criteria.
Customers can be reached via configured communication channels, for example by e-mail or letter, provided these channels have been set up.
Campaigns can be used to point customers to relevant options, add-ons, upgrades or additional services.
Depending on the setup, a campaign can not only inform but also initiate a subscription-related action, for example booking an option.
Campaigns can be prepared and scheduled for a specific start time, so that actions do not have to be triggered manually right away.
A limit on executions per hour lets you control how quickly campaign actions are processed.
Before execution, a campaign can be checked to better assess the target audience, configuration and potential risks.
Status, execution and statistics help teams manage and evaluate campaigns in a traceable way.
API and Webhooks can be used to connect campaign-related events or downstream processes with external systems.
A campaign process should guide teams safely from the idea to execution. To do so, the page should show a clear builder approach: goal, target audience, action, scheduling, check and execution.
The campaign's name, description, goal and channel are defined so that the campaign remains traceable later on.
The target audience is defined based on existing customer, subscription, product or option data.
The campaign can trigger a message or, depending on the setup, start a subscription-related action.
A scheduled start time defines when the campaign is to be executed.
A limit per hour can help execute campaigns in a controlled way.
Before launch, a campaign check can help assess the configuration, target audience and potential risks.
Status, progress and statistics support operational control during and after execution.
Campaigns can address customer groups in a targeted way by using existing data on customers, subscriptions, products, options or other attributes. This way, target audiences are not created from disconnected export lists but from the operational platform context.
Campaigns can be targeted more precisely at customers who meet certain product, option or subscription criteria.
Teams do not have to compile target audiences manually from several systems for every campaign.
Campaigns stay connected with customer, subscription and product data.
Before launch, you can check whether the target audience and campaign configuration make sense and can be executed.
A campaign can perform different actions. Depending on the setup, customers can be informed or subscription-related processes can be initiated.
Campaigns can trigger e-mail messages, provided the corresponding communication channel and the appropriate template have been set up.
Campaigns can trigger letter delivery, provided it has been set up and is intended for the respective process.
Depending on the configuration, a campaign can book a subscription option and thereby initiate an operational subscription process.
Campaigns can be used to prepare customers in a targeted way for options, upgrades or other downstream processes.
Further actions can be added depending on product development and configuration, for example token-based landing pages, customer data updates or subscription-related attribute changes.
The actions actually available depend on the release version, configuration, permissions and the communication channels that have been set up.
Campaigns should not be launched without control. tebio can support campaigns with a scheduled start time, throttling, status and execution control so that teams can control campaigns operationally.
Prepare campaign as a draft
Schedule start time Limit executions per hour
Start campaign
Pause campaign Resume campaign
Cancel campaign Finalize execution
Track status and progress
Before execution, a campaign check can help assess the target audience, configuration and potential operational risks. This helps teams see more clearly whether a campaign is ready to launch or should be adjusted first.
A campaign check supports operational quality assurance, but does not replace a professional review by the responsible teams.
The campaign appears ready to launch.
There are notes that should be checked before launch.
There are relevant anomalies that suggest an adjustment.
The campaign should be corrected before execution.
Campaigns must remain traceable during and after execution. Status, execution details and statistics help teams review progress, successful actions, errors and open items.
tebio campaigns can help companies address customers in a targeted way based on their subscription, product or usage relationship and trigger suitable downstream processes.
Point customers with specific plans, add-ons or usage profiles to upgrades, options or product changes.
Inform subscribers of specific print, e-paper, digital or bundle subscriptions about offers, options or Self-Care processes.
Address customers with specific plans, options or allowances about add-on packages, plan changes or retention offers.
Inform organizations, practices or user groups about license models, feature packages or renewal processes.
Address customers with specific device subscriptions, service packages or usage models about additional services or contract changes.
Inform members about training packages, add-on options, contract renewals or Self-Care processes.
Include partner-related customer groups or subscriptions in sales, offer or commission processes in a targeted way.
The tebio documentation should show how campaigns are prepared, target audiences defined, actions selected, scheduling and throttling configured, campaigns checked and executions monitored.
Campaigns in tebio are targeted processes based on customer, product and subscription data. They can be used to address customer groups, trigger messages or start subscription-related follow-up actions.
No. tebio is not a pure newsletter or marketing automation platform. Campaigns in tebio are connected with subscription management, customers, products, options, billing, the Business Portal, API and Webhooks.
Target audiences can be built from existing tebio data, for example customer data, subscription status, booked products, booked options or other criteria. The filters actually available depend on the setup and configuration.
Depending on the setup, a campaign can trigger messages, for example e-mail or letter. In addition, subscription-related actions may be possible, for example booking an option. The exact scope depends on configuration, release version and permissions.
Yes. Campaigns can be prepared with a scheduled start time so that execution does not have to happen manually right away.
Yes. Throttling per hour can help execute campaigns in a controlled way and limit the operational load.
Yes. A campaign check can help assess the target audience, configuration and potential anomalies before launch. It supports operational quality assurance, but does not replace a professional review by the responsible teams.
Yes. Depending on status and execution, campaigns can be paused, resumed or canceled.
Yes. Campaigns can provide status, progress and execution statistics so that teams can trace successful, failed or pending actions.
Yes. API and Webhooks can be used to connect campaign-related events or downstream processes with external systems.
Depending on the setup, a campaign can trigger a subscription-related action such as booking an option. Further processes such as confirmation, billing or Webhooks may then become relevant.
No. Campaigns are executed based on defined target audiences. Which customers are included depends on the selected criteria, permissions and campaign configuration.

Start for free with tebio or talk to us about how you can connect target audiences, communication, subscription actions, campaign control and integrations in one platform.