Can I test Parse.ly on a staging/dev site?
You can; this is a common request from publishers. The best way to test Parse.ly on a staging/dev site is to reach out to your account representative to set up a separate staging dashboard. When you integrate Parse.ly tracking on your staging/dev site, make sure you set the apikey to the staging apikey associated with the staging dashboard. This will help avoid staging urls showing up in your production dashboard and API results. Additionally, articles can be tested before they are published on your live site using a staging dashboard.
Seeing posts in Dash associated with staging/development URLs is likely a result of Parse.ly tracking code on a staging/development site with the apikey set to your production site. If the tracking code is already integrated this way on your staging/development site but you would like to remove the staging/development post pages from Dash, please contact your account representative. They can help block the reception of pageview and heartbeat events from specific subdomains such as your staging/development site. After blocking the reception of additional events from your staging/development site, we will attempt to remove the posts associated with staging/development sites from our records, and then update the traffic data in Dash to reflect the changes.