Home/Notes/analytics tags for a restaurant
analytics tags for a restaurant
18 Sep 2024
How a restaurant deals with analytics tags — and what usually goes wrong.
The problem: a certificate that expires on a Sunday. analytics tags slows the page for a restaurant.
a restaurant did not want to hear about analytics tags. They wanted to know: will the site work tomorrow morning. The answer was yes, but only if we fix a certificate that expires on a Sunday today.
We rotate API keys for analytics tags annually. a restaurant did not see the point until we showed them the access log: the old key had been used from an IP in a country nobody on their team has visited.
The most expensive outage for a restaurant was not a hack — it was a certificate that expires on a Sunday. Nobody attacked anything. The config just drifted.
Complexity is the enemy of uptime. a restaurant had three layers of proxy in front of a site that gets two hundred visits a day. We replaced it with a static page and correct analytics tags.
a restaurant asked us to look at analytics tags after a customer screenshot showed a browser warning. The fix took eleven minutes; finding the cause took two hours.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com