Content Analytics tables not populating data
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Content Analytics tables (sn_cda_analytics_visit_stat, sn_cda_page_stat,
sn_cda_tracked_page_agg, sn_cda_tracked_visit_agg) not populating despite
successful track_events API calls.
Steps performed:
1. Navigated ESC pages as authenticated user
2. Verified track_events calls in browser DevTools:
- POST /api/sn_cda/analytics/track_events
- Response: {"result":{"result":"success"}}
- Payload contains: profileId, userId, pageViews array with ESC URLs
3. Content Analytics Site Tracker widget is present in ESC header
4. Tracking profile "Content Publishing Profile" is Active=true, Default=true
5. Manually executed scheduled jobs:
- Content Publishing Profile (Profile Trigger)
- Content Analytics: Process Visits
6. Checked all CDA tables - all empty
7. sn_cda_analytics_log - completely empty
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Buddy,
If track_events shows success but all sn_cda_* tables — and especially sn_cda_analytics_log — are empty, the events arent making it into the Content Analytics processing pipeline.
That usually means to me one of three things:
The processing jobs arent actually running or are failing.
The tracking profile isnt properly tied to the ESC theme/header being used.
Content Analytics and its PA dependencies isn’t fully activated/configured.
A successful API call only means the browser sent the event — it doesn’t mean it was stored. The empty log table is the main clue the ingestion step isn’t happening.
@Naveen Bandaru - If help you answer; Please mark Solution Accepted and Thumbs Up.

