Audience Segments offers a few different ways to segment your audience in the dashboard, isolating a subset of users while also maintaing a view for your entire readership. These segments are often created based on subscription plans, but can be based on any method you use to bucket your audience. also supports geographic segmentation.

With geographic segmentation, you can look at all visitors in New York, all visitors in Europe, etc. Geographic segmenting doesn't require any additional implementation work on your side; contact your account manager if you're interested in this feature.

With subscription plans or other ways of bucketing readers (such as whether they're logged in), there's a small implementation change required. Once you've made this change based on the guidance below, notify to enable the dashboard view or views.


Depending on your Parsely plan, segment tracking may result in additional charges. Contact for more information. Note that you can't send us personal information like names or email addresses.

To enable segmentation, you'll need to send Parsely additional information about the plan a user is subscribed to, or whatever other classifer you're using. Here's an example of updating the tracking code for a user that is subscribed to the "basic" plan:

(function(w) {
  w.PARSELY = {
    autotrack: false,
    onReady: function() {
        data: {
          plan: "basic"

<!-- START Include -->
<!-- ...insert the parsely tracker code here... -->
<!-- END Include -->


The segmentation code must be placed before your standard Parsely tracking snippet.

Notice in the snippet above that in the call to PARSELY.updateDefaults, we provide an object like so:

  data: {
    plan: <name of plan>

You must pass an object that matches this shape. The data.plan attribute can be any string that uniquely identifies the name of the plan, or whatever other quality you want to segment on. You could similarly pass an attribute like data.logged_in.

If the current user isn't subscribed to any plan, set data.plan to null or skip the call to PARSELY.updateDefaults.

Decide whether you need just one custom dashboard segment (e.g. "Paid Subscribers") or whether multiple are required. Generally, we don't recommend implementing more than a handful per account. Then, send an email to letting us know of your desired segments (e.g. all possible values of data.plan).

Do you have an urgent support question?