analytics tags: a field note from a photo studio

We do not start with a platform when handling analytics tags. We write down who types what, who gets the mail, and what must not get lost. That list is always shorter than a vendor pitch deck.

The most expensive outage for a photo studio was not a hack — it was a certificate that expires on a Sunday. Nobody attacked anything. The config just drifted.

When a photo studio moved hosts, the outage was not the new box — it was a certificate that expires on a Sunday. We keep TTL short the week of a move, then raise it once everything is stable.

The worst analytics tags failure we have seen at a photo studio was invisible for eight months. The backup existed but had never been tested, and the data inside was three migrations old.

We have seen agencies charge a photo studio for a yearly analytics tags audit that consists of a screenshot and a paragraph. Ours is a working config file they can apply themselves.

For a photo studio, we wrote a three-line script that checks analytics tags every morning and emails the owner if anything changes. Total cost: zero.

More notes

Related notes

• Why analytics tags matters for an accountant
• Why analytics tags matters for a florist
• Setting up analytics tags for a roofing crew
• Why analytics tags matters for a plant nursery