parsely.com: Audience Data and Analytics for Digital Media Publishers

parsely.com: Audience Data and Analytics for Digital Media Publishers

The first part of the two step integration with Parse.ly tracking, is the installation of the tracking code. Jump to documentation about the metadata tag once you have the JavaScript running!

The Parse.ly Tracker is a small piece of JavaScript code that monitors user actions taken on your site and relays them to the Parse.ly analytics server.

To get started, insert the Parse.ly Tracker in the footer of your website template. Ideal placement is as the last code block before the closing of the body tag. If your website uses a templating system, this is usually in the “footer” template.

JavaScript implementation is the recommended way of tracking, but it is also possible to send the pixel data to the analytics server from your site’s serverside. This page describes and demonstrates how to format HTTP requests to send visitor data in such case.

To send visitor data, make a HTTP GET request to http://srv.pixel.parsely.com/plogger/. The request headers should contain User-Agent string that would be set to of the user device information (browser, version, etc.) initiating the action.

When using our JavaScript implementation, JavaScript implementation, you may need to be aware of privacy considerations surrounding Parse.ly’s data collection approach.

By default, Parse.ly collects standard web browser information about a reader, the uses of which are described below:

ip_address: IP address of the user; used for bot blocking and geo trends
user_agent: Identifier for the user’s device; used for device analytics (mobile vs desktop)
first_party_uuid: Site-specific identifier (UUID) for user; used in loyalty analytics (new vs returning)
third_party_uuid: Network unique identifier (UUID) for user; used in aggregate benchmarking
To comply with Personally Identifiable Information (PII) restrictions in certain geographic regions, as well as the privacy policies of individual publishers, Parse.ly can selectively disable the tracking of two of these pieces of information (individually for a specific site or API key). These are ip_address and third_party_uuid.

Disabling ip_address tracking will prevent Parse.ly from being able to do bot blocking for your site, but may lead to better compliance with strict privacy policies that consider IP addresses to be PII. Parse.ly also has plans to eventually incorporate geographic information in its dashboards, but blocking IP addresses will eliminate any possibility for this feature to be deployed for publishers on which ip_address tracking is disabled.

Disabling third_party_uuid will prevent Parse.ly from being able to do network-wide benchmarking for your site, but it will not disable any other functionality.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s