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.
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.
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.