Segment rules
Build audiences from governed customer attributes and linked activity.
Campaigns
For an account with a verified worker and delivery adapter, OfferAgent CampaignEngine builds a controlled campaign from account-scoped segments, explicit exclusions and a frozen audience snapshot. The team previews recipients, consent and frequency limits before approval, then schedules delivery through CommunicationHub. Every member keeps an individual status so results reflect actual eligibility, delivery and response.
Exported lists become stale and make consent, exclusions and duplicate protection difficult to verify.
Choose a measurable purpose and account-scoped segment.
Inspect included customers and every exclusion reason.
Freeze recipients and reviewed content before launch.
Send through CommunicationHub and follow member-level outcomes.
The campaign workspace exposes eligibility, approval and delivery at member level.
Prerequisite: Requires Campaign access, customer consent data and a configured delivery channel.
Sign-in and the correct plan are required. This link is not a public demo.
Build audiences from governed customer attributes and linked activity.
Show why a customer is suppressed before launch.
Preserve who was approved even when customer data later changes.
Separate eligible, suppressed, queued, delivered and failed states.
OfferAgent states what the capability does and what still requires configuration, permission or a human decision.
Only customers who match the segment and pass consent, suppression and frequency checks are eligible.
Yes. Preview lists excluded members and their reason before approval.
Yes, within the guarded lifecycle exposed by CampaignEngine.
No. A campaign starts from an approved audience; an automation starts from individual events.