Skip to content

Changelog

Most changes to Fidero reach your project without anything to do on your side: adapters keep pace with destination APIs, fixes and new capabilities land on the server, and the SDK updates in place. This page records them. Configuration & changes covers why updates propagate this way.

HubSpot: transient authentication failures retried

Section titled “HubSpot: transient authentication failures retried”

3rd August 2026 · Adapter update

HubSpot’s Forms API intermittently rejects a valid token with a 401. Fidero now retries those submissions, so a lead is no longer lost to a momentary failure. A genuinely revoked token still fails after the retries.

2nd August 2026 · Browser SDK

track() now writes each event to a durable browser queue before any network request, so delivery survives a page unload rather than depending on the request completing. Queued events retry with backoff and drain on a later page view. await fidero.track(…) resolves once the event is queued, and .delivered waits for the server’s acknowledgement.

Personal data scrubbed from page URL query strings

Section titled “Personal data scrubbed from page URL query strings”

11th July 2026 · Server

When a query-string value on a page or referrer URL matches recognised personal data (an email address, today), Fidero now replaces it with [redacted] before the event fans out to your warehouse and destinations. Every other parameter arrives exactly as sent.

BigQuery: deduplicated view and project-scoped rows

Section titled “BigQuery: deduplicated view and project-scoped rows”

10th July 2026 · Adapter update

Fidero now provisions an events_deduped view alongside the events table. It returns one row per event, so there’s no dedup query to write. Every row also carries the Fidero project it came from. Deduplication, the traits view and erasure requests are all scoped by project, so two projects sharing a dataset can never mix rows.

Faster dispatch for events fired before a redirect

Section titled “Faster dispatch for events fired before a redirect”

26th June 2026 · Browser SDK

A track() call fired in the moment before a redirect (a purchase confirmation handing off to a thank-you page, say) now dispatches immediately instead of waiting on a polling delay, so the event survives the navigation.

Meta: app events with device advertising IDs

Section titled “Meta: app events with device advertising IDs”

11th June 2026 · Adapter update

Events on the mobile channel now reach Meta as app events, and the device advertising ID (from device.advertisingId) travels as Meta’s madid for matching.

Mixpanel: distinct_id on identified pageviews

Section titled “Mixpanel: distinct_id on identified pageviews”

31st May 2026 · Adapter update

Pageviews from identified users now set distinct_id to the user’s ID as intended. A grouping bug meant identified pageviews previously arrived in Mixpanel without one.

20th May 2026 · Browser SDK

Pre-consent events are queued, then replay once consent lands. Replay now waits for integrations to finish loading on every consent path, so nothing fires into a half-initialised page.

15th May 2026 · Adapter update

Form submissions carry the visitor’s captured consent into HubSpot’s native consent fields (legalConsentOptions), so GDPR consent and subscription enrolment are recorded where HubSpot expects them.

1st April 2026 · Browser SDK

CookieBot (Usercentrics) joins the supported consent platforms. Fidero reads the banner’s consent state at a reliable moment in CookieBot’s lifecycle and tracks mid-session changes, so per-destination enforcement works the same as with every other CMP.

13th March 2026 · New destination

Events stream into your own Snowflake account. Provisioning happens automatically on the first event, and right-to-erasure deletions propagate to the warehouse like any other destination.

25th February 2026 · Adapter update

The Google Ads adapter moved to API version v23. Conversions kept flowing while the version changed underneath – no project needed any action.

Accurate device signals for relayed mobile events

Section titled “Accurate device signals for relayed mobile events”

25th February 2026 · Server

Fidero now enriches events with the request’s IP address and user agent on the web channel only. Mobile events relayed through your backend previously risked inheriting the relay server’s values. Device signals now stay the device’s.

19th January 2026 · Browser SDK Server

When a consent object names some categories and not others, the unstated categories are now denied – in the SDK and on the server. An absent consent object still passes through unchanged, by design. Consent & privacy covers the model.

4th January 2026 · Adapter update

The Meta Conversions API adapter moved to v24.0, with no action needed on any project.

Match-rate fixes for names and UK phone numbers

Section titled “Match-rate fixes for names and UK phone numbers”

4th January 2026 · Server

Names are stripped of punctuation before hashing, as Meta requires – “Jean-Pierre” and “O’Connor” now match. UK phone numbers written “+44 (0) 7700 900123” now normalise to the correct E.164 form instead of keeping the stray zero.

8th October 2025 · New destination

Podscribe joins the destinations, connecting conversions back to podcast campaigns. Emails are SHA-256-hashed before sending, and IPv4 and IPv6 are both handled.