Quickstart

Drop one script into your site, and Fidero starts capturing page views and click IDs straight away. Send an event with a single method call, and Fidero formats it, counts it once and delivers it to every tool in your stack. This page is the whole install: one snippet, one event, about two minutes.

The install is deliberately small. The real work happens after each event reaches Fidero.

Install and send your first event

Add the snippet to your <head>

Paste this into your site’s <head>, and replace YOUR_PROJECT_ID with your project’s ID.

<!-- Fidero: paste in your <head> -->
<script>
  // prettier-ignore
  !function(){let e=window.fidero=window.fidero??{};if(e.initialised)return;if(e.invoked)return console.error("[Fidero] Snippet included multiple times");e.invoked=!0;let r={};e.ready=new Promise((e,t)=>{r.resolve=e,r.reject=t}),e.ready.resolve=r.resolve,e.ready.reject=r.reject,e.buffered=[],e.initArgs=null,e.init=function(){return e.initArgs=Array.prototype.slice.call(arguments),e.ready};let t=function(r,t){return function(){let n=Array.prototype.slice.call(arguments);if(n.unshift(r),!t)return void e.buffered.push(n);let i={},d=new Promise(function(e,r){i.resolve=e,i.reject=r});return d.delivered=new Promise(function(e,r){i.resolveDelivered=e,i.rejectDelivered=r}),d.catch(function(){}),d.delivered.catch(function(){}),n.deferred=i,e.buffered.push(n),d}};["updateConsent","updateIdentity","reset"].forEach(r=>{e[r]=t(r,!1)}),["page","track"].forEach(r=>{e[r]=t(r,!0)}),e.load=r=>{let t=(r=r||"https://cdn.datahappy.co/sdk/v0.9/fidero.js").match(/.+sdk\/v?(.+)\/fidero.js/);null!==t&&t.length>=2&&(e.version=t[1]);let n=document.createElement("script");n.type="text/javascript",n.async=!0,n.src=r,(document.head||document.body).appendChild(n)}}()

  fidero.load();
  fidero.init("YOUR_PROJECT_ID");
  fidero.page();
</script>

The snippet loads asynchronously, captures the first page view, queues any calls made before it finishes loading, and pulls your project’s configuration from the server. It’s about a kilobyte.

Send your first event

Now send an event. Here’s a subscription starting:
```
fidero.track({
  event: "subscription_started",
  userId: "user_8f3a91",
  properties: {
    transaction_id: "sub_4Qb1Z7",
    value: 29.99,
    currency: "GBP",
  },
});
```
event is a standard name. Fidero gives you a fixed set of them: subscription_started, purchase_completed, trial_started and the rest, so naming is decided for you. The full set is on Standard events.

userId links this person’s earlier anonymous browsing to their profile. One profile then follows them from anonymous visitor to known customer. Pass identity inline like this, or set it once with updateIdentity.

In production you’d send a conversion like this from your backend, where the payment actually happens – the browser call is just the quickest route to a first event. Either way, always set transaction_id: it’s how a conversion counts once everywhere, even when Fidero delivers it to a destination through both a browser and a server channel.
Confirm it’s working

To watch it happen, initialise with debug: true:
```
fidero.init("YOUR_PROJECT_ID", { debug: true });
```
Fidero then prints [Fidero …] diagnostics to your browser console as it boots, loads your integrations and sends events. That’s enough to confirm the install is live, with no dashboard needed. You’ll also see the request to Fidero in your browser’s Network tab on every track call. Remove the debug option for production.

What Fidero delivers

This is everything you sent:

fidero.track({
  event: "subscription_started",
  userId: "user_8f3a91",
  properties: {
    transaction_id: "sub_4Qb1Z7",
    value: 29.99,
    currency: "GBP",
  },
});

Fidero delivers that conversion enriched with everything the browser knew weeks earlier and the event itself didn’t carry: the ad click that started the journey, the first- and last-touch campaigns, and the person’s resolved identity. It arrives formatted the way each destination needs it, so Meta, Google Ads and your warehouse all receive a complete, matchable event.

Fidero can do that because the server keeps each customer’s context, captured on that first visit and re-attached to every later event. The full event, traced from the click to the delivered conversion, is on How the pieces fit. Why the server holds that context is on the platform overview.

Next steps

That’s the install. Where you go next depends on your stack.

How the pieces fit The SDK, the endpoint and the config, with one event traced end to end.

SDK methods The whole API on one page: track, page, updateIdentity, updateConsent, reset and ready.

Server-side events Send events from your backend (Stripe renewals, webhooks, CRM triggers) where the memory earns its keep.

Your project is provisioned when you start, and built with you. See how little it takes: book an audit.