The Parse.ly plugin real-time and historical analytics to your content through a platform designed and built for digital publishing.
Designed and built for digital publishers, Parse.ly helps you understand how your audience is connecting to your content.
Thousands of writers, editors, site managers, and technologists already use Parse.ly to understand what content draws in website visitors, and why. Using our powerful dashboards and APIs, customers build successful digital strategies that allow them to grow and engage a loyal audience.
Join industry leaders -- like Mashable, Slate, News Corp, and Conde Nast -- who already use Parse.ly to bring clarity to content, audience, and analytics.
Features
- Get started with Parse.ly right away: the plugin automatically inserts the required parsely-page tag and JavaScript on all your published pages and posts.
- Allows you to specify the JavaScript implementation to use: standard, DOM free or asynchronous.
Feedback, suggestions, questions or concerns? E-mail us at [email protected] we always want to hear from you.
- This plug-in requires an active version of Parse.ly. We offer a free trial, sign up here
- If you haven't already done so, sign up for a trial of Parse.ly
- Download the plugin
- Upload the entire
wp-parsely
folder to your/wp-content/plugins
directory - Activate the plugin through the 'Plugins' menu in WordPress (look for "Parse.ly")
- Head to the settings page for the plugin (should be /wp-admin/options-general.php?page=parsely)
- Set your Site ID, which is your own site domain name (e.g.,
mysite.com
) - Save your changes and enjoy your data!
NOTE: This plugin does not currently support dynamic tracking (the tracking of multiple pageviews on a single page). Some common use-cases for dynamic tracking are slideshows or articles loaded via AJAX calls in single-page applications -- situations in which new content is loaded without a full page refresh. Tracking these events requires manually implementing additional JavaScript above the standard Parse.ly include that the plugin injects into your page source. Please consult the Parse.ly documentation on dynamic tracking for instructions on implementing dynamic tracking, or contact Parse.ly support for additional assistance.
Feedback, suggestions, questions or concerns? E-mail us at [email protected] -- we always want to hear from you.
- Follow the steps to install VirtualBox, Vagrant and
vagrant-hostsupdater
at http://vccw.cc/. - Navigate to the directory on your host machine to which you downloaded vccw.
- Within that directory, navigate to
www/wordpress/wp-content/plugins
and clone this repo --git clone https://github.com/Parsely/wp-parsely.git
- Checkout the branch on which you've been working
- Navigate back up to the root of the
vccw
directory and runvagrant up
- Ssh into the Vagrant machine with
vagrant ssh
- Navigate to
/var/www/wordpress/wp-content/plugins/wp-parsely
and run the test suite with the commandphpunit
Your Site ID is your own site domain name (e.g., mysite.com
).
Dash code will only be placed on pages and posts which have been published in WordPress to ensure we don't track traffic generated while you're still writing a post/page.
You can use the after_set_parsely_page
filter, which sends three arguments: the array of metadata, the post object, and the parselyOptions
array:
$parselyPage = apply_filters('after_set_parsely_page', $parselyPage, $post, $parselyOptions);
This filter can go anywhere in your codebase, provided it always gets loaded. We recommend putting it in your header file, so that it gets loaded with wp_head.
It is! We are hooked into Automattic's official plugins for AMP and Facebook Instant. AMP support is enabled automatically if the Automattic AMP plugin is installed, and for Facebook Instant you just have to enable "Parsely Analytics" in the "Advanced Settings" menu of the Facebook Instant Articles plugin.
Official AMP plugin: https://wordpress.org/plugins/amp/
Official FB Instant plugin: https://wordpress.org/plugins/fb-instant-articles/
See the wiki.
- Adds ability to filter final JSON-LD output
- Adds the ability to use a custom taxonomy as tags
- Adds AMP / Facebook Instant integration with official AMP / FBIA plugins from Automattic
- Fixes bug related to HTTPS canonicals
- Ability to assign custom taxonomies as section
- Bug fix related to adding section to tag field
- Updated documentation for installation and local development
- Allow developers to adjust the tag list and the category reported for a post
- Added support for themes to extend the reported authors
- Use JSON-LD / schema.org for parsely-page data instead of proprietary format
- Added support for multiple authors if using the Co-Authors Plus plugin https://wordpress.org/plugins/co-authors-plus/
- Maintenance release with multiple changes needed for WordPress VIP inclusion
- Migrated to WP Settings API
- Various syntax changes in line with Automattic's guidelines
- Removed the tracker_implementation option, plugin now uses Standard implementation for all installs
- Updated much of the copy in settings page
- Updated screenshots
- Added support for new option - "Use Categories as Tags"
- Fixed bug that caused wp-admin bar to be hidden when "Do not track authenticated in users" was selected
- Fixed WP category logic bug that failed on users with custom post types
- Added early support for post tags
- Fixed permalink errors on category/author/tag pages
- Added version output to both templates and settings pages
- Renamed API key to Site ID to avoid confusion
- Added option to not track or not track authenticated users (default is to not track authenticated users)
- Removed async implementation option
- Updated API key retrieval instructions
- Added activation/deactivation hooks
- null categories are now set to "Uncategorized"
- Support for using top-level categories for posts instead of the first active post the plugin finds
- parsely-page meta tag now outputs it's value using 'content' attribute instead of 'value'
- Minor fixes to outputting to use proper WordPress functions
- Added ability to add prefix to content IDs
- Ensured plugin only uses long tags
<?php
instead of<?
- Security updates to prevent HTML/JavaScript injection attacks (values are now sanitized)
- Better error checking of values for API key / implementation method
- Bug fixes
- Initial version
- Support for parsely-page and JavaScript on home page and published pages and posts as well as archive pages (date/author/category/tag)