> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Events and properties – Product Analytics pocket guide

Canonical URL: https://posthog.com/learn/product-analytics/pocket-guide/101

Chapter 01

# Events and properties – Product Analytics pocket guide

On Twig, choosing **Forest**, **Coast**, or **City** changes the stays on the page. The filter works. But once a visitor leaves, the product engineers can't tell which destination caught their attention.

To measure that behavior, the team uses [Product Analytics](https://posthog.com/docs/product-analytics.md). Its basic unit is an [event](https://posthog.com/docs/data/events.md) – a record that something happened in the product.

## See what autocapture records

The engineers add the [PostHog web SDK](https://posthog.com/docs/libraries/js.md) to Twig using its project token and host:

```javascript
posthog.init(TWIG_POSTHOG_TOKEN, {
  api_host: TWIG_POSTHOG_HOST,
});
```

Once Twig loads the SDK, it records pageviews and [autocapture](https://posthog.com/docs/product-analytics/autocapture.md) is on by default. Clicks on links and buttons become `$autocapture` events with details about the element and page, without a separate capture call for each button. The team can see what people use before deciding which actions need custom names and properties.

Select a filter below to inspect what Twig records for stay filters:

Reset

Twig

Filter by destination typeForestCoastCity

1 stay

![Dark A-frame cabin among autumn trees, with a gravel path leading to the entrance at dusk](https://posthog.com/static/cabin-52b343c8c87096a619df7bf1a904bcea.jpg)

### Adiron-shack

Adirondacks, New York

4 guests · 2 bedrooms · 2 baths

**$355** / night USD