Events Reference
Jule fires custom events to Iterable for campaign triggering. This page documents each event source and its payload.
Iterable events
These fire server-side from Jule's backend via the Iterable events/trackAPI. They appear in the user's Iterable activity timeline and can be used as Journey entry triggers.
| Event source | When | dataFields |
|---|---|---|
| Track Custom Event action — your configured name (default form_submission) | Form submitted, with the Track Custom Event action enabled in the editor's Iterable tab | project (project name), fields (the field values you mapped in the Track Event mappings) |
| Per-page event fires — custom names set per page | A page configured to fire Iterable events is submitted. Skipped when the submission has no email or user ID. | The properties you configure on the page |
| Coupon lifecycle — couponAssigned, couponRedeemed, couponExpired (names configurable per coupon) | A coupon is assigned, redeemed, or expires, when coupon Iterable sync is enabled | coupon_code, coupon_status, discount and expiry details (prefix configurable) |
Events tied to a submission require an identity — an email address (or user ID) captured by the form. Submissions without one are recorded in Jule analytics but not sent to Iterable.
Dashboard analytics
Widget interactions — impressions, opens, closes, page views, and submissions — are tracked separately in Jule's own analytics and power the charts in your dashboard's Analytics section. They are not sent to Iterable.