The main google analytics cookies aren’t being set on your homepage, but they are being set on /about.
It looks like the domain dev.zeroqode.com has analytics configured correctly, so any page that contains a call to dev. sets the ga cookie on the parent domain (.zeroqode.com), enabling analytics on subsequent navigations.
Whatever you’re doing on dev, copy over to your main site and you should get your analytics back.
It seems your registrar has redirect option. Try setting up a URL redirect from freelancer24.nl to www
https://www.argeweb.nl/domeinnaam/kb/hoe-stel-ik-een-redirect-in-naar-een-andere-website-106.html
It’s possible that our automated systems picked up a stale record. We schedule a DNS check for 24 hours after you first register a domain name with your app, and unfortunately sometimes the DNS system is even slower than that.
From everything I can see, your app looks okay.
Thanks @peterj! I really appreciate you taking the time to look over my app… I can see that you’re incredibly busy with this.
I’m pleased that everything is ok.
Thanks again 
Hi @peterj missed your response entirely 
the thing is, in each app (zeroqode.com or dev.zeroqod.com etc.) we simply installed Google Analytics plugin made by Bubble and inserted the same GA code.
we don’t set the code on each page separately that’s why this is vey odd. Maybe there is some way to reinitialize the GA plugin? Or do something else for the code to appear on the home page (and perhaps other pages where it doesn’t appear)
Thanks!
Hi Peter,
i see that it’s ticked - did you enable it already? I believe we need to deploy right?
When it’s not ticked means no cookies can be installed including the ones from Google Analytics plugin?
There’s a box in dev. and a box in your main site. When I glanced in there the dev. box was ticked already, but it wasn’t on your main site. If you’re seeing something else … hmm. Not sure what to tell you. Verify that it’s set on your main site, though.
I believe a deploy is necessary after changing that setting, yes.
If that check box is inactive, it means we won’t set cookies by default on users visiting your site… including google analytics. They have to opt-in.
People usually uncheck that option for legal reasons, and (I believe) use a cookie consent plugin to enable opt-in.
Oh, it’s actually the other way around @peterj
the dev box wasn’t ticked and main site was ticked.
because it reads " do not set cookies for new visitors by dafault" ticking the box sets it to true. Since it was ticked for main site the new visitors were not tracked - only the logged in ones were.
I think this should solve the issue. We’ll deploy and give it a try
Thanks a lot!
I just moved to cloudflare configuration with CNAME (so www.domain). But now I get constantly this error:
And Can’t configure my email settings
Update//
And now page is dead @peterj any suggestions?
Update2//
Cloudflare configuration is now correct (so it was probably me not being patient) but I still don’t see any images and connection to webpage is “unsecure”.
Any help will be appreciated!
My current local time is 18:11
You set your domain with bubble at 16:37
You were getting DNS errors until 17:23
Somewhere between 17:23 and 18:11 your DNS records finally stabilized enough to issue certificates
Once DNS stabilizes, certificate issuance takes maybe 30s, but it takes 30 minutes for all server caches to catch up with the fact that you should be using SSL
Your site looks correct on my end. Give it a bit longer. The images probably aren’t loading momentarily because of mixed content policies: Most browsers don’t allow http + https requests to be mixed together.
So again it’s only impatience 
thank you I will check in the morning (my local time is 00:21)
Thanks!
Is there anyone available for helping me with setting this up?
Hi Peter, (or anyone else that can assist)
I am setting up a new domain on my new bubble app. I transferred my DNS settings with name servers to namecheap as mentioned and allowed a few hours but still getting this bubble error? is this because i have to wait longer?
Also the CNAME wont show for the google Cname checker, is this also due to having to wait longer or have i inputted it incorrectly.
Note: my domain manager is still with godaddy just nameservers and dns with namecheap
Attached phots of the DNS and bubble:
Thanks in advance to anyone that can help
As I see it now, your records have propagated. NS records are quite a bit slower to propagate than other types, but everything looks good from my end now.
@peterj some domain managers don’t allow to point CNAME or ALIAS if it’s not an IP.
So basically can’t add CNAME/ALIAS with app.bubble.io value.
Used a DNS tool to see the IP (and got two 104.19.240.93 and 104.19.241.93)
Not sure if it will work
Use namecheap dns. Works like a charm.
I have seen the same issue - dramatic drop in traffic, new sign ups etc. A month or so later, now I am seeing some pick up.
as it turned out (thanks to @peterj who solved it) in our case the problem was because this checkbox was checked
If we are on a dedicated instance, do we use http://app.bubble.is instead of http://app.bubble.io/? Since we are still on the old domain?
