• Hello,

    I am using WP Statistics to track traffic sources, and I’ve noticed a recurring issue with traffic originating from our Telegram channel.

    When I check the Referrals section in WP Statistics, I can see that traffic from major sources like Google, Bing, Instagram, and Facebook are all being correctly identified and listed. However, despite generating a considerable number of clicks from links shared on our Telegram channel (specifically from the domain t.me), Telegram is completely absent from the Referrals list.

    This strongly suggests that the traffic is either:

    Not recorded by the plugin.
    
    Mislabeled as "Direct" or "Unknown" traffic.

    The inability to attribute traffic from Telegram (the referrer domain being t.me) makes it impossible to accurately measure the success of our campaigns on that platform.

    Could you please advise on how to ensure that WP Statistics correctly recognizes and logs traffic where the referrer domain is t.me and properly categorizes it in the Referrals list? Are there any specific settings, custom referral rules, or database adjustments required to address this source attribution issue?

    Thank you for your assistance.

Viewing 1 replies (of 1 total)
  • Plugin Support Mehmet

    (@gandomi)

    Hello Soroush,

    Thanks for reaching out!

    The reason Telegram traffic doesn’t appear in WP Statistics is that Telegram doesn’t send the referrer for privacy reasons. This means clicks from Telegram show up as Direct Traffic instead of Telegram.

    To make sure your Telegram traffic is tracked correctly, you can add source and medium parameters to your links.

    https://example.com?utm_source=telegram&utm_medium=social

    Once you do that, WP Statistics will be able to recognize the visits, and you can easily see the stats under Statistics > Referral > Social Media.

    This small tweak will let you get a clear view of how your campaigns are performing on Telegram.

    Best regards,

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.