Repeated meta tags
Specifying metadata information on your webpages is the second step of integrating with Parse.ly. (Jump to documentation about installing the tracking code if you don't have the tracker running yet!)
You can provide metadata in two different ways:
- JSON-LD (recommended) - following open standards and schemas, metadata is included in a script tag. This metadata can also be used by other services (such as Google, for enhanced display in search listings).
- repeated metatags (alternative) - if the CMS you are using has a way to provide page information as meta tags in the page header, then this might be a more convenient option. Metadata specified this way will only be used by Parse.ly.
Add tags like these to the
<head> element of all tracked pages.
<meta name="parsely-title" content="Zipf's Law of the Internet: Explaining Online Behavior" /> <meta name="parsely-link" content="https://blog.parse.ly/post/57821746552" /> <meta name="parsely-type" content="post" /> <meta name="parsely-image-url" content="https://blog.parse.ly/inline_mra670hTvL1qz4rgp.png" /> <meta name="parsely-pub-date" content="2013-08-15T13:00:00Z" /> <meta name="parsely-section" content="Programming" /> <meta name="parsely-author" content="Alan Alexander Milne" /> <meta name="parsely-tags" content="statistics,zipf,internet,behavior" />
|parsely-title||Post or page title (article headline)|
|parsely-link||Canonical URL for post/page. For page groups like galleries, it should always point to the main article. For accurate data, the canonical urls for the social networks (link rel="canonical" and og:url) must match or resolve to this url. For more information, please refer to the documentation here.|
|parsely-image-url||URL of the image associated with the post/page.|
|parsely-type||Page type, which must be one of the following strings: |
|parsely-post-id||String that uniquely identifies this post. Unless otherwise instructed by Parse.ly support, should be omitted in favor of |
|parsely-pub-date||Publication date, as ISO 8601 UTC timezone string.|
|parsely-section||Section the page belongs to (e.g. "Politics"). Note that only 1 section value is supported. Therefore, it is recommended that the top-level section or category is used and any sub-sections or child categories are added to parsely-tags.|
|parsely-author||Author who wrote the post. This field can be repeated for each author in a multi-author post.|
|parsely-tags||String of comma-separated keywords associated with the post (e.g. "basketball, NBA, LeBron"). These will map to "Tags" in the Parse.ly dashboard. Note that up to 100 parsely-tags values are supported.|
|parsely-metadata||Arbitrary data to attach to post. Must be a valid JSON-serialized string. See documentation about custom metadata.|
Escape double quotes in JSON item values. Double quotes should
be escaped with a backslash symbol like this:
Values in the meta tags will appear literally inside Parse.ly Analytics. Remember that all metadata is case sensitive. String values supplied here (specifically parsely-title, parsley-author, and parsely-section) as well as list values (specifically parsely-tags) will appear in Parse.ly analytics exactly as they are specified in the tag. As a result, make sure to use proper capitalization and specify the values as you expect them to appear. Values with variations (example: "John Smith" and "john smith") will appear separately in the Dashboard causing duplication and skewed data.