#Conversions overview video
Parse.ly Conversions currently supports five standard conversion types and one custom type:
- Subscription - When a user buys a subscription that will result in recurring revenue.
- Newsletter Signup - When a user provides their email via a form in order to receive emails from a company, such as a newsletter or an email course.
- Lead Capture - When a user provides identifying details (e.g. email, name) via a form to indicate they have interest in what the company is selling (i.e. a lead).
- Link Click - (Premium only) When a user clicks a link or button (e.g. an internal link or affiliate link).
- Purchase - (Premium only) When a user completes the one-time purchase of a product.
- Custom - (Premium only) When a user completes an action not covered by the five standard events.
Note: In the future, Parse.ly may provide benchmark comparisons of the standard categories of events (e.g. comparing how your newsletter signup performance compares to rest of the Parse.ly network). For this reason, we discourage using custom types except when absolutely necessary.
For conversions premium, there are five categories of conversion events, plus custom events: Each conversion action is a combination of two identifying attributes:
- Type - The category of the conversion listed in the section above. Parse.ly supports six types, which you can choose from.
- Label - (Premium only) The name of the specific action taken by a user (described in the parameter). You have the freedom to customize and specify the label.
- You must be able to put Parse.ly tracking on pages or forms where conversions occur and on any pages that users view on their way to converting.
- All pages must have valid metadata provided to Parse.ly.
#Code-free integrations details
Just exactly how code-free is this integration? It's actually pretty nifty! We will ask you a few questions about your site and conversions requirements, and then we will send you the code you need.
1. Conversions Information Form
Filling out this form is the first step. It requires knowledge about:
- What types of conversions you need
- The labels to associate with these conversions
- What page(s) the conversions occur on or off your site
- The type of trigger for each conversions, ie. Form submission, Link Click, or Page Confirmation
2. We do the magic and write your code and automatically implement it on your site through the Parse.ly tracker
3. You test to verify conversions are integrated correctly
#How to test conversions events
It is important to be able to test sending conversions without actually sending the event and cluttering up your reports with tests! We recommend using the following method to test all conversions on your site:
- Open the developer console and filter console to
- Select the "Settings" symbol in the top right, and then select "Preserve log"
- Paste this command into the console:
PARSELY.config.customizations.debug = true;
- Do the conversion action and look in the console for a message like this:
Debug: Conversion event would have been sent with type "Link Click" and label "Link Click".
#Self-managed integration option: Write your own conversions code
This is a special case where you already have conversion event triggers defined for other tools and systems and it would be best to keep that logic centralized and send Parse.ly conversion events directly. The advantage of using this method is that it provides you with more control of your conversions integration. However, there are disadvantages that should be considered before moving forward with this more time-consuming approach:
- You are responsible for the configuration being correct, and maintaining and updating that configuration as your site changes.
- You will not benefit from ongoing Parse.ly development, including bugfixes and features based on our extensive experience managing conversions for other customers.
- You will need to carefully consider and handle a variety of load order and race conditions, because the business logic is separated from the Parse.ly tracker module.
- Any changes to conversion integrations require site deploys.
If you decide to move forward with this secondary integration option, you can see our our detailed conversions integration documentation here for code samples and configuration details.