A campaign is the unit Personyze runs: an audience, some content, a place to show it, and a goal to judge it by.
Every channel — your own site, email, push, a mobile app — is the same campaign wearing a different face.
Building one
- Targeting and personalization — The wizard, step by step.
- A/B testing — Two versions, a split, and a verdict you can trust.
- Automation — Rules that watch your campaigns and act — pause, alert, promote a winner.
- Landing pages — Host a whole page at its own URL, on Personyze or your own domain.
- Scenario programs — pick an outcome and Personyze creates the several campaigns it takes, already wired to each other.
- Tags — labels that make two hundred campaigns readable, and that scope dashboards.
Channels
- Web browser — campaigns on your own site.
- Email — recommendations and personalized blocks inside email, sent by you or by Personyze.
- Web push — collecting subscribers and sending notifications.
- Mobile apps — the same targeting inside an iOS or Android app.
What a campaign actually shows — the action types, the editors, the template gallery, and how often a visitor sees it — is Content & Design.
Before and after it goes live
- QA & Launch — preview, audience forecast, safe publishing, and the four things to check when a campaign is not showing.
- Dashboards — Build a view scoped to this campaign, and have it emailed to you weekly.
A campaign left in testing reaches nobody but you. Testing & QA covers the
difference between preview, staging and published — it is the single most common reason a campaign
“does not work”.
difference between preview, staging and published — it is the single most common reason a campaign
“does not work”.