Description from extension meta
Set a cookie to tell your websites that you're a developer. Use with Google Analytics to avoid tracking internal traffic.
Image from store
Description from store
From any website, simply click on the Developer Cookie Icon in your browser to set yourself as a developer/team member for that domain. Green means that you are a developer and that cookies will be set for this domain, gray means you are not. This preference is saved and this extension will try to always keep a cookie set for that domain.
The "name" and "value" of the cookie that gets created can (and should) be customized to be unique to you or your organization.
A list of all of your active domains can be found on the Options page, where domains can be easily added or removed as needed. There is also a button here to clear any cookies that have been saved on your device. Right-click the Developer Cookie Icon in your browser and select "Options" to access this page any time. Alternatively, you can find a link to this page in your Extensions manager.
••• How to Use •••
In your scripts, check for this cookie before performing certain actions.
JavaScript example:
- - - - - - - - - - - - - - - - - - - - - - - - - - -
var devCookie = "ChromeDeveloperCookie=123";
if (document.cookie.indexOf(devCookie) !== -1) {
// I am a developer
// Show control panel, debug info, etc.
} else {
// I am NOT a developer
// Insert Google Analytics code here, etc.
}
- - - - - - - - - - - - - - - - - - - - - - - - - - -
PHP example:
- - - - - - - - - - - - - - - - - - - - - - - - - - -
$devCookie = @$_COOKIE["ChromeDeveloperCookie"];
if ($devCookie === "123") {
// I am a developer
// Show control panel, debug info, etc.
} else {
// I am NOT a developer
// Insert Google Analytics code here, etc.
}
- - - - - - - - - - - - - - - - - - - - - - - - - - -
••• Notes About Cookies •••
On your next visit to any of the domains in your list, a new developer cookie will be created if one does not already exist (assuming this extension is enabled). New cookies are set to expire after 30 days. To keep your cookies up-to-date, a check is done when this extension is started (often at the opening of a new browsing session) and the expiration date of all active domains is renewed. However, for many reasons it is possible that even with this extension enabled you could load the page as a public user (once every 30 days or as often as your cookies are cleared). These cookies are very helpful, but please do not rely on this method of identification to be bulletproof.
Activating a domain applies to all pages on that domain, so clicking the icon while viewing any page on "http://www.example.com/"; will cause your cookie to be set for all of the following:
- http://www.example.com/page1.html
- http://www.example.com/subfolder/page2.html
- http://example.com/page1.html
- and so on...
However, cookies set for "example.com" will NOT be present on "beta.example.com" and vice versa. Each new sub-domain can be added or removed with a single click.
WARNING: This method of identification is not secure and should not be used to replace a user log-in system. Do not display secure data based on this cookie.
Latest reviews
- (2018-06-24) nice work!!
- (2017-08-16) Shafiq al-Shaar: Worked perfectly. I love you.
- (2017-02-04) Jean Sweeny: Great product to clear and reset cookies
- (2015-06-30) Michael Blair: This extension is very useful and is much easier than setting cookies using other extensions.
- (2015-03-10) Pranav Kaistha: Works great!
Latest issues
- (2021-03-15, v:1.0.4) Ed Bartelli: Allow different cookies to be set for different sites.
It's as described. I'm interested in using this to set default cookies for incognito mode. - (2020-08-15, v:1.0.4) Ritu Ragni: how to get top right side bars(close bar, minimize/maximize bar) in crome app
i am unable to get top right side all bars - (2016-12-09, v:1.0.4) Daniel Mee: Cookie not being exluded in GA Filter
Hello. Thanks for making this extension. I saw it when searching for solutions to excluding my dynamic IP from GA reports. Instead of having JS execute or not execute the tracking code I thought it would be better to use it to set a cookie which then gets filtered. Looking at the realtime results though I can see that I am still being tracked. Do you know why the idea might not be working? Here's a screenshot of my filter config https://cloudup.com/c3xbgAIuPkq Regards.