Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
blog.justinthiele.com
Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
1–10 of 10 posts
Re: Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
#2Re: Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
#3Re: Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
#4You can edit how sources are defined using Custom Channel Groupings. So you can define traffic from HN as Social or Referral. Unfortunately this settings won't be retroactive, but it will work for future traffic.
Re: Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
#5> (annoyingly, traffic from Hacker News is counted as ‘Direct’ and not a ‘Referral’ in analytics, so it’s hard to get actual numbers) You can edit how sources are defined using Custom Channel Groupings. So you can define traffic from HN as Social or Referral. Unfortunately this settings won't be retroactive, but it will work for future traffic.
Re: Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
#6it's probably a better idea for the browser to handle the scrolling.
Re: Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
#7> (annoyingly, traffic from Hacker News is counted as ‘Direct’ and not a ‘Referral’ in analytics, so it’s hard to get actual numbers) You can edit how sources are defined using Custom Channel Groupings. So you can define traffic from HN as Social or Referral. Unfortunately this settings won't be retroactive, but it will work for future traffic.
I've seen people bypass this by either:
1. Having a HN specific URL (sometimes just ?hn attached to the URL)
2. Just having HTTPS landing pages.
One thing that could help fix this behavior (on newer browsers) would be for HN to explicitly authorize passing the referrer using `` or "origin"
EDIT: Filed a bug to get this implemented on HN, since Chrome and Safari support it, and Firefox support is ongoing: https://github.com/HackerNews/HN/issues/68
Re: Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
#8Re: Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
#9> (annoyingly, traffic from Hacker News is counted as ‘Direct’ and not a ‘Referral’ in analytics, so it’s hard to get actual numbers) You can edit how sources are defined using Custom Channel Groupings. So you can define traffic from HN as Social or Referral. Unfortunately this settings won't be retroactive, but it will work for future traffic.
That's not the issue here. The issue is that Hacker News is on HTTPS, but the link he posted to dictionarydomains.co isn't. Browsers don't pass a referrer on links between HTTPS->HTTP. So, visits from HN don't have a referrer. Custom Channel Groupings won't help in this case, because GA is completely blind to what visits are referrer-blocked HTTPS I've seen people bypass this by either: 1. Having a HN specific URL (s…
Do you know if it's the same case if the referrer link is HTTP->HTTPS?
Re: Show HN: The HN effect on Dictionary Domains (traffic and revenue numbers)
#10Earlier quoted context omitted.
That's not the issue here. The issue is that Hacker News is on HTTPS, but the link he posted to dictionarydomains.co isn't. Browsers don't pass a referrer on links between HTTPS->HTTP. So, visits from HN don't have a referrer. Custom Channel Groupings won't help in this case, because GA is completely blind to what visits are referrer-blocked HTTPS I've seen people bypass this by either: 1. Having a HN specific URL (s…
Thanks for that detailed explanation. I learned something new. Do you know if it's the same case if the referrer link is HTTP->HTTPS?
Default behaviors:
HTTP->HTTP: Referrer
HTTP->HTTPS: Referrer
HTTPS->HTTPS: Referrer
HTTPS->HTTP: No Referrer :(