Sawir Insights is behavioral analytics for WordPress: heatmaps, session recordings, surveys, a feedback widget, form analytics, conversion funnels, and a dashboard that ties them together.<\/p>\n\n
On multisite networks, each site tracks and configures its analytics independently.<\/p>\n\n
The reason it exists is simple. The established tools in this category are good, but they work by shipping a record of everything your visitors do to someone else's servers. For a lot of sites \u2014 especially in the EU \u2014 that is somewhere between uncomfortable and unworkable. I wanted the same class of tooling where the data never leaves the site that collected it. So that is the constraint this plugin is built around: your database, your uploads directory, your retention rules. There is no SaaS behind it, no account to create, and no phone-home of any kind.<\/p>\n\n
What it does<\/strong><\/p>\n\n What it deliberately does not do<\/strong><\/p>\n\n I think you should know what a tool refuses to do before you install it.<\/p>\n\n The frontend tracker is small vanilla JavaScript, batched over Privacy posture<\/strong><\/p>\n\n Do Not Track is honored by default. A consent-mode API ( Support<\/strong><\/p>\n\n Support runs through the wordpress.org forum for this plugin, or email ricardo@sawirstudio.com.<\/p>\n\n If Sawir Insights fits how you like tools to work, I make a few others in the same spirit:<\/p>\n\n The plugin is built for privacy-conscious deployments: data stays on your server, IP addresses are never stored, retention is configurable, Do Not Track is honored, and WordPress export\/erasure tools are integrated. Compliance itself depends on your configuration, notices, legal basis, and consent implementation \u2014 consult qualified counsel for your site.<\/p><\/dd>\n No. The plugin sends no behavioral data to Sawir Studio or any analytics provider. Events live in your WordPress database; recording files live beneath your protected uploads directory.<\/p><\/dd>\n Yes. I keep this as a wp-config.php-only setting so database credentials never enter the WordPress options table. Define all four constants before the \"That's all, stop editing\" line:<\/p>\n\n The analytics tables keep the main site's table prefix, so moving between the WordPress database and an external database is a plain table copy. Do not run two live collecting databases for one site: copy the tables, switch the constants, and only then resume collection. Otherwise you will split one site's history across two databases.<\/p><\/dd>\n No.<\/p><\/dd>\n Enable \"Require consent before tracking,\" then call No. Form capture records selectors, timing, and empty-state metadata only. Values never leave the browser.<\/p><\/dd>\n Recording is disabled by default. When enabled, all input values are masked automatically, canvas capture is off, and replay chunks stay beneath the guarded Add the Insights \u2192 Settings has separate recording retention and disk-cap controls. Past the cap, the oldest recordings are removed first. Usage is tracked continuously and recalculated weekly.<\/p><\/dd>\n Each active survey can target URL patterns, devices, a stable percentage of sessions, time on page, scroll depth, or desktop exit intent. One survey per browser session; dismissed surveys stay hidden for 30 days.<\/p><\/dd>\n Funnels are computed from ordered page-view and click metadata retained on your server, so history is bounded by the raw-event retention window in Insights \u2192 Settings.<\/p><\/dd>\n I fold raw events into heatmap aggregates hourly through WP-Cron. WordPress only runs WP-Cron when someone visits the site, so on a low-traffic site I recommend a real system cron, for example: \n
\n
sendBeacon<\/code>, with sampling controls. Visitors who are not sampled into recording never download the replay library at all.<\/p>\n\nwindow.swinsConsent<\/code>) integrates with whatever consent manager you already run. Sessions, events, and recordings are wired into WordPress's own personal-data export and erasure tools. Whether your specific deployment is GDPR compliant depends on your notices and legal basis \u2014 that part no plugin can do for you \u2014 but the data-minimization work is done.<\/p>\n\nOther plugins by Sawir Studio<\/h3>\n\n
\n
\n
sawir-insights<\/code> directory to \/wp-content\/plugins\/<\/code>, or install through the Plugins screen.<\/li>\n\n
Is Sawir Insights GDPR compliant?<\/h3><\/dt>\n
Does visitor data leave my server?<\/h3><\/dt>\n
Can analytics data live in its own database?<\/h3><\/dt>\n
define( 'SWINS_DB_HOST', 'localhost' );\ndefine( 'SWINS_DB_NAME', 'analytics' );\ndefine( 'SWINS_DB_USER', 'analytics_user' );\ndefine( 'SWINS_DB_PASSWORD', 'a-strong-password' );\n<\/code><\/pre>\n\nDoes it store IP addresses?<\/h3><\/dt>\n
How do I connect a consent manager?<\/h3><\/dt>\n
window.swinsConsent('grant')<\/code> when consent is granted and window.swinsConsent('revoke')<\/code> when it is withdrawn. The decision is saved in a first-party cookie.<\/p><\/dd>\nAre form values captured?<\/h3><\/dt>\n
How are session recordings protected?<\/h3><\/dt>\n
wp-content\/uploads\/sawir-insights\/recordings\/<\/code> directory. Only administrators can retrieve them, through an authenticated REST endpoint.<\/p><\/dd>\nHow do I mask or block sensitive page areas?<\/h3><\/dt>\n
swins-mask<\/code> class or data-swins-mask<\/code> attribute to mask an element's text. Add the swins-block<\/code> class to omit an element entirely from recordings.<\/p><\/dd>\nHow is recording disk usage controlled?<\/h3><\/dt>\n
How do surveys decide when to appear?<\/h3><\/dt>\n
How complete are funnel reports?<\/h3><\/dt>\n
Why do heatmaps lag behind live traffic?<\/h3><\/dt>\n
*\/5 * * * * cd \/path\/to\/wordpress && wp cron event run --due-now<\/code><\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n
\n