@affiliateo/web 4.3.0 → 4.4.1

package/README.md

@@ -1,238 +1,238 @@
-# @affiliateo/web
-
-Affiliateo web SDK. track affiliate visits and pass attribution metadata to your Stripe checkout.
-
-## Install
-
-```bash
-npm install @affiliateo/web
-```
-
-## Setup
-
-1. Connect your Stripe account on the Affiliateo dashboard
-2. Wrap your app in `<AffiliateoProvider>` with your campaign ID
-3. At checkout time, call `getAttribution()` and pass the result to Stripe metadata
-
-### Step 1. wrap your app
-
-```tsx
-// app/layout.tsx (Next.js App Router) or _app.tsx (Pages Router)
-import { AffiliateoProvider } from '@affiliateo/web';
-
-export default function RootLayout({ children }) {
-  return (
-    <AffiliateoProvider campaignId="YOUR_CAMPAIGN_ID">
-      {children}
-    </AffiliateoProvider>
-  );
-}
-```
-
-The provider:
-- Reads `?ref=` from the URL when a visitor arrives
-- Stores attribution in `localStorage` so it survives navigation
-- Sends pageview events to Affiliateo for click tracking
-
-### Step 2. in your checkout button (client-side)
-
-```tsx
-'use client'
-import { getAttribution } from '@affiliateo/web';
-
-async function handleCheckout() {
-  const attribution = getAttribution();
-
-  const res = await fetch('/api/checkout', {
-    method: 'POST',
-    body: JSON.stringify({ attribution }),
-  });
-
-  const { url } = await res.json();
-  window.location.href = url;
-}
-```
-
-`getAttribution()` reads `affiliateo_ref`, `affiliateo_visitor_id`, and `affiliateo_campaign_id` from `localStorage` and returns them as an object, ready to pass to Stripe.
-
-### Step 3. in your checkout API route (server-side)
-
-```ts
-// app/api/checkout/route.ts
-export async function POST(req) {
-  const { attribution } = await req.json();
-
-  const session = await stripe.checkout.sessions.create({
-    line_items: [{ price: 'price_xxx', quantity: 1 }],
-    mode: 'payment',
-    success_url: 'https://yoursite.com/success',
-    cancel_url: 'https://yoursite.com/cancel',
-    metadata: attribution,
-  });
-
-  return Response.json({ url: session.url });
-}
-```
-
-That's it. Affiliateo's webhook will automatically read the metadata and credit the right affiliate when the payment succeeds.
-
-## How it works
-
-1. Visitor clicks affiliate link → `yoursite.com?ref=pinkproton`
-2. `<AffiliateoProvider>` reads `?ref=pinkproton` from the URL and saves it in `localStorage`
-3. As the visitor browses, attribution stays in their browser
-4. At checkout, `getAttribution()` reads localStorage and returns the attribution object
-5. Your server passes it as Stripe metadata when creating the checkout session
-6. When Stripe fires the `checkout.session.completed` webhook, Affiliateo reads the metadata and credits the affiliate
-
-## Why `localStorage` and not cookies?
-
-- **Not blocked by Safari ITP or most privacy tools**
-- **No CSRF concerns**
-
-## GDPR / ePrivacy. merchant responsibility
-
-The SDK writes persistent identifiers (`affiliateo_visitor_id`, `affiliateo_ref`, `affiliateo_campaign_id`) to the visitor's `localStorage` and sends pageview events that include the visitor's IP, user agent, and approximate geolocation to Affiliateo's servers. Under EU ePrivacy (Article 5(3)) and GDPR, persistent identifiers stored on a visitor's device require prior consent the same way cookies do.
-
-If you serve visitors in the EU/EEA, UK, or any jurisdiction with equivalent rules, **you are responsible for obtaining consent before this script loads**, the same way you would for Google Analytics, Meta Pixel, or any other analytics tool. Typical approaches:
-
-- Gate the `<AffiliateoProvider>` (or the `<script src="…/t.js">` tag) behind your cookie banner's "accept" callback so it only loads after consent.
-- Document Affiliateo in your privacy policy as a processor (see our [Data Processing Agreement](https://affiliateo.com/dpa)) and list the categories of data collected.
-
-Affiliateo acts as your data processor for visitor analytics. You are the controller and decide the lawful basis for processing your visitors' data.
-
-## Alternative: vanilla HTML (no React)
-
-If you're not using React, use the tracking script directly instead of the provider:
-
-```html
-<script defer
-  data-campaign="YOUR_CAMPAIGN_ID"
-  src="https://affiliateo.com/t.js"
-></script>
-```
-
-Then in your checkout flow (vanilla JS):
-
-```js
-const attribution = {
-  affiliateo_ref: localStorage.getItem('affiliateo_ref'),
-  affiliateo_visitor_id: localStorage.getItem('affiliateo_visitor_id'),
-  affiliateo_campaign_id: localStorage.getItem('affiliateo_campaign_id'),
-};
-
-// Send to your server with the rest of your checkout payload
-fetch('/api/checkout', {
-  method: 'POST',
-  body: JSON.stringify({ attribution }),
-});
-```
-
-## Track conversion goals
-
-Pageviews auto-track. For specific moments that matter to your funnel
-(`signup_completed`, `trial_started`, `initiate_checkout`, etc.), use
-`track()` or HTML data attributes.
-
-### From React
-
-```tsx
-'use client'
-import { useEffect } from 'react'
-import { useAffiliateRef } from '@affiliateo/web'
-
-export default function SignupSuccess() {
-  const { track } = useAffiliateRef()
-  useEffect(() => {
-    track('signup_completed', { plan: 'free' })
-  }, [])
-  return <div>Welcome!</div>
-}
-```
-
-### HTML data attributes (zero JS, works everywhere)
-
-```html
-<button data-affiliateo-goal="initiate_checkout"
-        data-affiliateo-goal-price="49"
-        data-affiliateo-goal-plan="pro">
-  Subscribe
-</button>
-```
-
-The SDK auto-fires the goal on click. Optional `data-affiliateo-goal-*`
-attributes become metadata (kebab-case → snake_case, up to 10 params).
-
-### Scroll-depth tracking
-
-```html
-<section data-affiliateo-scroll="pricing_viewed">
-  ...your pricing content...
-</section>
-```
-
-Fires the first time any pixel of the section overlaps the viewport.
-Maximum permissiveness — if the user scrolled enough to see even a sliver,
-it counts. Earlier versions required 50% visibility, which was unreachable
-for tall sections (a pricing page with comparison tables silently dropped
-out of every funnel). Great for landing pages where you want to know
-which sections convert.
-
-### Goal naming rules
-
-Lowercase letters, digits, underscores, hyphens, colons. Max 64 chars.
-Metadata bounded to 4KB JSON.
-
-## Identify signed-in users (cross-device stitching)
-
-Without `identify()`, the same person browsing on phone and buying on
-laptop counts as two visitors. Call it once after sign-in:
-
-```tsx
-'use client'
-import { useEffect } from 'react'
-import { useAffiliateRef } from '@affiliateo/web'
-import { useUser } from './your-auth'
-
-export default function AuthBoundary({ children }) {
-  const { identify } = useAffiliateRef()
-  const user = useUser()
-  useEffect(() => {
-    if (user) identify(user.id)
-  }, [user])
-  return <>{children}</>
-}
-```
-
-Idempotent. safe to fire on every page load while a user is signed in.
-**user_id only.** The SDK does not accept, collect, or transmit email
-or any other PII.
-
-## API
-
-### `<AffiliateoProvider campaignId="..." apiUrl?="...">`
-
-React provider. Wrap your app once. Reads `?ref=` from URL, persists to localStorage, sends pageview events, sets up data-attribute + scroll listeners.
-
-Props:
-- `campaignId` (required): your Affiliateo campaign ID
-- `apiUrl` (optional): defaults to `https://affiliateo.com`
-
-### `useAffiliateRef()`
-
-React hook that returns `{ refCode, visitorId, track, identify }`.
-
-- `track(eventName, metadata?)`. fire a custom goal
-- `identify(userId)`. link this visitor to a merchant user_id (no PII)
-
-### `getAttribution()`
-
-Client-side function. Returns an object with `affiliateo_ref`, `affiliateo_visitor_id`, and `affiliateo_campaign_id` from localStorage. Pass directly as Stripe `metadata`.
-
-## Framework support
-
-Works with any JavaScript framework or vanilla JS:
-- **Next.js** (App Router & Pages Router)
-- **Remix** / **React Router**
-- **Vite + React**
-- **Vanilla JS/HTML** (use the `<script>` tag instead)
+# @affiliateo/web
+
+Affiliateo web SDK. track affiliate visits and pass attribution metadata to your Stripe checkout.
+
+## Install
+
+```bash
+npm install @affiliateo/web
+```
+
+## Setup
+
+1. Connect your Stripe account on the Affiliateo dashboard
+2. Wrap your app in `<AffiliateoProvider>` with your campaign ID
+3. At checkout time, call `getAttribution()` and pass the result to Stripe metadata
+
+### Step 1. wrap your app
+
+```tsx
+// app/layout.tsx (Next.js App Router) or _app.tsx (Pages Router)
+import { AffiliateoProvider } from '@affiliateo/web';
+
+export default function RootLayout({ children }) {
+  return (
+    <AffiliateoProvider campaignId="YOUR_CAMPAIGN_ID">
+      {children}
+    </AffiliateoProvider>
+  );
+}
+```
+
+The provider:
+- Reads `?ref=` from the URL when a visitor arrives
+- Stores attribution in `localStorage` so it survives navigation
+- Sends pageview events to Affiliateo for click tracking
+
+### Step 2. in your checkout button (client-side)
+
+```tsx
+'use client'
+import { getAttribution } from '@affiliateo/web';
+
+async function handleCheckout() {
+  const attribution = getAttribution();
+
+  const res = await fetch('/api/checkout', {
+    method: 'POST',
+    body: JSON.stringify({ attribution }),
+  });
+
+  const { url } = await res.json();
+  window.location.href = url;
+}
+```
+
+`getAttribution()` reads `affiliateo_ref`, `affiliateo_visitor_id`, and `affiliateo_campaign_id` from `localStorage` and returns them as an object, ready to pass to Stripe.
+
+### Step 3. in your checkout API route (server-side)
+
+```ts
+// app/api/checkout/route.ts
+export async function POST(req) {
+  const { attribution } = await req.json();
+
+  const session = await stripe.checkout.sessions.create({
+    line_items: [{ price: 'price_xxx', quantity: 1 }],
+    mode: 'payment',
+    success_url: 'https://yoursite.com/success',
+    cancel_url: 'https://yoursite.com/cancel',
+    metadata: attribution,
+  });
+
+  return Response.json({ url: session.url });
+}
+```
+
+That's it. Affiliateo's webhook will automatically read the metadata and credit the right affiliate when the payment succeeds.
+
+## How it works
+
+1. Visitor clicks affiliate link → `yoursite.com?ref=pinkproton`
+2. `<AffiliateoProvider>` reads `?ref=pinkproton` from the URL and saves it in `localStorage`
+3. As the visitor browses, attribution stays in their browser
+4. At checkout, `getAttribution()` reads localStorage and returns the attribution object
+5. Your server passes it as Stripe metadata when creating the checkout session
+6. When Stripe fires the `checkout.session.completed` webhook, Affiliateo reads the metadata and credits the affiliate
+
+## Why `localStorage` and not cookies?
+
+- **Not blocked by Safari ITP or most privacy tools**
+- **No CSRF concerns**
+
+## GDPR / ePrivacy. merchant responsibility
+
+The SDK writes persistent identifiers (`affiliateo_visitor_id`, `affiliateo_ref`, `affiliateo_campaign_id`) to the visitor's `localStorage` and sends pageview events that include the visitor's IP, user agent, and approximate geolocation to Affiliateo's servers. Under EU ePrivacy (Article 5(3)) and GDPR, persistent identifiers stored on a visitor's device require prior consent the same way cookies do.
+
+If you serve visitors in the EU/EEA, UK, or any jurisdiction with equivalent rules, **you are responsible for obtaining consent before this script loads**, the same way you would for Google Analytics, Meta Pixel, or any other analytics tool. Typical approaches:
+
+- Gate the `<AffiliateoProvider>` (or the `<script src="…/t.js">` tag) behind your cookie banner's "accept" callback so it only loads after consent.
+- Document Affiliateo in your privacy policy as a processor (see our [Data Processing Agreement](https://affiliateo.com/dpa)) and list the categories of data collected.
+
+Affiliateo acts as your data processor for visitor analytics. You are the controller and decide the lawful basis for processing your visitors' data.
+
+## Alternative: vanilla HTML (no React)
+
+If you're not using React, use the tracking script directly instead of the provider:
+
+```html
+<script defer
+  data-campaign="YOUR_CAMPAIGN_ID"
+  src="https://affiliateo.com/t.js"
+></script>
+```
+
+Then in your checkout flow (vanilla JS):
+
+```js
+const attribution = {
+  affiliateo_ref: localStorage.getItem('affiliateo_ref'),
+  affiliateo_visitor_id: localStorage.getItem('affiliateo_visitor_id'),
+  affiliateo_campaign_id: localStorage.getItem('affiliateo_campaign_id'),
+};
+
+// Send to your server with the rest of your checkout payload
+fetch('/api/checkout', {
+  method: 'POST',
+  body: JSON.stringify({ attribution }),
+});
+```
+
+## Track conversion goals
+
+Pageviews auto-track. For specific moments that matter to your funnel
+(`signup_completed`, `trial_started`, `initiate_checkout`, etc.), use
+`track()` or HTML data attributes.
+
+### From React
+
+```tsx
+'use client'
+import { useEffect } from 'react'
+import { useAffiliateRef } from '@affiliateo/web'
+
+export default function SignupSuccess() {
+  const { track } = useAffiliateRef()
+  useEffect(() => {
+    track('signup_completed', { plan: 'free' })
+  }, [])
+  return <div>Welcome!</div>
+}
+```
+
+### HTML data attributes (zero JS, works everywhere)
+
+```html
+<button data-affiliateo-goal="initiate_checkout"
+        data-affiliateo-goal-price="49"
+        data-affiliateo-goal-plan="pro">
+  Subscribe
+</button>
+```
+
+The SDK auto-fires the goal on click. Optional `data-affiliateo-goal-*`
+attributes become metadata (kebab-case → snake_case, up to 10 params).
+
+### Scroll-depth tracking
+
+```html
+<section data-affiliateo-scroll="pricing_viewed">
+  ...your pricing content...
+</section>
+```
+
+Fires the first time any pixel of the section overlaps the viewport.
+Maximum permissiveness — if the user scrolled enough to see even a sliver,
+it counts. Earlier versions required 50% visibility, which was unreachable
+for tall sections (a pricing page with comparison tables silently dropped
+out of every funnel). Great for landing pages where you want to know
+which sections convert.
+
+### Goal naming rules
+
+Lowercase letters, digits, underscores, hyphens, colons. Max 64 chars.
+Metadata bounded to 4KB JSON.
+
+## Identify signed-in users (cross-device stitching)
+
+Without `identify()`, the same person browsing on phone and buying on
+laptop counts as two visitors. Call it once after sign-in:
+
+```tsx
+'use client'
+import { useEffect } from 'react'
+import { useAffiliateRef } from '@affiliateo/web'
+import { useUser } from './your-auth'
+
+export default function AuthBoundary({ children }) {
+  const { identify } = useAffiliateRef()
+  const user = useUser()
+  useEffect(() => {
+    if (user) identify(user.id)
+  }, [user])
+  return <>{children}</>
+}
+```
+
+Idempotent. safe to fire on every page load while a user is signed in.
+**user_id only.** The SDK does not accept, collect, or transmit email
+or any other PII.
+
+## API
+
+### `<AffiliateoProvider campaignId="..." apiUrl?="...">`
+
+React provider. Wrap your app once. Reads `?ref=` from URL, persists to localStorage, sends pageview events, sets up data-attribute + scroll listeners.
+
+Props:
+- `campaignId` (required): your Affiliateo campaign ID
+- `apiUrl` (optional): defaults to `https://affiliateo.com`
+
+### `useAffiliateRef()`
+
+React hook that returns `{ refCode, visitorId, track, identify }`.
+
+- `track(eventName, metadata?)`. fire a custom goal
+- `identify(userId)`. link this visitor to a merchant user_id (no PII)
+
+### `getAttribution()`
+
+Client-side function. Returns an object with `affiliateo_ref`, `affiliateo_visitor_id`, and `affiliateo_campaign_id` from localStorage. Pass directly as Stripe `metadata`.
+
+## Framework support
+
+Works with any JavaScript framework or vanilla JS:
+- **Next.js** (App Router & Pages Router)
+- **Remix** / **React Router**
+- **Vite + React**
+- **Vanilla JS/HTML** (use the `<script>` tag instead)

package/dist/bot-detect.d.ts

@@ -1,5 +1,5 @@
 /**
- * Client-side bot detection. Mirrors Datafast / PostHog / Plausible's
+ * Client-side bot detection. Mirrors PostHog / Plausible's
  * approach: catch the obvious automation tools at SDK init so they
  * never fire a single network request.
  *
@@ -20,8 +20,8 @@
  * layer 3 (kicks in on the request), then layer 2 (server checks before
  * writing). If any one layer rejects, the event drops.
  *
- * Patterns sourced from the Datafast script tag + npm SDK (publicly
- * inspectable). We include their full list because it represents years
+ * Patterns sourced from widely-used analytics SDKs (publicly
+ * inspectable). We include a comprehensive list because it represents years
  * of accumulated bot-shape knowledge that's expensive to reproduce.
  */
 /**

package/dist/bot-detect.js

@@ -1,5 +1,5 @@
 /**
- * Client-side bot detection. Mirrors Datafast / PostHog / Plausible's
+ * Client-side bot detection. Mirrors PostHog / Plausible's
  * approach: catch the obvious automation tools at SDK init so they
  * never fire a single network request.
  *
@@ -20,8 +20,8 @@
  * layer 3 (kicks in on the request), then layer 2 (server checks before
  * writing). If any one layer rejects, the event drops.
  *
- * Patterns sourced from the Datafast script tag + npm SDK (publicly
- * inspectable). We include their full list because it represents years
+ * Patterns sourced from widely-used analytics SDKs (publicly
+ * inspectable). We include a comprehensive list because it represents years
  * of accumulated bot-shape knowledge that's expensive to reproduce.
  */
 // Selenium/WebDriver/headless flags set on window or navigator. Modern

package/dist/provider.js

@@ -8,12 +8,12 @@ const DEFAULT_API_URL = 'https://affiliateo.com';
 const LS_VISITOR_ID = 'affiliateo_visitor_id';
 const LS_REF = 'affiliateo_ref';
 const LS_CAMPAIGN_ID = 'affiliateo_campaign_id';
-// Persistent opt-out flag. Mirrors Datafast's DATAFAST_IGNORE_TRACKING key —
+// Persistent opt-out flag (affiliateo_opt_out) —
 // when set to "true" the SDK silently noops every outbound call. Survives
 // page reloads. removed by optIn(). Checked at init time so a previously
 // opted-out visitor never re-fires auto-pageviews after a refresh.
 const LS_OPT_OUT = 'affiliateo_opt_out';
-// Client-owned session id (Datafast-style). The BROWSER owns the session,
+// Client-owned session id. The BROWSER owns the session,
 // not the server. One id is reused for every event within a sliding
 // 10-minute activity window, then a fresh one is minted. Because the id is
 // generated here and sent on each event, a burst of pageviews (a redirect
@@ -26,7 +26,7 @@ const SESSION_WINDOW_MS = 10 * 60 * 1000;
 // Same-URL pageview throttle, persisted in sessionStorage so it survives
 // hard navigations / redirect bounces (the old in-memory throttle reset on
 // every fresh page context, which let a 3-hop bounce fire 3 pageviews).
-// Different URLs are never throttled against each other. Mirrors Datafast's
+// Different URLs are never throttled against each other, with a
 // 60s same-URL suppression.
 const SS_PV_THROTTLE = 'affiliateo_pv_throttle';
 const PV_THROTTLE_MS = 60 * 1000;
@@ -88,7 +88,7 @@ function uuid() {
 // Get-or-create the current session id with a sliding 10-minute window.
 // Stored in localStorage so every tab and every page load in the same
 // browser shares one session. Each call slides the window forward (the same
-// way Datafast refreshes its session cookie on each event), so an actively
+// way a session cookie is refreshed on each event), so an actively
 // browsing visitor keeps one id and a returning visitor past the window
 // gets a fresh one. Returns a UUID string the server stamps onto the event.
 function getSessionId() {
@@ -169,7 +169,7 @@ export function AffiliateoProvider({ campaignId, apiUrl, allowedHostnames, allow
     // Normalize autoCapturePageviews. Three shapes:
     //   - undefined / true / object → auto-capture ON (with object overrides)
     //   - false → auto-capture OFF entirely (host must call trackPageview)
-    // Defaults match Datafast: captureInitialPageview true, trackHashChanges
+    // Sensible defaults: captureInitialPageview true, trackHashChanges
     // false, debounceMs 100.
     const autoCfg = autoCapturePageviews === false
         ? { enabled: false, captureInitialPageview: false, trackHashChanges: false, debounceMs: 100 }
@@ -299,7 +299,7 @@ export function AffiliateoProvider({ campaignId, apiUrl, allowedHostnames, allow
         }
         catch { /* swallow */ }
     }, [apiBase, log]);
-    // Manual pageview. Mirrors Datafast's trackPageview(path?). Same payload
+    // Manual pageview via trackPageview(path?). Same payload
     // shape the auto-fired pageview uses (see sendPageview inside the route
     // effect below) so server-side routing / dedup / IP+UA enrichment behave
     // identically for both code paths.
@@ -370,13 +370,13 @@ export function AffiliateoProvider({ campaignId, apiUrl, allowedHostnames, allow
     // affiliate ref so the next pageview is a brand-new anonymous visitor.
     // The campaign_id stays (it's a property of the site, not the visitor).
     //
-    // Matches Datafast's reset() semantics for non-cookieless mode: new
+    // reset() semantics for non-cookieless mode: new
     // visitor, no event fired, caller handles "tell the server about it"
     // by triggering whatever pageview / navigation comes next.
     //
     // Returns a Promise so callers can `await reset()` before navigating
     // (the localStorage writes are sync but the Promise lets the API stay
-    // consistent with Datafast's async signature, future-proofing for
+    // an async signature, future-proofing for
     // server-minted IDs in cookieless mode).
     const reset = useCallback(async () => {
         try {
@@ -766,8 +766,8 @@ export function AffiliateoProvider({ campaignId, apiUrl, allowedHostnames, allow
         // Debouncing collapses back-to-back navigation events into one. Some
         // frameworks (Next.js, certain Vue routers) fire pushState then
         // replaceState in the same tick to canonicalize the URL; without
-        // debouncing that's two pageviews per real navigation. Default 100ms
-        // matches Datafast; set debounceMs to 0 to disable.
+        // debouncing that's two pageviews per real navigation. Default 100ms;
+        // set debounceMs to 0 to disable.
         let lastPath = window.location.pathname;
         let lastHash = window.location.hash;
         let pendingPageviewTimer = null;
@@ -812,7 +812,7 @@ export function AffiliateoProvider({ campaignId, apiUrl, allowedHostnames, allow
         };
         // HTML-attribute goal scanning (`data-affiliateo-goal`,
         // `data-affiliateo-scroll`) and the IntersectionObserver that drove
-        // them were removed in 3.0.0 to match Datafast's npm SDK ergonomics:
+        // them were removed in 3.0.0 to streamline the npm SDK ergonomics:
         // SDK does pageview + track() + identify(); merchants fire goals
         // themselves via onClick={() => track('signup_clicked')} or by
         // wiring their own IntersectionObserver and calling track() from it.

package/dist/queue.d.ts

@@ -9,7 +9,7 @@
  *   networks (train wifi, subway transitions, dropping 4G) merchants saw
  *   ~10-15% fewer events than they should have.
  *
- *   This queue mirrors the pattern PostHog / Segment / Amplitude / Datafast
+ *   This queue mirrors the pattern PostHog / Segment / Amplitude
  *   all converged on: in-memory queue, localStorage persistence so events
  *   survive page reload, periodic auto-flush, retry on failure up to N
  *   times, drop after N tries to bound memory.
@@ -37,7 +37,7 @@
  *   - MAX_QUEUE_SIZE   hard cap so a long network outage can't fill
  *                      localStorage and break the host app. Events
  *                      beyond the cap are dropped FIFO (oldest first).
- *   - FLUSH_INTERVAL_MS = 5_000   matches Datafast's web SDK default
+ *   - FLUSH_INTERVAL_MS = 5_000   a sensible web SDK default
  *   - SIZE_FLUSH_THRESHOLD = 10   triggers a flush when queue grows
  *                                 past this even before the timer fires
  */

package/dist/queue.js

@@ -9,7 +9,7 @@
  *   networks (train wifi, subway transitions, dropping 4G) merchants saw
  *   ~10-15% fewer events than they should have.
  *
- *   This queue mirrors the pattern PostHog / Segment / Amplitude / Datafast
+ *   This queue mirrors the pattern PostHog / Segment / Amplitude
  *   all converged on: in-memory queue, localStorage persistence so events
  *   survive page reload, periodic auto-flush, retry on failure up to N
  *   times, drop after N tries to bound memory.
@@ -37,7 +37,7 @@
  *   - MAX_QUEUE_SIZE   hard cap so a long network outage can't fill
  *                      localStorage and break the host app. Events
  *                      beyond the cap are dropped FIFO (oldest first).
- *   - FLUSH_INTERVAL_MS = 5_000   matches Datafast's web SDK default
+ *   - FLUSH_INTERVAL_MS = 5_000   a sensible web SDK default
  *   - SIZE_FLUSH_THRESHOLD = 10   triggers a flush when queue grows
  *                                 past this even before the timer fires
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@affiliateo/web",
-  "version": "4.3.0",
+  "version": "4.4.1",
   "description": "Affiliateo web SDK — affiliate attribution and tracking for web apps",
   "main": "dist/index.js",
   "module": "dist/index.js",