You can receive user events on your server to manage tasks like registration, email follow-ups, and more.
Your server must respond with a 2xx status code within 10 seconds of receiving the request. If your server does not respond within this time, the event will be considered undelivered.
OctoFlow will attempt to resend undelivered events up to 30 times. Each retry is delayed using an exponential backoff strategy, calculated with the following formula:
delay(n) = n^4 + 15 + rand(0, 29) * (n + 1)
delay is the retry delay in seconds.n is the retry attempt number.rand(0, 29) adds a random delay between 0 and 29 seconds.You can find all event schemas in our API reference.
| Event | Schema | Description |
|---|---|---|
onboarding.started |
Schema | Triggered when a user starts the onboarding process and the first page loads, creating a new session. |
onboarding.completed |
Schema | Triggered when a user reaches the final screen in the onboarding process. |
profile.updated |
Schema | Triggered when a user provides their email. |
Note:
To trigger the
onboarding.completedevent, the final screen must have an ID that starts withfinal. Only screens with an ID beginning withfinalwill be recognized as the final screen in the onboarding process.