Skip to main content
When you use the Cometly Report Builder (Cometly’s tool for custom reports), you may see the label No Source. It means the origin of a customer’s journey could not be tracked or identified. Funnel events such as booked demos, leads, converted trials, trial LTV and gross revenue are examples where No Source might appear often. No Source in Cometly reports usually comes from a gap in tracking: the journey began before Cometly was installed, the pixel (the script on your website that records visits) did not load, an ad was missing its URL parameters, or the visitor moved between two of your domains. This article explains each cause and what you can do about it.

Setting expectations

Seeing 5-10% of events labeled as No Source is normal because of factors like complex VPNs or technical limitations. With proper setup and monitoring, you can minimize this percentage.

Automatic Advanced Matching

Automatic Advanced Matching increases data accuracy by sending hashed customer information for better attribution. Turning off this feature will not affect Cometly’s core tracking and attribution abilities. You can disable it without compromising functionality.

Common reasons for No Source

1. Historical customer journeys

If a customer’s journey began before Cometly was fully installed and integrated, their source information might not be available. This is especially common with historical data from before tracking was in place. Learn more about historical customer journeys and data maturing.
Retargeting campaigns can provide attribution insights for past customers. If a past customer interacts with your ads, Cometly’s flexible attribution windows can capture recent clicks and show you their updated interactions.

2. Pixel installation issues

An incorrectly installed Cometly pixel can prevent accurate tracking of customer journeys. Below are common scenarios and how to address them. The Cometly pixel is installed through Google Tag Manager (most common) Google Tag Manager is frequently blocked by browser tracking plugins, so a Cometly pixel installed through GTM will often fail to load. This leaves gaps in your tracking data, including No Source. To fix this, remove the Cometly pixel from Google Tag Manager and install it directly (hard-coded) in the <head> section of your website. This way, the pixel does not rely on GTM and is not affected by blocker plugins. The pixel is not installed on all pages If the pixel isn’t installed on all pages where conversions occur, Cometly cannot attribute events correctly. Install and verify the Cometly pixel Third-party forms or iframe forms For third-party forms embedded as iframes, the pixel must be installed on both the landing page and the iframe to capture data accurately. View guides for setting up tracking on supported third-party forms Checklist for troubleshooting pixel installation:
  1. Is the pixel installed on all landing pages that your ads direct to?
  2. Are there additional domains or subdomains that need the pixel?
  3. Are third-party forms properly integrated and tracked?

3. URL parameter issues

URL parameters identify and track specific traffic sources. If they are missing or set up incorrectly, you can get No Source events. Fixing URL parameter errors:
  • Make sure all of your paid ads have the Cometly URL parameters. See Add URL parameters to your ads. If the Ads Manager shows a red dot, see Fix UTM Setup Errors.
  • Make sure visits from social platforms are tracked correctly by adding URL parameters to bio links and organic posts. This keeps attribution consistent even when referrer information is unreliable. The same URL parameters page has a section on social organic URL parameters.

4. OAuth or cross-domain tracking not set up

For SaaS companies or businesses with multiple domains, cross-domain tracking must be set up to avoid No Source events. How to enable cross-domain tracking:
  1. Install the Cometly pixel on all relevant domains (for example, your marketing website and your app registration page).
  2. In Cometly, go to Setup > Install the Cometly pixel. Under Pixel options, turn on Automatic Cross Domain Tracking.
Benefits:
  • Automatic tracking of the comet_token across verified domains.
  • A unified view of user journeys across multiple websites.
If you run a SaaS company, see Pixel setup for SaaS companies to set up OAuth and automatic cross-domain tracking.

Troubleshooting summary

To address No Source events, review the areas below. Check Setup > Tracking Health in Cometly, verify that the pixel loads using your browser’s developer tools, and look for conflicts from other scripts. After a fix, reload your website and monitor new events for correct attribution.
  1. Historical journeys: Were these events triggered by journeys that began before Cometly was installed?
  2. Pixel installation: Is the pixel installed correctly on all necessary pages and forms?
  3. URL parameters: Are URL parameters set up properly?
  4. Cross-domain tracking: Is the comet_token linking user activity across domains?

Confirm you have reduced No Source in Cometly reports

A fix only applies to journeys that start after you make it, so events that already show No Source stay as they are. Open Setup > Tracking Health and check that the pixel and URL parameter checks no longer report a problem. Then watch your new events in the Report Builder: the share labeled No Source should fall toward the normal 5-10% range.

Frequently asked questions

Is No Source the same as Direct / None in Cometly?

No. They are two separate sources in the Report Builder. Direct / None is a visit that reached your site without a referring website, for example when someone types your URL into their browser, while No Source means the origin of the journey could not be tracked or identified. See Referral vs. direct traffic sources.

Can I fix conversions that already show No Source?

Not when the journey began before the pixel was installed. Cometly cannot attribute a conversion to an ad click that happened before the pixel was live, so the fixes on this page reduce No Source on new events. See Data maturing.

How do I check that the Cometly pixel is firing on a page?

In Cometly, go to Setup > Install the Cometly pixel and use Verify your pixel. You can also install the Cometly Pixel Helper, a Chrome extension that shows an Init event on each page that contains the pixel. See Cometly Pixel Helper.

Next steps

Still have questions or need a hand? We’re happy to help. Reach our team at support@cometly.com.