Skip to main content
All CollectionsGetting Started Advanced Setup Resources
Cometly Pixel Setup Guide for SaaS Companies
Cometly Pixel Setup Guide for SaaS Companies

Learn how to set up the Cometly Pixel for your SaaS company and understand the key considerations for effective implementation.

Updated this week

Welcome to Cometly! To help you get the most out of our platform, we've highlighted the top three essential setup steps for your SaaS business. Follow these simple guidelines to ensure accurate tracking and insightful analytics from day one.

1. Install the Cometly Pixel

Add the Cometly Pixel to the <head> of every marketing page (including blogs and academies) and only to the login and registration pages of your app. This ensures comprehensive tracking of visitor behavior without causing data conflicts.

Using Google Tag Manager? Follow our Google Tag Manager Installation Guide to easily install the Cometly Pixel.

Have a WordPress Site? Refer to our WordPress Installation Guide for step-by-step instructions. Note that additional steps are required to address caching issues specific to WordPress.

Next Steps:

  • Add & Verify Domains: After installing the pixel, navigate to the Install Pixel setup page in your Cometly dashboard. Add all your domains where the pixel is installed and complete the verification process to ensure accurate tracking across these domains.

When you add and verify your domains in Cometly, they are automatically included in the Referral Source Exclusion List. This ensures that any referral clicks originating from your own verified domains (e.g., from cometly.com to app.cometly.com) are excluded from your referral reports. Excluding your own domains from referral sources ensures that your referral data remains accurate. You can always add more domains to the referral source exclusion list by navigating to Traffic Permissions in the Space Setup area of the app.


2. Enable Cross Domain Tracking

To accurately track users as they move between your marketing site and your app, Cometly uses a unique identifier called the comet_token. This token links user interactions across different domains, ensuring precise attribution of traffic and conversions.

Example: Traffic moving from cometly.comapp.cometly.com

How to Enable:

  • Toggle On Feature: If the Cometly Pixel is installed on both your marketing website and app registration page, simply toggle on the Cross Domain Tracking feature in the Install Pixel setup area. Your verified domains will automatically utilize cross domain tracking.

What This Does:

  • Automatic Tracking: The comet_token is automatically passed between your verified domains.

  • Seamless User Journeys: Effortlessly track user interactions across multiple websites, providing a complete and unified view of their journey.

Why It Matters:
Enabling this feature ensures that all user activities are accurately tracked, regardless of the domain they interact with. This comprehensive tracking helps you understand user behavior better and optimize their experience across all your platforms.

Troubleshooting:
If you encounter any issues with the automatic Cross Domain Tracking feature, you can easily set it up manually by following our detailed guide.


3. Configure OAuth If Applicable

The Cometly Pixel automatically captures essential form fields such as full name, first name, last name, email, and phone number. We use the captured email address to link user actions to their attribution journey.


If your app uses OAuth for authentication:

  • Follow Our Setup Guide: Refer to our detailed OAuth Configuration Guide for step-by-step instructions.

  • Send the comet_token: Ensure that the comet_token is included during the OAuth process. This token links the OAuth authentication event back to the original user journey, allowing Cometly to accurately track user sign-ups and authentication events.

Why This Matters:

Proper OAuth configuration enables Cometly to monitor and analyze user authentication events seamlessly. By sending the comet_token, you ensure that each OAuth event is accurately attributed to the user's initial interaction with your platform.

Did this answer your question?