TIL: You can use their API to auto-create goals.

Alright, so the Fathom hype train is usually about the "no-code" clicky-click interface. Fine for one-offs. But if you're managing more than a handful of sites and actually care about tracking trends, manual goal creation is a time sink masquerading as simplicity.

Their API is the real unlock. You can script goal creation based on events—new site launches, new marketing campaign landing pages, whatever. This means your analytics actually keep pace with your infra, which is how it *should* work.

Here's a crude but functional Python snippet I use. It checks for a new page URL in our site deployment manifest, then creates a goal to track its visits.

```python
import requests

FATHOM_API_KEY = 'your_key_here'
SITE_ID = 'your_site_id_here'

def create_pageview_goal(page_path, goal_name):
url = "https://api.usefathom.com/v1/goals"
headers = {"Authorization": f"Bearer {FATHOM_API_KEY}"}
payload = {
"site_id": SITE_ID,
"event": "pageview",
"path": page_path,
"title": goal_name
}
response = requests.post(url, json=payload, headers=headers)
# Always log the response. Don't trust it worked.
print(f"Status: {response.status_code}, Response: {response.text}")
return response.status_code == 200

# Example: Trigger this from your CI/CD pipeline post-deploy
new_feature_page = "/launch/new-feature"
create_pageview_goal(new_feature_page, "New Feature Launch Page")
```

Key points:
* This moves goal creation from a manual, forgettable task to an automated part of your workflow.
* The API is straightforward, but like any cloud service, monitor your usage. It's another thing that can fail silently.
* You'll need to handle auth and errors properly. This example is barebones.

Now, the real test: does this actually save time and improve data consistency? In my case, yes. But I'd want to see the bill from Fathom to see if there's a cost impact for high volumes of API calls versus manual creation. Probably negligible, but I don't take claims on faith.

show me the bill