community-analytics-data
Use when analyzing Experience Cloud site analytics including login metrics, member engagement, page view tracking, and content performance. Triggers: Experience Cloud site analytics, community member engagement data, portal login tracking, page view reports community, GA4 Experience Cloud integration. NOT for CRM Analytics or Tableau CRM. NOT for internal Salesforce reporting on standard CRM objects.
Best use case
community-analytics-data is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when analyzing Experience Cloud site analytics including login metrics, member engagement, page view tracking, and content performance. Triggers: Experience Cloud site analytics, community member engagement data, portal login tracking, page view reports community, GA4 Experience Cloud integration. NOT for CRM Analytics or Tableau CRM. NOT for internal Salesforce reporting on standard CRM objects.
Teams using community-analytics-data should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/community-analytics-data/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How community-analytics-data Compares
| Feature / Agent | community-analytics-data | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when analyzing Experience Cloud site analytics including login metrics, member engagement, page view tracking, and content performance. Triggers: Experience Cloud site analytics, community member engagement data, portal login tracking, page view reports community, GA4 Experience Cloud integration. NOT for CRM Analytics or Tableau CRM. NOT for internal Salesforce reporting on standard CRM objects.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# Community Analytics Data Use this skill when a practitioner needs to understand, report on, or configure analytics for an Experience Cloud site — covering login activity, member engagement, page views, and content performance. It does not apply to CRM Analytics (Einstein Analytics), Tableau CRM, or standard internal Salesforce reporting. --- ## Before Starting Gather this context before working on anything in this domain: - Confirm the user has a licensed Experience Cloud site (Customer Community, Partner Community, or LWR-based site) and has System Administrator or delegated Network Admin access. - The most common wrong assumption: practitioners expect real-time data. Engagement Insights dashboards have up to a 24-hour data lag and cannot be customized. - NetworkActivityAudit records are retained on a rolling 12-month basis — data older than 12 months is permanently deleted. Plan archival if historical trend reporting beyond one year is needed. - GA4 integration requires republishing the site after adding or changing the Measurement ID; it does not take effect on cached pages until publish. --- ## Core Concepts ### Engagement Insights: Built-In Administration Dashboards Experience Cloud provides read-only Engagement Insights dashboards accessible from the site's Administration panel under **Administration > Insights**. These dashboards show login activity, unique logins, page views, new member growth, and top-performing pages. They are pre-built, non-customizable, and reflect data with up to 24 hours of lag. They are appropriate for quick executive snapshots but cannot be filtered by segment, time-sliced below the day level, or embedded outside the Administration panel. ### NetworkActivityAudit and NetworkUserHistoryMonthly Objects For custom reporting, Salesforce exposes two key objects: - **NetworkActivityAudit** — records individual page view and login events per member per site. Each row captures the Network (site), member, action type, and timestamp. Retention is a rolling 12 months; records older than 12 months are deleted by the platform with no warning. - **NetworkUserHistoryMonthly** — aggregated monthly rollup of user activity per Network. Useful for long-term trend reporting without incurring the per-row volume of NetworkActivityAudit. Retention behavior follows standard org data limits; check your org's storage and confirm with Salesforce documentation for your edition. Custom report types built on these objects allow standard Reports and Dashboards to surface community activity data alongside CRM records (e.g., contact, case, account). ### GA4 Integration via Measurement ID Experience Cloud sites support Google Analytics 4 integration natively. Enter a GA4 Measurement ID (format: `G-XXXXXXXXXX`) in **Administration > Advanced > Google Analytics** for the site. Salesforce injects the `gtag.js` snippet on every page of the site automatically — no manual code change is required. This enables GA4 event tracking, funnel analysis, audience segmentation, and conversion measurement that complements Salesforce-native metrics. Important: the site must be republished after adding or updating the Measurement ID for the change to take effect on all pages. ### Content Performance via Page-Level Analytics Page view data in NetworkActivityAudit and GA4 can be used to assess content performance — which knowledge articles, product pages, or community discussion threads drive the most engagement or deflect the most cases. GA4 provides richer behavioral metrics (bounce rate, session duration, scroll depth) while native reports confirm which authenticated members are viewing which pages. --- ## Common Patterns ### Pattern 1: Custom Report for Daily Active Users Per Site **When to use:** When the business needs to track daily or monthly active user counts for an Experience Cloud site beyond what the read-only Engagement Insights panel shows — especially when filtering by user segment, license type, or combining with CRM data. **How it works:** 1. Create a Custom Report Type with **Networks** as the primary object and **Network Activity Audits** as a related object. 2. Build a report using this type, grouped by **Network Name** and **Activity Date**. 3. Add a count of unique Members (distinct login records) to measure daily active users. 4. Add filters for Action = `Login` to isolate authentication events, or `Page View` for content engagement. 5. Schedule the report to run daily and deliver to a dashboard or via subscription. **Why not the alternative:** The built-in Engagement Insights dashboards cannot be exported, scheduled, or filtered by user segment. A custom report gives scheduling, sharing, and drill-down capability. ### Pattern 2: GA4 Funnel Tracking for Self-Service Case Deflection **When to use:** When the business wants to measure whether Experience Cloud content (knowledge articles, FAQ pages, community answers) is reducing support case volume — a common ROI metric for self-service portals. **How it works:** 1. In GA4, define a funnel exploration starting at a known entry point (e.g., search results page or support landing page) through knowledge article views, and ending at the "Contact Support" or "Create Case" page. 2. The GA4 Measurement ID must already be configured in site Administration and the site republished. 3. Cross-reference GA4 funnel drop-off rate (users who viewed an article but did not reach the case creation page) with case volume from standard Salesforce Case reports. 4. High funnel abandonment before the case page, combined with stable or declining case volume, indicates successful deflection. **Why not the alternative:** NetworkActivityAudit does not capture session-level behavioral flow or conversion events. GA4 is the appropriate tool for multi-step funnel and conversion analysis. --- ## Decision Guidance | Situation | Recommended Approach | Reason | |---|---|---| | Quick executive dashboard — logins, page views, member growth | Engagement Insights (Administration > Insights) | Read-only, zero setup, sufficient for snapshots | | Filtered or scheduled active-user reporting against CRM data | Custom report on NetworkActivityAudit via Custom Report Type | Flexible, combinable with Contact/Account/Case data | | Session behavior, funnel analysis, bounce rate, conversion tracking | GA4 integration (Measurement ID in site settings) | GA4 captures behavioral session data Salesforce does not natively expose | | Long-term (>12 months) trend reporting on user activity | NetworkUserHistoryMonthly + archival strategy | NetworkActivityAudit is purged at 12 months; monthly aggregates extend the usable window | | Deep segmentation analytics, machine learning on engagement data | Export to external data warehouse (e.g., via Data Export or Salesforce Connect) | Platform-native tools lack ML/segmentation capabilities at this depth | --- ## Recommended Workflow Step-by-step instructions for an AI agent or practitioner configuring or reporting on Experience Cloud analytics: 1. **Clarify requirements** — Determine whether the request is for built-in snapshots (Engagement Insights), custom Salesforce reports (NetworkActivityAudit/NetworkUserHistoryMonthly), external analytics (GA4), or a combination. Confirm data retention requirements: if historical data beyond 12 months is needed, plan archival before NetworkActivityAudit records age out. 2. **Check existing site configuration** — Verify the Experience Cloud site is active and the user has Administration panel access. For GA4, confirm whether a Measurement ID is already configured under **Administration > Advanced > Google Analytics**. 3. **Configure native analytics access** — For Engagement Insights, navigate to **Administration > Insights** and verify the dashboards are populating (allow up to 24 hours for initial data). For custom reports, build a Custom Report Type on Networks + Network Activity Audits (or Network User History Monthly for aggregates). 4. **Configure GA4 integration if required** — Enter the GA4 Measurement ID (`G-XXXXXXXXXX`) in **Administration > Advanced > Google Analytics**, then republish the site. Validate that `gtag.js` is firing on site pages using browser developer tools or the GA4 DebugView. 5. **Validate and document data coverage** — Confirm which metrics are covered by each surface. Document the 12-month retention limit for NetworkActivityAudit in the project's data governance notes and set a reminder or automated export if historical data must be preserved. --- ## Review Checklist Run through these before marking work in this area complete: - [ ] Engagement Insights dashboards are accessible and showing data (or documented as intentionally unused) - [ ] Custom report types reference the correct object relationships (Network > NetworkActivityAudit or NetworkUserHistoryMonthly) - [ ] GA4 Measurement ID is entered and site has been republished if GA4 integration is in scope - [ ] Data retention limit (rolling 12 months for NetworkActivityAudit) is documented in project notes - [ ] 24-hour data lag in Engagement Insights is communicated to stakeholders expecting real-time data - [ ] No custom report or dashboard is being positioned as a substitute for CRM Analytics unless explicitly out of scope --- ## Salesforce-Specific Gotchas Non-obvious platform behaviors that cause real production problems: 1. **NetworkActivityAudit rolling 12-month retention** — Salesforce automatically deletes NetworkActivityAudit records older than 12 months with no notification. Organizations that delay building reporting infrastructure risk permanently losing historical engagement data. Export to an external system or use NetworkUserHistoryMonthly for longer retention before the window closes. 2. **Engagement Insights 24-hour data lag** — Data in the built-in Engagement Insights dashboards (Administration > Insights) can be up to 24 hours behind real-time. Practitioners who build stakeholder dashboards on Engagement Insights without disclosing this lag will face credibility issues when the data does not match same-day expectations. 3. **GA4 Measurement ID requires site republish** — Adding or changing the GA4 Measurement ID in site Administration does not take effect until the site is republished. Cached pages continue to use the old (or no) tracking snippet until publish. Validate tracking with GA4 DebugView after every Measurement ID change. 4. **Built-in dashboards are read-only and non-embeddable** — Engagement Insights dashboards cannot be customized, filtered, cloned, exported, or embedded in Lightning pages or external portals. Practitioners who promise stakeholders a customized engagement dashboard must use Custom Report Types and standard Reports/Dashboards instead. --- ## Output Artifacts | Artifact | Description | |---|---| | Engagement Insights configuration notes | Documented state of built-in dashboards and any known data lag for stakeholder communication | | Custom report type setup | Report type on Networks + NetworkActivityAudit or NetworkUserHistoryMonthly with recommended groupings and filters | | GA4 integration checklist | Measurement ID entry, publish confirmation, and DebugView validation steps | | Data retention and archival plan | Documents the 12-month NetworkActivityAudit window and export or archival cadence if historical data is required | --- ## Related Skills - admin/einstein-analytics-basics — Use when the requirement is for CRM Analytics (Einstein Analytics / Tableau CRM) rather than native Experience Cloud site analytics - data/report-performance-tuning (if present) — Use when custom reports on NetworkActivityAudit are hitting query limits due to high row volume
Related Skills
sandbox-data-masking
Use this skill when configuring or reviewing Salesforce Data Mask to protect PII/PHI in partial or full copy sandboxes after a refresh. Trigger keywords: data mask, sandbox masking, PII in sandbox, GDPR sandbox, HIPAA non-production, mask contacts, obfuscate fields non-production. NOT for sandbox refresh mechanics (use sandbox-refresh-and-templates), NOT for production data anonymization, NOT for Shield Platform Encryption at rest.
gdpr-data-privacy
Use this skill when implementing GDPR or CCPA data privacy controls in Salesforce: Individual sObject linkage, consent tracking, Right to Be Forgotten (RTBF) requests, data subject request handling, and Privacy Center configuration. Trigger keywords: GDPR, data privacy, consent management, right to erasure, Individual object, ContactPointConsent, ShouldForget, data subject request, Privacy Center, data portability. NOT for general data quality cleanup, duplicate management, field-level encryption (see platform-encryption skill), or sandbox data masking (see sandbox-data-masking skill).
data-classification-labels
Classify Salesforce fields by data sensitivity and compliance category using the four built-in classification attributes (SecurityClassification, ComplianceGroup, BusinessOwnerId, BusinessStatus). Covers Metadata API deployment, Tooling API querying, and Einstein Data Detect recommendations. NOT for data masking, Shield Platform Encryption, or runtime access control enforcement.
customer-data-request-workflow
Implement GDPR/CCPA data subject rights (access, deletion, rectification) using Salesforce Privacy Center and/or custom workflow. NOT for general backup or org-level data retention policy.
omnistudio-deployment-datapacks
Use when exporting, importing, or version-controlling OmniStudio components using DataPacks via the OmniStudio DataPacks tool or vlocity CLI. Covers DataPack export/import, Git version control integration, CI/CD for OmniStudio. NOT for SFDX-based metadata deployment of non-OmniStudio components.
omnistudio-asynchronous-data-operations
Use Integration Procedures queues, DataRaptor Chain, and Remote Actions with async patterns for long-running OmniStudio flows. NOT for simple DataRaptor reads.
dataraptor-transform-optimization
Use when DataRaptor Transform operations are slow, hit governor limits, or use Apex where formula fields would suffice. Covers formula vs Apex expressions, bulk transform sizing, and chained transform composition. Triggers: 'dataraptor transform slow', 'dataraptor formula vs apex', 'dataraptor bulk transform', 'dr governor limit'. NOT for DataRaptor Extract or Load performance.
dataraptor-patterns
Use when designing or reviewing OmniStudio DataRaptors, especially Extract versus Turbo Extract versus Transform versus Load, field mapping strategy, performance tradeoffs, and when to move work into Integration Procedures or Apex. Triggers: 'DataRaptor Extract', 'Turbo Extract', 'DataRaptor Load', 'DataRaptor Transform', 'OmniStudio data mapping'. NOT for overall OmniScript journey design or Integration Procedure sequencing when the main question is not the DataRaptor shape itself.
lwc-datatable-advanced
Advanced lightning-datatable patterns — inline edit + draftValues, custom cell types via extending LightningDatatable, sortable columns, infinite scroll with onloadmore, row-level errors, and the cost of large data sets. NOT for read-only display of small lists (plain lightning-datatable suffices) or fully custom grids (use a third-party library).
lwc-data-table
Use when designing or reviewing `lightning-datatable` usage in Lightning Web Components, including column configuration, stable `key-field` values, inline editing, row actions, infinite loading, and custom cell types. Triggers: 'lightning datatable inline edit', 'row actions in lwc datatable', 'key field missing', 'infinite loading in datatable'. NOT for highly custom virtualized grids or broad page-performance work outside the datatable boundary.
lwc-custom-datatable-types
Use when you need to extend `lightning-datatable` with custom cell renderings: status pills, progress bars, image thumbnails, action cells, editable pickliststo, rich-text, or any column that `lightning-datatable` does not ship out of the box. Triggers: 'custom cell type lightning datatable', 'progress bar column', 'image column', 'inline edit picklist in datatable', 'rich text column'. NOT for basic datatable usage (see `lwc-data-table`) and NOT for tree-grid or large-dataset virtualization (see `virtualized-lists`).
salesforce-data-pipeline-etl
Export large Salesforce datasets to a lakehouse via Bulk API 2.0, CDC streams, or Salesforce Data Pipelines. NOT for ad-hoc exports.