ContentSherpa Traffic By Referrer

Modified on Wed, 6 Aug at 10:41 PM

The ContentSherpa Traffic By Referrer report shows the origin of visitor traffic to your site, based on the referring URLs. It provides key metrics such as sessions, visitors, engagement levels, conversations, and leads, helping you analyze which external sources or links are driving the most traffic and user interaction.


To access the Traffic By Referrer reports, follow the steps below.

  1. From the Left Nav Menu, click Reports > ContentSherpa > Traffic By Referrer. 
  2. The Traffic By Referrer page is displayed, presenting each Referrer alongside the key performance metrics.

    Note: Clicking on the Referrer link opens the page or source from which the visitor was referred.


    Key Metrics Displayed in the Report:
    • Referrer - The URL that directed traffic to your site.
    • Sessions - Total number of times users visited from that referrer.
    • Visitors - Count of unique visitors from that referrer.
    • Engaged Sessions - Sessions where visitors interacted meaningfully.
    • Engaged Visitors - Unique visitors who had engaged sessions.
    • Conversations - Number of chatbot conversations initiated. 
    • Questions - Number of visitors submitted questions.
    • Conversation Saves - The total number of conversations that were saved.
    • Leads - Leads captured from the interactions. 
    • Repeat Visitors - Visitors who returned after their first visit.

  3. On the Traffic By Referrer page, you can search and customize the report table by Date. 
  4. You can filter by the Dimensions available in the drop-down menu. A maximum of three Dimensions can be applied at a time.
  5. You can filter and apply sub-filters to refine the traffic data view. 
    You can read here to learn how to use the report features.




 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article