
Security News
RubyGems Adds Cooldown Feature to Bundler for Newly Published Gems
RubyGems and Bundler 4.0.13 introduced an opt-in cooldown feature that delays newly published gems during dependency resolution.
@bagdock/analytics
Advanced tools
Bagdock Analytics SDK — lightweight client-side event tracking with batching and dedup
----++ ----++ ---+++
---+++ ---++ ---++
----+--- ----- --------- --------++ ------ ----- ----++-----
---------+ --------++----------++--------+++--------+ --------++---++---++++
---+++---++ ++++---++---+++---++---+++---++---+++---++---++---++------++++
----++ ---++--------++---++----++---+++---++---++ ---+---++ -------++
----+----+---+++---++---++----++---++----++---++---+++--++ --------+---++
---------++--------+++--------+++--------++ -------+++ -------++---++----++
+++++++++ +++++++++- +++---++ ++++++++ ++++++ ++++++ ++++ ++++
--------+++
+++++++
Track events, attribute conversions, and measure engagement across Bagdock-powered self-storage apps. The SDK batches events client-side, deduplicates within a configurable window, captures UTM attribution automatically, and flushes gracefully on page unload.
npm install @bagdock/analytics
# or
bun add @bagdock/analytics
Your app calls track() methods. The SDK deduplicates, queues, and flushes events in batches to the Bagdock API over HTTPS.
sequenceDiagram
participant App
participant SDK as @bagdock/analytics
participant API as Bagdock API
App->>SDK: track({ eventType: 'lead' })
SDK->>SDK: Dedup check
SDK->>SDK: Attach UTM metadata
SDK->>SDK: Queue event
Note over SDK: Flush on timer (5 s) or batch full (25)
SDK->>API: POST /api/loyalty/events
API-->>SDK: 200 OK
On beforeunload and visibilitychange, the SDK flushes with navigator.sendBeacon so no events are lost during navigation.
import { BagdockAnalytics } from '@bagdock/analytics'
const analytics = new BagdockAnalytics({
apiKey: 'YOUR_API_KEY',
autoPageView: true,
})
analytics.trackLead({
operatorId: 'opreg_acme',
referralCode: 'REF123',
metadata: { source: 'pricing_page' },
})
analytics.trackSale({
operatorId: 'opreg_acme',
valuePence: 14900,
currency: 'GBP',
})
await analytics.flush()
analytics.destroy()
The SDK captures UTM parameters from the URL on init, persists them in sessionStorage for the tab's lifetime, and attaches them as metadata to every event.
// User lands on: https://example.com?utm_source=google&utm_medium=cpc&utm_campaign=spring
const analytics = new BagdockAnalytics({ apiKey: 'YOUR_API_KEY' })
analytics.getUTM()
// → { utm_source: 'google', utm_medium: 'cpc', utm_campaign: 'spring' }
analytics.trackLead({ operatorId: 'opreg_acme' })
// → event metadata includes utm_source, utm_medium, utm_campaign
Parse UTM parameters from any URL:
import { parseUTM } from '@bagdock/analytics'
parseUTM('https://example.com?utm_source=partner&utm_campaign=launch')
// → { utm_source: 'partner', utm_campaign: 'launch' }
Create a provider component that initializes the SDK once and tracks route changes:
'use client'
import { useEffect, useRef } from 'react'
import { usePathname, useSearchParams } from 'next/navigation'
import { BagdockAnalytics } from '@bagdock/analytics'
export function AnalyticsProvider({ children }: { children: React.ReactNode }) {
const pathname = usePathname()
const searchParams = useSearchParams()
const ref = useRef<BagdockAnalytics | null>(null)
const prevPath = useRef('')
useEffect(() => {
if (!ref.current) {
ref.current = new BagdockAnalytics({
apiKey: process.env.NEXT_PUBLIC_ANALYTICS_API_KEY!,
autoPageView: true,
})
}
return () => { ref.current?.destroy(); ref.current = null }
}, [])
useEffect(() => {
const path = pathname + (searchParams?.toString() ? `?${searchParams}` : '')
if (path !== prevPath.current) {
prevPath.current = path
ref.current?.trackPageView()
}
}, [pathname, searchParams])
return <>{children}</>
}
Wrap your root layout:
<AnalyticsProvider>
{children}
</AnalyticsProvider>
Track renders and clicks from embedded widgets on partner sites:
const analytics = new BagdockAnalytics({ apiKey: 'YOUR_API_KEY' })
analytics.trackEmbedRender('opreg_acme')
analytics.trackClick('link_abc123', 'REF456')
Track points, rewards, and referrals:
analytics.track({
eventType: 'points_earned',
memberId: 'mem_abc',
operatorId: 'opreg_acme',
valuePence: 500,
})
analytics.track({
eventType: 'reward_redeemed',
memberId: 'mem_abc',
metadata: { rewardId: 'rwd_xyz', tier: 'gold' },
})
analytics.track({
eventType: 'referral_completed',
referralCode: 'REF123',
memberId: 'mem_abc',
})
| Method | Description |
|---|---|
track(event) | Track any event with full control over the payload |
trackClick(linkId, referralCode?) | Track a link click with optional referral attribution |
trackLead(params) | Track a lead conversion |
trackSale(params) | Track a completed sale |
trackPageView() | Track a page view (captures URL and referrer automatically) |
trackEmbedRender(operatorId?) | Track when an embedded widget renders |
getUTM() | Return the current UTM attribution context |
flush() | Flush the event queue immediately |
destroy() | Flush remaining events, clear timers, remove listeners |
TrackableEventinterface TrackableEvent {
eventType: EventType
linkId?: string
memberId?: string
operatorId?: string
referralCode?: string
valuePence?: number
currency?: string
landingPage?: string
referrer?: string
metadata?: Record<string, unknown>
}
EventTypetype EventType =
| 'click' | 'lead' | 'sale' | 'signup' | 'embed_render'
| 'share' | 'qr_scan' | 'deep_link_open' | 'page_view'
| 'reward_redeemed' | 'points_earned' | 'referral_completed'
| Export | Type | Description |
|---|---|---|
BagdockAnalytics | class | Main SDK class |
parseUTM | function | Parse UTM parameters from a URL |
BagdockAnalyticsConfig | interface | Constructor config shape |
TrackableEvent | interface | Event payload shape |
EventType | type | Union of supported event type strings |
UTMParams | interface | UTM parameter shape |
| Option | Type | Default | Description |
|---|---|---|---|
apiKey | string | — | Required. Your Bagdock API key |
baseUrl | string | https://loyalty-api.bagdock.com | API base URL |
flushIntervalMs | number | 5000 | How often to flush queued events (ms) |
batchSize | number | 25 | Max events per flush batch |
dedupWindowMs | number | 500 | Window for dropping duplicate events (ms) |
autoPageView | boolean | false | Track a page view on init |
debug | boolean | false | Log SDK activity to the console |
Events queue in memory and flush on a timer or when the batch size fills. Duplicate events — defined as matching eventType, linkId, referralCode, and memberId — within the dedup window are dropped silently.
graph TD
A["track() called"] --> B{"Duplicate?"}
B -- Yes --> C["Drop"]
B -- No --> D["Add to queue"]
D --> E{"Queue full?"}
E -- Yes --> F["Flush"]
E -- No --> G["Wait for timer"]
G --> F
sessionStorage, scoped to the current tab. It is cleared when the tab closes.Authorization: Bearer headers over TLS.fetch and navigator.sendBeacon.MIT — see LICENSE.
FAQs
Bagdock Analytics SDK — lightweight client-side event tracking with batching and dedup
The npm package @bagdock/analytics receives a total of 9 weekly downloads. As such, @bagdock/analytics popularity was classified as not popular.
We found that @bagdock/analytics demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
RubyGems and Bundler 4.0.13 introduced an opt-in cooldown feature that delays newly published gems during dependency resolution.

Security News
pnpm 11.5 now recognizes npm staged publish approvals in release metadata, preventing those releases from being mistaken for lower-trust package publishes.

Security News
Federal audit finds NIST lacked a plan to clear the NVD backlog, wasted funds on duplicate work, and delayed use of CISA data.