#What is the integration checklist for new customers?
Every new Parse.ly integration starts with the same first two steps:
- Include our basic tracker on all pages of your site.
- Include metadata in one of our recognized formats on all pages of your site.
If your site is a single page application (SPA), or otherwise has dynamically loaded content, you may need to configure single-page application tracking to utilize the automatic pageviews of the SPA specific tracker.
We're happy to provide a testing site ID and dashboard if you're not ready to experiment on your production site. Contact firstname.lastname@example.org to get one set up.
In most cases, customers are able to accomplish both steps quickly and without hassle. However, if you do run into trouble, we recommend the following:
- Use our Validator tool to check both that both the tracker and metadata are correct for a particular URL.
- For tracking issues, use our integration troubleshooting guide to help find the most relevant technical documentation.
- For metadata issues, read about how to avoid the most common metadata mistakes.
- Log into Parse.ly at http://dash.parsely.com/<your site ID>/ and see how the data is being received.
Additional integration steps for Enterprise customers
If you're a Starter or Growth tier customer interested in any of the following steps, please contact email@example.com about upgrading your account.
While the above two steps will provide you with a fully functional analytics dashboard, there are a number of further steps you may want to take to enhance a basic integration, depending on your needs.
Collecting data from other platforms
- Configure tracking for Facebook Instant or Google AMP.
- Configure tracking for your Android and iOS apps.
Collecting video/audio data from embedded players
- If you use a supported player, read the specific documentation to see if any additional scripts or configuration is necessary for Parse.ly to automatically detect video events.
- Otherwise, define a strategy for the Parse.ly tracker to discover and detect video events.
Customizing data collection
- Modify your tracking integration to define custom audience segments.
- Provide custom metadata (for use with the Parse.ly API or Data Pipeline)
Configuring other tools
- Modify your homepage markup to track slot performance via the Overlay bookmarklet.
- Get started with the Parse.ly API.
- Get started with the Parse.ly Data Pipeline.
- Schedule a staff training session with your account manager.
- Invite your colleagues to create Parse.ly logins from dash.parsely.com/<your site ID>/settings/users
#How do I integrate Parse.ly?
Getting set up with Parse.ly is generally an easy and painless process. The integration is done by a member of your tech team, a developer for your site, or anyone who manages your CMS for that matter.
If you're the person responsible for this process, consult our comprehensive integration checklist and make sure you've completed every step before you get up and running.
1. Sign up for a trial and obtain a Site ID.
- Kick things off on our Signup Page to start a trial or contact your account manager.
2. Dropping two bits of code into your CMS (or alternatively using our Wordpress plugin).
3. Verifying the above mentioned code snippets are properly added to your site.
- Using our Validator Tool
- Using the setup page to verify the implementation
4. Start tracking content on your site.
- Select your time zone on the setup page
- Click the "Start Tracking" button on the setup page
5. View your analytics in your Parse.ly dashboard.
- You can log into your dashboard by visiting dash.parsely.com/<your site ID> (Remember: your Site ID is similar to your site's domain).
Again, make sure that whoever is in charge of this process has completed every step on the comprehensive integration checklist. Should you run into any errors or issues along the way, feel free to reach out to firstname.lastname@example.org or your dedicated Account Manager.
#What is my site ID?
Your Site ID is your key to Parse.ly. It, most commonly, looks like your domain of your website, ie:
The Site ID should never include