I’m in the process of implementing the JavaScript SDK on our website through Google Tag Manager. I have the page, track, and identify working properly!
However, after a user logs out of my app I’m calling _cio.reset() (documentation) and I can’t get this to work. I also don’t understand how to troubleshoot this.
Here is the code (tag) I’m firing in GTM … is this code correct?
![](https://uploads-us-west-2.insided.com/customerio-en/attachment/cac9e7f1-7151-4855-a1bb-2638ad087921.png)
It appears to be firing properly where I want it (on the logout screen, which is confusingly named Sign In but doesn’t matter):
![](https://uploads-us-west-2.insided.com/customerio-en/attachment/6b1d3337-543a-4a6b-b7b4-4791745600e1.png)
Here is what the detail of the fired tag looks like:
![](https://uploads-us-west-2.insided.com/customerio-en/attachment/a2ba0272-d044-4eca-ad4e-1a7be67d4ea2.png)
The problem is that, even after this tag fires, as I continue to browse the website, the activity (page views, etc) continues to be tracked and associated to a known person in Customer.io (the person who was identified previously) so Customer.io appears to not be “accepting” the _cio.reset() call -- shouldn’t future activity after _cio.reset() is called show up in Customer.io as anonymous activity?
The only way I can think to troubleshoot this is looking at the cookies stored. Both before and after the reset is called, there’s still a _cioid cookie showing up. Should this cookie go away automatically after _cio.reset() is called? Looking for help knowing how to debug this.
![](https://uploads-us-west-2.insided.com/customerio-en/attachment/f3916c55-5898-4f83-9188-dd9405acb7e7.png)
Thanks!
Best answer by Jordan
View original