Cookies · Consent Mode v2
No ad cookie runs until you say so.
You probably landed here looking for a 24/7 plumber in Seattle. This site keeps one note about your cookie choice. Everything else waits for the Allow button.
Three kinds, one switch
Strictly necessary storage always runs; analytics and advertising run only after you press Allow.
Strictly necessary. The record of your cookie choice, and the chat token if you open the support chat. Without the first, the banner would ask you on every page. Without the second, a chat about a slow drain would vanish when you click to the next page. Neither tracks you across other sites.
Analytics. Counts of visits and which pages people read before they call. We use it to see whether anyone reads the drain cleaning section or skips straight to the phone number. Held off by analytics_storage until you allow it.
Advertising. Conversion cookies from Google Ads, Microsoft Advertising and Meta Ads. They tell the platform that a click on our "emergency plumber seattle" ad turned into an inquiry. Held off by ad_storage until you allow it.
There is no fourth category hiding behind a "partners" link. No social widgets, no embedded video, no map tiles.
Every key, by name
This table is the full list of what can land in your browser from this site, and how long each stays.
The first two rows run without asking, and both live in your browser's local storage rather than as cookies. Every row marked "After Allow" is set only once all four consent signals are granted.
| Name | Set by | What it is for | Lasts | Category |
|---|---|---|---|---|
site_consent_v2 | This site, vedi542.js | Remembers Allow or Decline so the banner stops asking. The only stored choice on the site. | 6 months | Strictly necessary |
bees_chat_token | This site, cagif5f.js | Links your browser to your chat thread so you can return to it. Only set once you send a first chat message. | Until you clear it; transcript kept 12 months on our side | Strictly necessary |
_gcl_au | Google Ads | After Allow: stores the gclid so a later inquiry counts as a conversion. | 90 days | Advertising |
_ga, _ga_* | Google Analytics | After Allow: tells one visit from another for visit counts. | 2 years | Analytics |
_uetsid | Microsoft Advertising | After Allow: ties pages in one session to an msclkid click. | 1 day | Advertising |
_uetvid | Microsoft Advertising | After Allow: recognises a returning visitor for conversion counting. | 13 months | Advertising |
_uetmsclkid | Microsoft Advertising | After Allow: holds the msclkid from the landing URL. | 90 days | Advertising |
_fbp, _fbc | Meta Ads | After Allow, where a Meta campaign runs: browser ID and the stored fbclid. | 90 days | Advertising |
Swipe the table sideways to see every column.
The string on the end of the link
An ad click arrives with a click identifier in the URL, and whether it is kept depends on your choice.
We pay for search ads today. Google Ads and Microsoft Advertising send traffic here, and Meta Ads does where a campaign runs there. When you click, the platform tacks a parameter onto our address:
gclidfrom Google Adsmsclkidfrom Microsoft Advertisingfbclidfrom Meta Ads
It looks like ?gclid=Cj0KCQ… and means nothing to anyone but the platform. If you allowed storage, the matching tag keeps it in the cookie listed above, so a call booked through the form two days later still gets credited to the ad that brought you. If you declined, the value is read off the URL and dropped. It is not written to your browser, and the form does not send it on.
No platform has reviewed or signed off on this site. They sell the ad slot and count the clicks.
Consent Mode v2, signal by signal
Four signals start denied before anything loads, and your button press is the only thing that moves them.
The very first script on every page sets Google's consent mode defaults to denied, with a 500 millisecond wait for an earlier stored choice to load. Microsoft's UET tag reads the same consent state. Here is exactly what each signal does in each situation.
| Signal | Controls | First visit | After Allow | After Decline or withdraw |
|---|---|---|---|---|
ad_storage | Ad cookies on your device | denied | granted | denied |
ad_user_data | Sending user data to Google for ads | denied | granted | denied |
ad_personalization | Personalised ads and remarketing | denied | granted | denied |
analytics_storage | Analytics cookies | denied | granted | denied |
Swipe the table sideways to see every column.
While denied, Google's tags can send cookieless pings: a hit with no identifier stored on your device, used for modelled counts. A browser sending Global Privacy Control stays at denied on all four and is never shown the question again.
Saying yes, then changing your mind
Consent is one press of Allow in the bottom bar, and the "Cookie settings" link in every footer takes it back.
On your first visit a bar docks at the bottom of the screen. It does not cover the page, and the phone number and the form both work while it sits there. Allow grants all four signals. Decline keeps them denied. Ignoring it is the same as Decline.
To change it later, scroll to the footer of any page and press . The bar comes back and you choose again. Withdrawing sets all four signals back to denied at once. Cookies already placed by the ad tags then expire on their own schedule, or you can clear them in your browser settings straight away.
The choice itself is kept for 6 months, then the bar asks again.
What still works if you say no
Declining costs you nothing on this site: every page, the form, the chat and the phone work exactly the same.
Still works: reading every page, sending an inquiry, the support chat, the call button, and the written price we give you after a site look. A burst pipe repair at 3 a.m. gets the same answer whether you pressed Allow or not.
Stops: no ad or analytics cookie is set, click identifiers are not stored, the platforms get no ad storage or ad user data signal from your visit, and we lose the ability to say which ad brought you. That is our problem, not yours.
Their rules, in their words
The ad platforms handle their own data under their own documents, linked here so you can read them at the source.
- Google (Google Ireland Ltd / Google LLC): policies.google.com/privacy and how Google uses data from sites like this one at policies.google.com/technologies/partner-sites.
- Microsoft (Microsoft Ireland Operations Ltd): the Microsoft privacy statement at privacy.microsoft.com/privacystatement.
- Meta (Meta Platforms Ireland Ltd): facebook.com/privacy/policy.
What we do with the inquiry itself, how long we keep it and how to get it deleted is in the privacy policy. The terms of an actual job are on the terms page.
Ask about one cookie
If a name in your browser is not on this list, tell us which one and we will find out what set it.
Email [email protected] with the cookie name and the page you saw it on. Or call 206-745-7570; it is the same number that takes emergency calls, so keep it short if it is raining. Post goes to Beesplumbingandheating, 2401 SW Alaska St, Seattle, Washington 98106, United States.
To have data deleted rather than just explained, use the route on the data request section. We answer within 7 days.
Done reading? Water still running?
Call 206-745-7570