About this plugin
CauseWise Analytics adds the hosted CauseWise tracker to public WordPress pages and shows analytics in wp-admin.
io, or paste the tracking snippet from the CauseWise dashboard. The plugin reads data-site from a snippet and stores only that public key. js through WordPress.
The pasted snippet is not saved and is not added to the page. Do not also paste the snippet into the theme, or the page will send two page views.
Dashboard → Home shows a CauseWise Stats widget in the main column: a traffic chart, page views, unique sessions, Today / 7 Days / 30 Days, and Top Pages / Referrers. Four smaller widgets for page views, sessions, traffic, and top pages stay available in Screen Options. Show, hide, drag, and collapse them with the normal Dashboard controls.
Configure sets the date range for a smaller widget. Each widget links to the CauseWise Analytics screen.
The CauseWise Analytics screen shows overview counts, the traffic chart, top pages, referrers, sessions, goals, funnels, and recent events for today, the last 7 days, or the last 30 days. A navigation bar at the top jumps to each section on that same screen. Recent events load separately from the charts.
Each row shows the event name, type, time, and page path. The list can be filtered, paged, and refreshed without reloading WordPress. It reads the CauseWise API.
It does not calculate a second set of metrics. 2. txt.
The same charts can be placed on a page with a CauseWise block or a shortcode. Analytics Overview, Traffic Chart, Top Pages, Referrers, Goals, and Recent Events are in the CauseWise block category. The shortcodes are [causewise_stats], [causewise_traffic], [causewise_top_pages], [causewise_referrers], [causewise_goals], and [causewise_events].
Each accepts range ( today, 7d, or 30d ), an optional title, and theme ( light, dark, or system ). Top Pages, Referrers, and Recent Events also accept limit from 1 to 20. The default range is 7d.
CauseWise Dashboard, shortcode [causewise_dashboard], shows those sections together with goals and funnels. It has one date range, one theme, an optional title, and a link to advanced analytics. show_stats, show_traffic, show_pages, show_referrers, show_goals, show_funnels, and show_events can be 0 to hide a section.
The block uses the theme alignment controls: default, wide, and full width. It can sit inside a Group, Row, Columns, or Cover block. Width in the inspector can also be a custom maximum in pixels.
The shortcode accepts width="1100px", width="100%", width="wide", or width="full". A custom width uses width: 100% and that maximum, so it stays inside its parent. Panels follow the dashboard’s own width: one column when narrow, two when medium, and three overview cards when wide.
The traffic chart is a bar chart. Dates on that chart use a short label such as Oct 20. Top Pages omits invitation tokens and other secrets from the path.
The page still shows a sign-in message, and the numbers are not saved in the post. The dashboard heading is CauseWise Analytics unless a title is set. 0, shows CauseWise Analytics instead.
A title you wrote is kept, even if it includes a number. The installed plugin version is not shown on the dashboard. An authorized viewer can choose Customize layout to drag panels by a handle, resize them from either edge to one third, half, two thirds, or full width, and move or resize the focused handle with the arrow keys.
A small hide control and Restore panels are available while editing. Reset layout returns the author’s sections. Those choices are saved in that viewer’s WordPress account for that dashboard, so the same layout is there when they sign in from another browser or device.
A shortcode can set instance so two dashboards stay separate. The saved layout does not include analytics numbers. If WordPress cannot be reached, the browser keeps a temporary copy.
A section the page author turned off stays hidden.
A page shows a sign-in message to everyone else. The numbers load in the browser only after WordPress confirms the viewer can activate plugins, through the same private analytics route the Dashboard uses. They are not saved in the post, the block, or the shortcode.
Event properties are not shown. The management API key stays on the server. Page caches are asked not to store the response when that viewer is signed in.
A management API key is required for that screen. Create one in CauseWise under Settings → API keys. Leave the site ID blank when the key belongs to one site; enter the site ID when it can see more than one.
The key is stored in WordPress and is sent only from the server to CauseWise. It is not added to the tracker and it is not included in the admin page.
Select a Button or Buttons block and open the CauseWise panel to record clicks without writing JavaScript. Turn on Enable event tracking, choose an event name such as button_click, and add optional properties such as location = hero. track on the CauseWise script already on the page.
The plugin does not add a second analytics backend. Page views stay automatic. Do not name a click pageview.
The panel explains what is sent. CauseWise records the event name, the properties you type, and the page address the tracker already includes. It does not read the button text, the link address, or anything typed into a form.
Property names that look like emails, passwords, tokens, or other personal data are not saved. If the CauseWise script is missing, the button still works and nothing is sent.
A Buttons block and a Button inside it can both be configured. The click is sent once, for the button. A second copy of the click listener does not send a second event.
The choice is stored with the block. The button’s saved HTML is unchanged, so existing buttons stay valid. Data attributes are added when the page is rendered.
Other blocks, classic HTML buttons, and form submissions are not tracked.
com installations that do not grant manage_options. The block panel uses the WordPress block editor filters and does not require manage_options.
The readable plugin source is in src/. The chart component source shipped with this plugin is in src/causewise-react/. 4 is the MIT-licensed library compiled into the admin and embed scripts.
txt. 0 draws the dashboard editor. txt.
js.
External service and privacy
io, an external service operated by RazorSoft, Inc. Nothing is sent until an administrator saves a public site key and turns tracking on. The plugin does not phone home on activation.
- Public pages then load https://causewise.io/causewise.js in the visitor’s browser. That script sends the page address, path, title, referrer, time, a random visitor id, a session id, and the browser user agent to https://causewise.io/api/collect. It does not send the management API key. wp-admin is not tracked. A public page is tracked only after tracking is enabled.
- A Button or Buttons block with event tracking sends one custom event through that same script. The event includes the name and properties saved on the block, plus the page address the tracker already sends. It does not read the button text, the link address, or form fields. Property names that look like emails, passwords, tokens, or other personal data are not saved.
- Analytics screens, Dashboard widgets, blocks, and shortcodes send the management API key from the WordPress server to https://causewise.io/api/v1. The browser does not receive the key. The numbers are not saved in the post. Visitors who cannot manage CauseWise see a sign-in message and do not receive the analytics script.
- The plugin stores the public site key, the tracking switch, and the management API key in WordPress options. It does not send WordPress user accounts, comments, or post content to CauseWise.
- Uninstall deletes those options. It does not delete pages or the CauseWise account. Deactivation leaves the options in place.
- CauseWise has free and paid plans. Every feature in this plugin is included in the plugin. Plan limits are enforced by the CauseWise service, not by locked plugin code.
- Privacy statement: https://causewise.io/#privacy
- Service: https://causewise.io