You can receive user events on your server, so that you can manually handle registration, email follow-ups, etc.

Receive policy

Maximum response time: 10 sec
Maximum retry count: 30
Retry timeout: exponential backoff

Your server must respond with 2xx status within 10 seconds of request. If your server does not respond, we consider event not being received.

FunnelFox will repeatedly send unreceived events up to 30 times. Every next retry is delayed exponentially using the following formula:

delay (n) = n^{4} + 15 + rand (0, 29) \times (n + 1)

delay is retry delay in seconds
n is retry attempt
rand(0, 29) is a random amount of seconds from 0 to 29

Events

All events schemas can be found in our API reference.

Event	Schema	Description
`onboarding.started`	link	Fires when user has opened your onboarding and page has loaded, new session is created.
`onboarding.completed`	link	Fires when user has reached a final screen in onboarding.
`profile.updated`	link	Fires when user has provided their email
`purchase.completed`	link	Fires, when user has completed a purchase or when recurrent/upsell purchase happens

🚧
Assign screen with ID final*
We currently consider a “final screen” as a screen with ID that starts the final custom ID. Only these screens will hook onboarding.completed events.

Webhook Events

Receive policy

Events

🚧
Assign screen with ID `final*`

Receive policy

Events

🚧Assign screen with ID final*

🚧
Assign screen with ID `final*`