Custom events record user actions — button taps, completed flows, purchases. Pulsate uses them for two things:
- Event-triggered campaigns — e.g. show a loan campaign to users who fired
didPressLoanButton. - Analytics — understand what customers actually do in your app.
Sending an event
val pulsateManager = PulsateFactory.getInstance()
pulsateManager.createEvent("didPressLoanButton")
Once an event has been received at least once, it becomes selectable in the CMS campaign targeting section.
Sending several events at once
pulsateManager.createEvents(listOf("openedStatement", "downloadedStatement"))
Naming tips
- Use stable, code-reviewed names (
didPressLoanButton, not free-form strings) — every distinct string becomes a separate event in the CMS. - Event names are limited to a reasonable length; keep them short and descriptive.