Envato Market has gone HTTPS everywhere!

PIXINVENT · July 7, 2016, 5:02am

I think Dashbord Plus also needs to be updated. As its not working for us.

xphp · July 7, 2016, 5:24am

I think that explains 20%~30% loss in traffic today?

urbazon · July 7, 2016, 7:23am

Working now, thanks

JoomlaBuff · July 7, 2016, 7:31am

Hi @dtbaker no not working i can see dashboard plus tab in the settings page but when i hit its redirect me to codecanyon profile page. no options are there as before

PIXINVENT · July 11, 2016, 5:06am

There is a big traffic drop after market goes to HTTPS, don;t know why but it’s affect on sales too.

dtbaker · July 12, 2016, 3:35am

No traffic drop here in Google Analytics. I’ve actually seen an increase.

dtbaker · July 12, 2016, 12:48pm

Here’s a good one for you

paypal.com just started to appear in our Elite Analytics around about the same time HTTPS launched.

Most are paypal.com/webscr and some are paypal.com/in/cgi-bin/merchantpaymentweb

It’s only some referrals, not all. Screenshot:

Think this is related to HTTPS?

dtbaker · July 12, 2016, 12:58pm

(Could it have been customers who originally landed days ago in HTTP, and coming back from HTTPS sets a new referral because they don’t already have one registered in Analytics? I’m not sure how Analytics treats customers if they jump from http to https)

jacobbednarz · July 12, 2016, 10:51pm

I’ll have a chat with our analytics team and see if they can shed some light on the situation here. I know last time I spoke with them they mentioned we were seeing more “sessions” being reported as they were being split into multiple instead of the one continuous flow.

I’ll check out the w3c spec for the referer policy today and see what I can come up with but if this is something we’ve stumbled on and PayPal is at fault, we’ll need to get in touch with them to resolve it.

dtbaker · July 13, 2016, 4:02am

Here we go:

jacobbednarz · July 13, 2016, 5:43am

I’ve spent a bit of time looking into this and the reason this has popped up is indeed because of the move to HTTPS however this is correct behaviour based on the w3 spec. Section 15.1.3 of RFC2616 states the following:

Clients SHOULD NOT include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.

Prior to the HTTPS rollout, PayPal and Skrill transactions were returned to a HTTP URL from a HTTPS referrer whereas now it is a HTTPS return URL from a HTTPS referrer. This coincides and explains the behaviour we are seeing for analytics. Please note, this does not mean you are getting any differences in traffic - it is just the source that is now different as previously it would have been marked as “other” or “unknown”.

Thanks to @dtbaker for the work around!