Skip to main content
What does 'No Source' mean?

Explaining the Report Builder source 'No Source'.

Updated over 3 months ago

👋 Start Here

When viewing data using the Cometly Report Builder, you may come across the label 'No Source'. This designation typically indicates that the origin of a customer's journey couldn't be tracked or determined by the system properly. In this article, we will address the most common reasons for why this would occur.


Historical Customer Journeys:


The customers associated with this tag may be completing journeys that began before Cometly was fully installed and integrated. As a result, their source information may not be available. You can read more about historical customer journeys by checking out our article on Data Maturation.

Pro Tip: While you can't control the timing of a customer's journey, running retargeting campaigns is a great way to get attribution insights on past customers. If a past customer engages with your ads, you can leverage Cometly’s flexible attribution windows to track their recent clicks and uncover more detailed insights from these more recent interactions.


Pixel Code Installation Issues:


If the Cometly Base Pixel Code was not installed correctly on your site or platform, tracking errors may occur. This can prevent Cometly from properly identifying and recording the customer's journey source.

How to fix: An easy checklist to go through when looking for pixel errors would be the following:

  • Do I have the pixel installed across all landing pages that my ads are directed to?

  • Are there any additional landing pages that are separate from my primary domain that the Cometly Base pixel needs to be installed on?

  • Am I running any third party forms on my landing pages?

    • If 'Yes', are those forms installed as an iframe on my site?

      • If 'Yes', then make sure the Cometly Base Pixel is installed on both the landing page as well as the iframe form.


UTM Parameter Issues:


Incorrect installation or configuration of UTM parameters may also cause the 'No Source' label to appear. UTM parameters are crucial for identifying and tracking specific traffic sources, and errors here can disrupt that process.


Conclusion

In conclusion, there are three common areas that can affect an event being tagged as 'No Source'. By using the information provided in this article, you'll be able to immediately troubleshoot and investigate upon seeing this tag. If your 'No Source' events do not meet the criteria mentioned in this article, please don't hesitate to reach out to support@cometly.com so that we can investigate further!

Did this answer your question?