What is sfnext-analytics-consent?

An analytics guide for a Storefront Next shop. It explains event tracking, connections to engagement services, consent checks, page-view tracking, and first-touch attribution, which records how a shopper first arrived.

Use it to configure Einstein, Active Data, or Data 360 adapters, add a custom adapter, track page views and shopper actions, and pass attribution data through the shop.

It keeps shopper events from being sent before the shopper has given the required consent and shows where the tracking code and settings belong. It also reduces confusion when adding or changing analytics services.

sfnext-analytics-consent — Skill by SalesforceCommerceCloud

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add SalesforceCommerceCloud/b2c-developer-tooling --skill sfnext-analytics-consent

Clone the repo

git clone --depth 1 https://github.com/SalesforceCommerceCloud/b2c-developer-tooling

Made for: Claude Code.

Or install storefront-next, the plugin that ships this one along with the rest of its 24 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-analytics-consent/github.svg)](https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-analytics-consent)

Your own site

<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-analytics-consent"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-analytics-consent/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-analytics-consent"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-analytics-consent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 179 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,506 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00179	$0.01506
Opus 5.5	$0.00072	$0.00602
Sonnet 5.5	$0.00036	$0.00301
Haiku 4.5	$0.00018	$0.00151

Measured 15d ago against content hash 8cb5f6ce591e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sfnext-analytics-consent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 15d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/storefront-next/skills/sfnext-analytics-consent/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Events flow: component -> useAnalytics() -> event mediator (@salesforce/storefront-next-runtime/events) -> each registered engagement adapter. Every adapter checks shopper consent before sending. Read docs/README-ADAPTER-PATTERN-GUIDE.md and docs/README-CONSENT-TRACKING.md in your project for the full guides; where they disagree with the code, trust the code (paths below were verified).

Where things live

Concern	Location
Adapter config	`engagement.adapters.*` in `config.server.ts`
Adapter types, store, `hasConsent`, `buildConsentPreferences`	`@/lib/adapters` (`src/lib/adapters/engagement/`)
Registration of built-in adapters	`src/lib/adapters/engagement/register.ts` (`initializeEngagementAdapters`)
Built-in adapters	`einstein.ts`, `active-data.ts`, `data360.ts` in the same folder
Page view tracking	`src/analytics/page-view-tracker.tsx` (`PageViewTracker`, mounted in `src/root.tsx`)
Event hooks	`@/hooks/use-analytics`, `@/hooks/use-tracking-consent`
Attribution	`src/lib/attribution.ts`, `@/hooks/use-attribution`, `src/middlewares/attribution-forwarding.server.ts`

Configure built-in adapters

// config.server.ts
engagement: {
  adapters: {
    einstein: { enabled: true, consentCategory: 'analytics', host, einsteinId, realm, siteId, isProduction: false,
                eventToggles: { view_page: true, view_product: true /* ... */ } },
    data360:  { enabled: true, consentCategory: 'analytics', appSourceId, tenantId, siteId, webStoreId: 'sfnext', eventToggles: { /* ... */ } },
    activeData: { enabled: true, /* see config.server.ts */ },
  },
  analytics: {
    trackingConsent: { enabled: true, defaultTrackingConsent: TrackingConsent.Declined,
                       consentCategories: ['necessary', 'analytics', 'marketing', 'personalization'] },
    pageViewsBlocklist: [/* paths that must not emit view_page */],
  },
}

The shipped IDs (einsteinId, realm, tenantId, ...) are sample values. Replace them with your own before go-live, or set enabled: false.
An adapter with consentCategory: 'analytics' sends nothing unless 'analytics' is in trackingConsent.consentCategories.
eventToggles turns individual event types on or off per adapter. Data 360 ships only view/impression events enabled.
The einstein and data360 adapter blocks, and activeData.enabled / activeData.eventToggles, are protected config paths and cannot be overridden with PUBLIC__ env vars; edit config.server.ts and rebuild. Other keys follow the PUBLIC__app__engagement__... pattern (see storefront-next:sfnext-configuration).

Read the full file on GitHub · 92 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

15d ago First seen · 92 lines · 179 tokens per session scan A 8cb5f6ce591e

Subscribe to this mod's changes

sfnext-analytics-consent is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed today), licensed Apache-2.0. It adds 179 tokens to every session and 1,506 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-05.

Analytics and metrics E-commerce b2c cli dx

shopping

Skill "shopping" from Hmbown/Codewhale, covering shopping, when to use, setup, workflow and non-goals.

Hmbown/Codewhale · 0 tokens

daiso-cli

A command-line interface for searching Daiso and related Korean shopping, store, food, cinema, and convenience-store data through the Daiso project. It can return structured JSON for searches and comparisons.

hmmhmmhm/daiso-mcp · 146 tokens

goofish-publish-item

A workflow for publishing second-hand items on Xianyu, a Chinese marketplace for used goods. It turns an item description and images into a category, title, listing text, and a ready-to-submit listing.

fancyboi999/goofish-cli · 151 tokens

goofish-reply-buyer

A Chinese-language workflow for handling buyer messages on Xianyu, a Chinese second-hand marketplace. It reviews conversations, classifies buyer intent, and drafts replies according to the seller’s rules, but waits for human approval before sending.

fancyboi999/goofish-cli · 160 tokens

goofish-shop-diagnosis

A read-only diagnostic workflow for Xianyu shops and listings. It compares how a shop’s items appear in marketplace search with their stored details to investigate visibility and sales problems.

fancyboi999/goofish-cli · 149 tokens

booking-cli

Searches Booking.com from the terminal via cli-web-booking — find hotels, apartments, and hostels by destination, dates, and guests; get property details by slug; resolve destination names to IDs. Use when the user asks about Booking.com, hotel search, accommodation prices, property ratings, or comparing places to…

ItamarZand88/CLI-Anything-WEB · 80 tokens