11–20 of 37 posts
The site looks great. When I tried to add a site, the link for the js to be included was missing the scheme (http|https): If we could have a restricted live demo, or a video to get a feel of how things work before needing to get some fair amount of data, that’d be even better. Great job and good luck with it. edit: apparently // is the way to go, see comments below.
The site looks great. When I tried to add a site, the link for the js to be included was missing the scheme (http|https): If we could have a restricted live demo, or a video to get a feel of how things work before needing to get some fair amount of data, that’d be even better. Great job and good luck with it. edit: apparently // is the way to go, see comments below.
// is a protocol relative URL so it will work for both http and https
The site looks great. When I tried to add a site, the link for the js to be included was missing the scheme (http|https): If we could have a restricted live demo, or a video to get a feel of how things work before needing to get some fair amount of data, that’d be even better. Great job and good luck with it. edit: apparently // is the way to go, see comments below.
Not including the http|https tells the browser to use the current page to figure out if the file should be loaded over http or https. Loading http content if you're on a https page will trigger non-secure content warnings with browsers
I like how your support options progress from "Online" to "CEO's iPhone" :) I'd like to read more about how it works, maybe see an integration guide, but it seems you only have the one (beautiful) page right now?
But behind the scenes how it works is that JS file (ie. usecharm.com/mmelin.js or something) returns different code depending on the cookie of the visitor and the configuration of the project. So if you launch a test, the goals and changes will come out in that file and it is also based on what page it is requested from, so the change could be different when requested from the homepage of your site vs a content page. By default it just has basic analytics stuff like referrer-detection and measuring demographics.
Do you think I should add a "behind the scenes" or similar section that explains all the technical stuff going on?
The site looks great. When I tried to add a site, the link for the js to be included was missing the scheme (http|https): If we could have a restricted live demo, or a video to get a feel of how things work before needing to get some fair amount of data, that’d be even better. Great job and good luck with it. edit: apparently // is the way to go, see comments below.
Though you're right it does look a bit weird, I will add a note to the instructions explaining what it is and that its not a bug or anything. Replacing it with http:// would've worked perfectly fine as well.
We use the same scheme to link to the media on our CDN so the app can switch seamlessly between http and https secured sections (account,billing) without any different code
As others have said, I'd include screenshots and details about the optimization process works, not the monitoring bits and referral tracking - after all, most people already have a very involved process they use to do that.
Design wise it looks good, but the signup button transparency is distracting.