CAMPAIGNS and scores
Run tests with purpose.
Track outcomes at scale.
Configure how your load tests are organized, scored, and reported directly from Gatling Enterprise Edition. Group tests around business goals. Give leadership the visibility they need. Without touching your simulation code.
Organize load tests around business goals
A Campaign is a container. It groups your load tests around a single business objective (a release, a Black Friday, an audit) and tracks their results over time.
Until now, your tests lived in isolation. You knew what ran. You didn't know why, or whether it was working.
Campaigns add the layer that was missing: structure, purpose, and a score that tells you if you're ready. Your scenario logic stays exactly as written. Only the context changes.
Every campaign records exactly what health looks like over time
Each run updates the campaign score automatically. Each day, the platform snapshots the full campaign state (scores, linked tests, SLO results) so you can follow progress and catch regressions before they become incidents.
Get a score that means something
Methodology: Are your tests set up correctly? Do they have names, defined load types, and objectives?
Objectives: Stack up to 50 injection steps per scenario: ramps, constants, spikes, at-once bursts. Build any traffic shape your production actually produces.
Confidence: Are your tests passing? Did they run cleanly, and did your SLOs hold?
.png)
OUTCOMES
What changes when performance testing has a purpose
The feature your organization has been missing at every level
Your work now has a throughline. Tests you've been running in isolation connect to a goal, contribute to a score, and build toward something. The rigor you've always applied is finally visible to the rest of the organization.
Heading
Stop running one-off tests before every release and hoping for the best. Campaigns give you a continuous, structured view of system health, with the history to know whether what you're seeing is normal, improving, or a warning sign.
Heading
You've been asking for a way to show what performance testing is actually achieving. Campaign scores give you that, a defensible, data-driven answer to "are we ready?" that doesn't require anyone to read a test report.
Heading
Ready to create
your first campaign?
Your Gatling Enterprise Edition account is all you need.
FAQ
Frequently Asked Questions about Campaigns and scores
No. Campaigns sit above your existing tests and runs. Nothing about how your simulations are written needs to change.
It's a composite of three dimensions: Methodology (are tests configured with rigor?), Objectives (are systems meeting their SLOs?), and Confidence (is that performance consistent over time?). Each dimension scores out of 100. The campaign score is the average of the three.
No. Each test belongs to one Campaign at a time, this keeps ownership and scoring clean.
Anyone on the team can view their team's campaigns. Creation, editing, and deletion follow the same permissions as tests.
Your all-in-one load testing platform
Design complex tests, manage global infrastructure, and turn results into action on one powerful platform.
Need technical references and tutorials?
Minimal features, for local use only
