Getting Started
Changelog
08/05/2026
- Conditions now use a route ID and priority key for determining what routes go where, and the route processing priority. This separates ordering from connection logic. Use the new route IDs and priorities. For IDs, use
route_{id}and generate an ID with our normal ID generator for consistency. Route IDs can also be names of your choosing. - Consolidated category APIs to one canonical /category API rather than endpoints nested under other assets
- Many other changes not previously added to this changelog
19/06/2024
- [Breaking Changes] - The raw events API has been updated to a new approach, allowing more direct data based on our DB columns directly.
- All metrics are now selected through the
restrictToMetricsattribute - A maximum of 15 columns of data can be returned per request
- You can now directly access tracking field data with this approach
- Maximum paging length has been increased from 1,000 -> 10,000
- Note that because this accesses raw data, it currently does not resolve names, just IDs. We will extend this later to add mappings for asset IDs
11/06/2024
- Added
conversionTimeattributes to conversion uploads - Added
disablePostbackattributes to conversion uploads - Updated hit reporting spec, pending changes in the UI
03/04/2024
- Added
restrictToMetricsandreturnUniqueVisitorsinformation to reporting API.
15/07/2023
- Updated API domain to
api.funnelflux.pro
03/09/2022
- Added ID generation article
22/06/2022
- Initial release of the v1 API docs, with limitations and some omissions
Last modified on