Other
Changelog
16/11/2026
- Added customer API keys to the Auth API under a new
API Keystag:POST /api-keys(apiKeyCreate) creates a key and returns its plaintextsecretonce (APIKeyIssued,Cache-Control: no-store),GET /api-keys(apiKeyList) lists the account's active keys oldest first (APIKeyList), andDELETE /api-keys/{id}(apiKeyRevoke) revokes one permanently. FunnelFlux API keys carry theffk_prefix and are sent asAuthorization: Bearer <secret>; only the SHA-256 hash is stored, so every read after creation carriesmaskedinstead of the secret. See the Authentication guide. - [Breaking-ish] API key management accepts a web-app session credential only. An API key or a legacy Auth0 token is refused with
403 session_required(newSessionRequiredresponse) before anything is read or written; a session whose Clerk user carries no FunnelFlux account identifier answersaccount_not_linkedinstead.POST /api-keysalso refuses a blank or over-255-character name with400 invalid_name, the 51st active key with409 api_key_limit_reached, and answers503withissuing_login_unavailable,issuing_login_lookup_failedorapi_key_unavailable(APIKeyError).DELETE /api-keys/{id}answers404 not_foundfor an unknown or already revoked key and409 ambiguous_api_keywhen the id matches more than one row. POST /auth/reset_passwordoperation id is nowauthResetPassword(wasauthResetPasswordRetired). Behaviour is unchanged: Auth0 provider only,410 endpoint_retiredunder Clerk,503 account_changes_frozenwhile the sign-in provider cutover freeze is on.- [Breaking-ish]
POST /trafficsource/data-mapping/clear/(clearTrafficSourceDataMapping) accepts an omitted or emptyfieldagain: that clears every manual name of the one traffic source acrosscampaign,field1andfield2. This restores the clear-all behavior the 13/11/2026 entry said was removed; sendfieldto clear a single field.DataMappingClearRequest.fieldis optional again, and its enum now also allows''. - [Breaking-ish]
DataMappingClearRequestnow setsadditionalProperties: false: the body may carry onlyidTrafficSourceandfield, each spelled exactly so and at most once. Unknown or differently-cased keys, and anullfield, are refused with400 invalid_requestand nothing is cleared — omitfieldto clear all fields. - Added
PUT /funnel/move/(moveFunnelsToFunnelGroup) to move funnels into a funnel group.idFunnelGroupis the canonical target;idCampaignremains a temporary alias and is ignored whenidFunnelGroupis set; with neither, the request answers400"Missing idFunnelGroup".PUT /campaign/funnel/move/(moveFunnels) is now documented as deprecated in favour of the new path and accepts the same input. - Outbound webhook payloads now carry
schema_version"1.1"(was"1.0"). Version1.1is the version that always includes the top-levelreferring_page_idandreferring_page_namefields; no other field changes. The webhook JSON Schema accepts"1.0"and"1.1"and requires the two fields only for"1.1". If your receiver checksschema_versionfor an exact"1.0", accept"1.1"as well. Middleware payloads keep their own version. - The webhook hit object no longer documents
time_on_page; webhooks never sent it. ConversionsUpdateParams.postbackCallsno longer declaresdefault: none. OmittingpostbackCallsdoes not stop delivery on conversion or custom-event uploads; onlynoneordisablePostbacks: truedoes.onlyOnceandallbehave the same as omitting it.
14/11/2026
- Integration ad-account and conversion-goal reads now document provider authentication failures in
IntegrationUnauthorized: the401response can contain a provider error message withouterror_description. Gateway authentication failures retain the existingUnauthorizedbodies.
13/11/2026
- [Breaking]
POST /trafficsource/data-mapping/clear/now requiresfield(campaign,field1, orfield2) and clears exactly that field. Omitting or sending an emptyfieldreturns400 invalid_request; the former clear-all-fields behavior is removed. - Data-mapping upload and clear operations moved from the
Traffic Sourcestag to the newData Mappingtag in the Assets API. - Added the Data Mapping guide, covering field declarations, uploads, clears, validation, and report name resolution.
12/11/2026
- Requests authenticated with a customer API key or a legacy Auth0 API token now share one per-account, per-minute cap (default 60). When it is exhausted, the API gateway answers HTTP 429 with a
RateLimitErrorbody (codeAPI_RATE_LIMITED) and aRetry-Afterheader, and the operation is not performed. Web-app session traffic is not limited. Every operation in the Assets, Reporting, Billing and Auth specs now documents the429response; batch reads (byIds, list endpoints) instead of looping single-item reads. - Auth API operations now document a shared
401body (access_token_required,no_access, orinvalid_tokenfor an invalid or expired token or API key) and a403account_not_linkedresponse for a valid token or API key whose Clerk user has no FunnelFlux account. No account is resolved or created in that case. POST /auth/register(authRegister) is now documented. It works under the Auth0 provider only and can answer409registration_in_progressor503account_changes_frozen/registration_unavailable, withRetry-After. Under the Clerk provider it answers410endpoint_retiredwithreplacement: checkout; new accounts are created only through checkout.- [Breaking] Under the Clerk sign-in provider, password login (
/auth/login), the MFA OTP verification endpoint (/auth/mfa/otp), and the MFA status, enrollment and authentication-method delete endpoints answer410withEndpointRetiredError(errorendpoint_retired,replacementsign_in) andCache-Control: no-store, before any credential or body is read. They keep working under the Auth0 provider. - Added
PUT /trafficsource/data-mapping/upload/(uploadTrafficSourceDataMapping, tagTraffic Sources): merges ID-to-name rows into a traffic source's manual names forcampaign,field1orfield2. RequestDataMappingUploadRequest; responseDataMappingUploadResponsewithaddedandupdatedcounts. At most 10,000 rows and 4 MiB per request. The upload is all-or-nothing: if any row is refused, nothing is stored androwErrorslists every refused row with itsDataMappingRowError.reason. Errors useDataMappingErrorcodes (invalid_request,no_rows,too_many_rows,invalid_rows,not_found,dictionary_sync_enabled,field_not_declared,body_too_large). - Added
POST /trafficsource/data-mapping/clear/(clearTrafficSourceDataMapping, tagTraffic Sources): removes a traffic source's manual names for one field, or all three fields whenfieldis omitted or empty, and returns theremovedcount. Names synced from an integration are never touched, and the field does not need to be declared. TrafficSourcehas a newdataMappingobject (TrafficSourceDataMapping:campaign,field1Slot,field2Slot,suffixIds) that declares which fields carry manual name mappings. Declaring any field whileintegration.features.dictionarySync.enabledis on is rejected with 400dictionary_sync_conflict.- [Breaking-ish]
TrafficSource.conversionTrackingMode(classicorintegrations) is now a top-level field, and the mode is no longer read frommeta. When the field is omitted on save, the stored mode isclassic. Conversions route through integrations only when the mode isintegrations, a connection is set, andintegration.features.capi.enabledis true. Saving one setting never changes the other. A save withintegrationsremoves the stored classic postbacks andconversionTrackingSettings, other values are rejected with 400, and unlinking the integration setsclassic. Pagenow has a read-onlyownerfield, filled by loading endpoints and ignored on save.- [Breaking-ish]
PUT /reporting/update/conversions/now documents re-upload rules for the same hit and transaction ID. A re-upload within 5 minutes is ignored as a duplicate. Between 5 minutes and 3 hours, a revenue change replaces the revenue without calling postback URLs or webhooks again unlessforcePostbacksis true. After 3 hours, the upload replaces the conversion and is delivered again. Negative revenue deletes the conversion at any time.disablePostbacks: trueorpostbackCalls: nonestops all outbound delivery and overridesforcePostbacks.postbackCallsvaluesonlyOnceandallare accepted but have no effect, soonlyOnceno longer prevents a re-upload from being delivered again. PUT /reporting/update/customevents/now documents that custom events are not deduplicated. Each accepted upload goes to postback URLs, webhooks, Meta and TikTok again, while Google Ads and Microsoft Ads receive each hit and event number only once. SetdisablePostbacks: trueorpostbackCalls: noneto record events without sending them. Negative revenue is rejected.- [Breaking-ish]
PUT /reporting/update/cost/,POST /reporting/update/reset/andDELETE /reporting/update/reset/now require nonzerotimeStartandtimeEnd, withtimeEndstrictly aftertimeStart,timeStarton or after2020-01-01T00:00:00Z, andtimeEndno later than 12 calendar months aftertimeStart. Other requests are rejected with 400 before anything is counted, changed or deleted. For reset requests, a missing restriction is reported before time-window errors. - Cost update and reset requests now reject a
restrictToTrackingFieldskey whose value list is empty or contains only blank values (400). Omit the key to leave tracking fields unrestricted. DrilldownReportParams.restrictToMetrics: when it andcalculatedMetricsare both empty, the default metric set excludesCustomEvent1-10,AverageTimeOnPageandBounceRate. Unsupported names are ignored, and a request naming only unsupported metrics returns rows with no metrics. Names match regardless of case, surrounding whitespace, underscores, spaces, hyphens and colons.bounceRateandaverageTimeOnPagecan now each be requested alone, and a request naming one never receives the other.
11/11/2026
- [Breaking] FunnelFlux no longer adds
origin_page_idororigin_page_nametoaction_datain webhook and middleware payloads. Read the new top-levelreferring_page_idandreferring_page_namefields instead. The otheraction_dataorigin keys (origin_node_id,origin_node_name,origin_node_type) are unchanged, and action parameters submitted by the visitor's request still pass through as customer data even when their names match the removed keys. - Every webhook payload (
node_execution,on_action,conversion_triggered,custom_event_triggered) and every middleware POST payload now carries top-levelreferring_page_idandreferring_page_namestrings. They name the most recent page in the current journey before the current step, or before the converting page hit for conversion and custom-event webhooks. Both are always sent from the release that contains runtime change01a85a4df, and both are empty strings when no earlier page exists. When the page-name lookup fails,referring_page_idis still set andreferring_page_nameis an empty string. They are JSON payload fields, not URL tokens. The webhook payload JSON Schema declares both as optional strings, so stored1.0payloads from earlier deliveries stay valid;schema_versionstays"1.0".
03/11/2026
- [Breaking]
IntegrationCapabilities.capi.forced(returned byGET /integrations/capabilities) is renamed tocapi.available, matchingcostSync.availableanddictionarySync.available. It is true when the provider offers conversion delivery; a traffic source's own choice staysintegration.features.capi.enabled.forcedis no longer returned, so clients that read it must switch toavailable. - Ledger and Reporting now document a single authentication scheme,
Authorization: Bearer TOKEN. Thekeyquery parameter andX-API-Keyheader schemes are no longer listed. - Traffic source
meta.conversionTrackingMode(classicorintegrations) works with integration setup to choose the route: Classic URL, HTML pixel and custom-event postbacks fire unless the stored mode isintegrationsand the linked connection plus CAPI switch are on. Stored Classic never sends provider conversions; provider delivery for stored Integrations requires full setup; a legacy or unset mode retains classic delivery and sends CAPI when the integration is fully set up. Saving in Integrations mode removes the stored classicpostback,customEventPostbackandconversionTrackingSettings; saving in Classic mode, or without a mode, keeps them. TrafficSourceIntegration.platformis documented as read-only: it is derived from the linked connection and any client-sent value is ignored.- Saved short links: archived links keep routing traffic and keep their slug reserved; unarchive returns them to the active list. Delete remains the only operation that stops routing.
- Data reset (
POSTandDELETE /v1/reporting/update/reset/) now requires at least one restriction besidestimeStart/timeEndand rejects blankrestrictToFunnelIDsentries with 400.restrictToTrackingFieldskeys are documented. - Cost updates document a 400 response for rejected segment restrictions; Known Proxy and Hosting Provider connection types require
includeProxyHostingTraffic=true. Entrances excluded byincludeFilteredTrafficorincludeProxyHostingTraffickeep their existing cost. ArestrictToDeviceTypeofUnknownalso matches entrances with no device data. - Connection Type filters:
""and theConnection data not availablelabel match rows with no connection data only;"0"matches id 0 only. - Integration queue rows now include
transactionIdanddestinationEvent. - Funnel nodes document the
armornode type andnodeArmorRefParams, with theArmorConfigschema.
22/10/2026
- Reporting filters for
Connection: Connection Type,Device: Device TypeandFiltered Statusnow accept the display label (case-insensitive) or the numeric id string returned by drilldown rows. Unknown values and wildcards return 400. For Device Type, the empty id""and theUnknownlabel match id 0 and rows with no device data;"0"matches id 0 only. For Connection Type,""matches id 0, and only theConnection data not availablelabel matches rows with no connection data. - Reporting endpoints no longer document a
429 Rate limit exceededresponse. The reporting API no longer applies its own rate limit; account-level rate limits still apply.
12/10/2026
- [Breaking-ish]
IntegrationCapabilities(returned byGET /integrations/capabilities) no longer includesdisabledReason.enabledno longer defaults totrue: it is now always derived from the provider's configured capability set and isfalsewhen that set is empty. Clients should stop treating a missingenabledas enabled and stop readingdisabledReason. GET /integrations/{id}/ad-accountsnow documentsadAccountsas a required response field. Successful discovery with no visible accounts returnsadAccounts: []rather than omitting the field.
08/10/2026
- Added
POST /reporting/logs/integrations/queue(tagLogs): read-only, paginated view of the authenticated owner's delayed integration queue rows. Request bodyIntegrationQueueLogParams; responseIntegrationQueueLogReportwithIntegrationQueueLogReportRowrows andIntegrationQueueLogMetadata.status=completedmeans the delayed-work row closed, not that the conversion was delivered; an expired held row isstatus=failedwithlastErrorexactlyexpired. Semantic and filter validation failures return 422 with code 606. POST /reporting/logs/integrationsdescription now documents the rowoutcomevalues (queued,delivered,skipped,failed,unknown) and the matching outcome filter.unknownmatches a stored empty outcome, and no outcome is excluded by default.
03/10/2026
IntegrationCapabilities.capi.configFieldsentries (IntegrationCAPIConfigFieldRequirement) now carry a requiredscopefield (traffic_source_link) and no longer expose the previousalternativesarray. [Breaking-ish] — callers readingalternativesmust switch toscope;scopeis required.IntegrationCapabilities.costSync.dailyReconcilenow exposesscheduleMode(local_delayorfixed_utc_hour) andfinalizationUtcHour, alongside the existingfinalizationDelayMinutes, so clients can render the reconciliation schedule.- Added optional per-link CAPI credentials on
TrafficSourceIntegration:datasetId(Meta dataset or pixel ID) andeventSourceId(TikTok Events APIevent_source_id— not the Marketing API numeric pixel ID); both are required when CAPI is enabled for that provider. A per-linktestEventCodeis also accepted for provider test events. TrafficSourceIntegrationEventMappingdestinationtypenow also acceptsconversion_goal, in addition toconversion_actionandevent_name.
09/09/2026
- Middleware config
timeoutMsnow accepts1through60000. The effective cap is plan-dependent (Middleware basic 10s, Middleware Pro 30s synchronous); values above30000take effect only withloadingPage.enabled(detached execution, up to 60s). - Added
MiddlewareConfig.loadingPage(MiddlewareLoadingPage/MiddlewareLoadingTheme/MiddlewareLoadingTextStep) for the Middleware Pro interstitial shown while a detached request runs. - Added
MiddlewareConfig.responseData(MiddlewareResponseData/MiddlewareResponseVar) for Middleware Pro response-variable extraction, optional redirect query append, and JS delivery. - Added
MiddlewareConfig.restrictSentData(MiddlewareRestrictSentData/MiddlewareSentDataFilter) to allow-list outboundtracking_fieldsand visitor-submitted data-buffer keys on all plans. - Added authenticated
POST /reporting/logs/integrationsfor paged integration delivery logs (IntegrationLogParams/IntegrationLogReport). IntegrationCapabilities.capinow includesconfigFields(IntegrationCAPIConfigFieldRequirement) describing required CAPI configuration keys, labels, and alternatives.
21/08/2026
- Added Saved Short Links under the Assets API (
Short Linkstag):GET /shortlink/list/,GET /shortlink/find/byId/,GET /shortlink/find/bySlug/,POST /shortlink/save/,PUT /shortlink/save/,DELETE /shortlink/delete/,POST /shortlink/duplicate/,PUT /shortlink/archive/, andPUT /shortlink/unarchive/. The target is a structured funnel entrance, not a generic URL. DELETE /shortlink/delete/hard-deletes the row and frees its slug; this is not reversible. UsePUT /shortlink/archive/for the recoverable op — archived links keep their slug reserved and are not routable at Edge.POST /shortlink/duplicate/requires both a name and a slug (the server cannot derive a user-visible slug) and always creates an active copy. Slug collisions returnduplicate_slug, orduplicate_slug_archivedwhen the holder is archived.GET /integrations/{id}/ad-accounts/{adAccountId}/conversion-goalsnow accepts optionalloginCustomerIdfor manager/login customer context from ad-account discovery.
18/08/2026
- [Breaking] Reporting removed
Insight: Time on Pagefrom the drilldown grouping attributes. Time on page is now stored at millisecond resolution, so per-value grouping is no longer offered; useInsight: Time on Page Segmentsfor duration bands. - [Breaking-ish]
restrictToMetricsonPOST /reporting/drilldownnow returns the default metric set when empty, rather than all metrics.averageTimeOnPageand the newbounceRateare excluded from that default set. - Added
bounceRateto drilldown rows: the share of measured page views, as a percentage from 0 to 100, that ended in under 3000 ms. The denominator is beacon-measured page views only, so the metric describes JS-tracked traffic. averageTimeOnPageandbounceRateare opt-in and are returned only when named explicitly inrestrictToMetrics. Both are omitted — never0— when nothing was measured, so render an absent value as "no data" rather than zero.IntegrationAdAccountnow returnstimezone,businessId, andbusinessName.POST /reporting/drilldownnow documents a400response for an invalid grouping attribute, i.e. one not returned byGET /reporting/attributes/.restrictToMetricsonPOST /reporting/logs/incoming-postbacksis now a documented enum of the valid row-field names.- The
200response on the reporting cost-update endpoint is clarified: cost updates are accepted for asynchronous processing, matching segments are queued, zero-entrance segments complete as no-ops, and warehouse application happens after the response. - Tag responses now include
tagTypeandtagValue. - Documented the outgoing-connection rules enforced when saving a funnel:
webhookandvisitorTagnodes must have exactly one outgoing connection to an active node;externalUrlnodes must have none;root,rotator,condition,logic,actionProxy, andmiddlewarenodes must have at least one;lander,offer,landerGroup,offerGroup, andlabelnodes are unrestricted.
09/08/2026
- Added Auth API integration lifecycle and synchronization endpoints under
/integrations, including OAuth, reauthorization, ad-account, conversion-goal, and sync-status operations. - [Breaking] Billing subscription and usage routes now use
/subscriptions/meand/usage/eventsinstead of/subscriptionand/usage; added addon trial start, cancel, convert, and eligibility endpoints. - Added
TrafficSource.integrationconfiguration schemas for server-side delivery, dictionary sync, cost sync, and event mapping. - Reporting now documents
averageTimeOnPage, explicitrestrictToMetricsvalues, and optionaltimezonefields for conversion and custom-event uploads.
16/07/2026
- Added authenticated, owner-scoped
POST /reporting/logs/incoming-postbacksfor paged raw incoming-postback logs.restrictToMetricsselectively returns requested row fields (case-insensitive); conversion rows returneventNumber: null.
15/06/2026
- [Breaking-ish] Middleware destination
timeoutMsnow accepts1through10000, clamps to 10 seconds, and still defaults to 5 seconds. - Middleware Config list
statusnow explicitly allows an empty query value; empty ornot-deletedexcludes deleted configs. - [Breaking] Middleware routes now use
idRoutestring route keys pluspriorityfor evaluation order. The default route isidRoute: "default"withpriority: 0; non-default routes use priorities1through255. - [Breaking] Middleware funnel connections now use
connectionMiddlewareParams.onRouteIdwith string route keys such asapproved,review, ordefault. - [Breaking-ish] Middleware reporting logs now return
matchedRouteIDas the string route key and no longer exposematchedRouteLabel. Middleware summary rows includeaverageLatencyMs. - Added
hasBasicAuthPasswordandhasHmacSecrettoMiddlewareDestinationso clients can detect and preserve stored middleware destination secrets. REST read responses now return********placeholders instead of realbasicAuth.passwordorhmacSecretvalues when those secrets are set. - Added
nodeMiddlewareRefParams.destinationOverridesfor middleware funnel nodes, supporting node-levelheaders,basicAuth.username,basicAuth.password,hmacSecret,hasBasicAuthPassword, andhasHmacSecretwithout overriding destination URL, method, or type. - Documented
execute_timeout_msin outbound Middleware Node POST payloads and added Middleware Function Templates with copy-ready JavaScript, TypeScript, Python, Go, Cloudflare Workers, and Google Cloud Functions examples. - Removed
MiddlewareRoute.responseModefrom the Middleware Config contract. Middleware routes now always continue through the selected funnel connection; nonavigate,return_success, orreturn_rejectresponse modes are exposed in the MVP API. - Tightened middleware condition validation docs:
body_json.<path>accepts dot segments only,status_codevalues must be integer HTTP codes from100to599, andbody_textsupports text operators. - Updated
MiddlewareDestination.urldocumentation to clarify that middleware destinations must be HTTPS outside development environments. - Documented that FunnelFlux token placeholders are plaintext-only for middleware destination URLs and are not expanded inside custom header values.
- Added global page group category endpoints on both
/page/group/*and/pagegroup/*paths usingcategoryType=landerGrouporcategoryType=offerGroup; only global page groups are category-managed. - Added reporting attributes
Element: Global Lander Group CategoryandElement: Global Offer Group Category.
12/06/2026
- Added Middleware Config endpoints under the Assets API for listing, finding, creating, updating, deleting, duplicating, archiving, unarchiving, and moving middleware configurations by category.
- Added
POST /reporting/logs/middleware/summaryto return middleware configuration assets merged with middleware execution-log aggregates. - Added a Middleware Nodes guide covering synchronous routing behavior, request payloads, delivery headers, route evaluation, timeouts, fallback behavior, and destination restrictions.
09/06/2026
- Updated
POST /auth/loginto document the MFA-required response shape withmfa_required,mfa_token,factor, andmfa_requirements; internal MFA follow-up endpoints remain hidden from the public API docs. - Corrected Auth API token and user response field types:
expires_atandupdated_atare numeric timestamps,permissionsis an array of strings, andemail_verifiedis a boolean.
08/06/2026
- Added Logic Script asset endpoints under the Assets API for listing, finding, creating, updating, deleting, duplicating, archiving, unarchiving, and moving Logic Scripts by category.
- Added Logic Script helper endpoints:
GET /logicscripts/languagefor the backend-owned language catalog andPOST /logicscripts/validatefor validating script code, static route keys, and dynamic route detection. - Added funnel logic-node routing support through
connectionLogicParams.onRouteKeys[]; connect adefaultroute for runtime fallback when validation, compilation, execution, or dynamic route matching cannot produce a connected route. - Updated funnel delete documentation to clarify that Logic Scripts are global assets and are not deleted by funnel cascade.
- Added a Logic Scripts guide for building route-key scripts, including a copyable AI prompt for generating valid snippets.
01/06/2026
- Added Webhook Config endpoints under the Assets API for listing, finding, creating, updating, deleting, duplicating, archiving, unarchiving, and moving webhook configurations by category.
- Added
POST /reporting/logs/webhooks/summaryto return webhook configuration assets merged with webhook delivery-log aggregates. - Added funnel schema support for webhook nodes and action-triggered webhook dispatch via
nodeWebhookRefParams,connectionActionParams.webhookConfigIDs, andconnectionActionProxyParams.webhookConfigIDs. - Added Webhook Payloads, including the public
webhook_outbound_payload_v1delivery headers, event types, examples, and downloadable JSON Schema.
23/05/2026
- Bulk delete and archive endpoints for offer sources, categories, campaigns (funnel groups V1), and funnel groups V2 now accept a
ParentMutationRequestbody with acascadeActionofcascade,move, ororphan, plus an optionaltargetParentID(required whencascadeActionismove). Omitting cascade options preserves existing behaviour. Legacy single-ID query parameters (idOfferSource,idCategory, etc.) remain accepted for backwards compatibility. - Funnel delete now documents its cascade scope: funnel-scoped (local) assets are soft-deleted alongside the funnel — page groups, conditions and logic scripts whose
restrictToFunnelIdpoints at it, plus AI node settings belonging to that funnel. - Added
POST /reporting/update/customevents/to submit custom event updates. - Visitor Tag endpoints (
/visitor-tags/...) are now fully documented: find, list, list-by-status, create, update, duplicate, delete, archive/unarchive, and move-category.
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
/categoryAPI 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