We have FINALLY released the long-awaited custom events feature.
You can now find information on these in the tracking codes area, set aliases under system settings, and can see our help article here.
This is an initial release so not all aspects are finished, but you can now:
- Send 1-10 custom events back to FunnelFlux via postback URL and JavaScript
- Send optional revenue with those events
- Set aliases for use in the reporting UI
- In all reporting pages, you can see custom event count, event revenue, completion rates per visit, revenue per custom event, and cost per custom event
We have some upcoming further changes to complete custom event implementation:
- Ability to set postbacks for each one in traffic source conversion tracking (an obvious feature that we should release in the coming days)
- Ability to trigger custom events in the funnel builder as users perform an action
- Ability to upload custom events via API much like conversions
- Addition of custom events to the raw events reporting
- Adding total revenue columns to reporting to sum all revenue sources, and updating ROI/P&L metrics to use these as well (right now, "revenue" is actually conversionrevenue only).
Please note custom events have the following limitations:
- Custom events can only happen once per user. Our current database design prevents duplicates of custom events. We intend to change this in the future, as we feel there's many scenarios where you want to send custom events multiple times.
- Custom events cannot pass unique transaction ID data
- You can only trigger custom events using their number when using postbacks/JS. We won't allow triggering by alias (e.g. event_name=lead), because if you ever changed aliases in our UI you could break existing events or make them switch to new event columns in our database, fragmenting your data.
Other important changes
In order to make custom events more convenient, we also made a significant change to our hit design.
Previously, only hits (views) to offers could convert. We have now made it possible for all page view events to convert, i.e. lander views as well.
Other fixes/updates
- We added a "disable VID append" feature to data passing. This is for rare cases where VID may break a downstream system and you want to disable our auto-appending of it on redirect
- We have added some initial logics to prevent excessive sessions sizes, which is happening to some odd traffic originating from TikTok/Pangle (we think somehow they are caching cookies across users and causing the same VIDs to get used when they should not)
- We have updated various API schema to use new restrictToMetrics associated with custom events
- Improved some issues with reporting which were causing updated asset changes to not reflect in the UI (e.g. you delete an asset, it reappears).