Campaign Nodes
Event Trigger
Start a campaign when Leadpush receives a matching event for a contact.
The Event Trigger starts a campaign from behavioral or integration events, such as checkout_started, trial_created, or subscription_cancelled.
When to use it
Use this trigger when campaign entry depends on something a person did, rather than a static contact profile or segment membership.
Common examples:
- onboarding after a signup event
- recovery after an abandoned checkout event
- follow-up after a product or billing event
- lifecycle messages after an event sent through an integration
Settings
- Event name: the event that should enter the contact into the campaign.
- Frequency: controls whether the same contact can enter once, on every matching event, or after a fixed interval.
- Event payload: event-triggered simulations can provide a sample JSON payload so event fields are available while testing.
Simulation and execution behavior
Simulations run against a sample contact and can include a mock event payload. During real executions, the payload comes from the event that entered the contact into the campaign.
After the campaign is started, the trigger itself cannot be changed. Review the event name and re-entry settings before publishing.
Best practices
- Use stable event names that match your integration naming conventions.
- Test simulations with a realistic payload when later nodes use event data.
- Keep re-entry rules conservative unless repeated events should create repeated campaign runs.