Skip to main content
A campaign binds reusable content, delivery settings, routing, and browser session options into one controlled assessment.

​
Before creating a campaign

Prepare the target list, landing page, and—unless the campaign is standalone—the email template and SMTP profile. Plugins and modules are optional.
Create and review reusable resources before opening the wizard. This keeps the final review focused on scope, timing, recipients, and runtime behavior.

​
Campaign wizard

Setup

Set the name, description, campaign type, and production hostname.

Content

Select the SMTP profile, email template, landing page, plugins, and modules.

Launch

Select the target list, target URL, schedule, tracking parameter, protocol, and streaming options.

Review

Confirm authorization, scope, resources, timing, routing, and data handling before the campaign can start.
New Campaign wizard on the Setup step, with the four-step progress indicator
The final step summarizes every choice made in the previous three before the campaign can be created:
Campaign wizard Review step summarizing campaign, content, attack vectors, and launch settings

​
Campaign creation demo

This recording shows the campaign-creation workflow with synthetic data in a controlled environment. It is provided for review of the operator experience, not as a substitute for written authorization and scope review.
Target URLs must be complete HTTP or HTTPS URLs. Production campaigns also require a hostname without a scheme, port, path, query, or fragment.

​
Campaign types

Complete campaigns use the selected email and SMTP delivery resources. The dashboard always creates them with a scheduled delivery window.Both timezone-aware start and end times are required. The start must be in the future and the end must follow the start. P-BitM activates the campaign at the start and distributes recipient email delivery across that window. The end time closes the planned email-delivery window; it does not stop or complete the campaign.

​
Production hostname reservations

In production, an active or paused campaign exclusively owns its public hostname. A scheduled Complete campaign reserves that hostname for every UTC calendar day covered by its start and end times, so two scheduled windows on the same UTC day conflict even when their hours do not overlap. The same hostname can be reused for delivery windows on different UTC days. After activation, the campaign continues to own the hostname while it remains active or paused. If another active or paused campaign still owns the hostname when a scheduled campaign becomes due, activation remains pending and is retried after the hostname becomes available. Stopping or completing the owner releases it.

​
Runtime controls

Campaign states include draft, scheduled, active, paused, completed, and error. A Complete campaign can be stopped manually while it is still scheduled or after it becomes active. Once active, both Complete and Standalone campaigns can be paused and resumed. Pause suspends the campaign runtime; resume returns that runtime to active. Stop is terminal for either campaign type: it removes the runtime and changes the campaign state to completed.
A Complete campaign remains active after its email-delivery window ends. It can continue for days, weeks, or months and is completed only when an operator stops it. P-BitM does not infer campaign completion from the final scheduled email time.
Use the dashboard for routine lifecycle management. CLI equivalents are listed in the CLI reference.
Last modified on August 28, 2026