For the rudderstack integration, when are events sent to it? Other integrations have settings for when we want events sent for each step or form completion.
THe UI and docs aren’t clear on this. Ideally there should be a setting that gives these options:
Ah, got it. I totally missed this line in that “How to use”:
When each step of your form is loaded and submitted, a RudderStack event will be tracked.
It would be nice to get control of whether every step should be sent or just completion. Many times we just want completion for things like rudderstack. Otherwise we need to filter downstream and that’s just extra work that I think makes more sense as config option in feathery.
More importantly, Rudderstack bills based on event volume per month so always sending events for step submissions when we don’t need them ends up driving up costs up due to event volume.
Eg. Feathery firm with 5 questions is 6 events per user to rudderstack (5 step submissions and 1 form completion).
I had to completely disable rudderstack integration – way too many events were being sent per survey, we’d hammer our monthly event quota if we ultimately launched this because we’d be getting 6-7x the # of events we need to get in this case from feathery. Hoping there can be configuration for this.
Additionally, there is a “page” tracking event being sent when there’s no configuration to control this (there should be like the other events to Rudderstack)
We are still seeing page events sent to rudderstack, which are the pageview events.
This causes the same issue as my comments with the other events: it blows up the rudderstack event volume.
At minimum, this should be controllable in the Rudderstack integration settings.
However, unless Im missing something, pageviews aren’t important for feathery given you have the “step load” event which I believe is exactly equivalent. So suggest pageview events are disabled.