Introduction to Parse.ly Integrations

Welcome to the Parse.ly integration process! The Support team will help you get started so you can use your new Parse.ly products. This document contains answers to your questions: the who, what, where, when, and how of Parse.ly integrations.

Who will we work with?

A member of the Support team will be assigned as your integration project manager (PM) and will work closely with your Relationship Manager (RM) from Parse.ly’s Customer Success team.

Where is our integration project?

Your PM creates an Asana project customized based on the products and features in your contract. This project contains implementation instructions specific to your technical stack and preferences based on info gathered from a technical questionnaire we will ask you to complete. The tasks and milestones contained within will help keep your team on track to complete the project correctly and in a timely manner.

Who is responsible for completing tasks?

Tasks and milestones are divided among 3 teams:

1. Business: The end-users of Parse.ly products (e.g. editorial, content, marketing, executive stakeholders).
2. Technical: The people who will work on the Parse.ly integration (e.g. product, development).
3. Parse.ly: The Integration Project Manager and Relationship Manager.

Each task and milestone in your Asana project is labeled with a tag identifying the team responsible for completing it. As you progress through the integration, tasks are assigned to a representative from each team as they are ready to be worked on.

What development work is required?

This varies based on the products included in your contract and project. Here’s a quick overview of our products to give you an idea of the development effort for each:

• Dashboard (core elements): requires adding a JavaScript tracking code and metadata in a Parse.ly-supported format. 
• Channels: Traffic from Google AMP, Facebook Instant Articles, and iOS and Android apps can be broken out in the Parse.ly dashboard with additional development work. Apple News traffic is also visible in its own channel so long as the Apple News format is utilized. An RSS feed is not considered to be truly native to Apple News. Therefore, we cannot capture analytics on any RSS articles due to this. Implementation requires outreach to the Apple News team for feed enablement, but no additional development work is necessary. 
• Campaigns: Parse.ly automatically tracks campaigns via supported parameters.
• Video tracking: Video content must be embedded on your site in order to be trackable. The development lift is low for Parse.ly-supported players including Brightcove, JWPlayer, mediaelement.js, video.js, Vimeo, Wistia, and YouTube. However, custom or unsupported players or videos that play in iframes require a significant addition of code.
• Conversions: You may choose between a Parse.ly managed low-code conversions integration, a self-managed integration, or a combination of both. Take a look at our Conversions Tracking and Conversions Tracking Best Practices doc to ensure your site is optimized for setup and that Parse.ly supports the conversion events you want to track. 
• Segments: Parse.ly offers two types of segments. Those based on standard data (most commonly, geographic segments) do not require development work. Segments based on custom data require the addition of code including a defined key/value pair indicating when a pageview is fired for a user that belongs in the segment.
• API: requires setting up calls for content personalization and recommendations.
• Data Pipeline: requires an experienced data science team with the knowledge and skills to build in-house analytics using Parse.ly data.
• SSO: requires connection and authentication with your system.

How do we get started?

Completing the technical questionnaire is the first step in your integration project. Be sure to designate a member of your technical team to provide responses as quickly as possible. Once we receive your answers, we’ll set up a kickoff call so you can meet your PM and RM, discuss your team’s goals, review the integration process, and talk about future steps like training. 

When will our integration be complete?

This varies depending on several factors: which products are included in your contract, how many sites you’ll track with Parse.ly, and the availability of your development resources. Due dates and timelines are included in your project and represent an estimate of the amount of time each task and milestone should take to complete. If you can complete steps ahead of time you can keep moving forward. Alternatively, the timelines can be adjusted if you need additional time to complete some steps. Our goal is to help you implement our products correctly so that your team can begin using them as quickly as possible.

How can we receive technical help in the future?

After your integration project is complete, the Parse.ly Support team will continue to be your go-to resource for technical procedures, questions, and issues throughout the life of your account. The best way to reach out is to email support@parsely.com and cc your Relationship Manager.