> For the complete documentation index, see [llms.txt](https://notara.gitbook.io/notara-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notara.gitbook.io/notara-docs/connectors/humblytics.md).

# Humblytics

The Humblytics connector gives the agent access to your privacy-friendly website analytics — traffic, pages, clicks, forms, funnels, and ad attribution.

## What It Enables

| Tool                              | Capability    | Description                                                                              |
| --------------------------------- | ------------- | ---------------------------------------------------------------------------------------- |
| `get_traffic_summary`             | `read`        | Aggregate traffic metrics (page views, visitors, sessions, bounce rate) for a date range |
| `get_traffic_trends`              | `read`        | Time-series traffic trends bucketed by hour, day, week, or month                         |
| `get_traffic_realtime`            | `read`        | Live visitor count and recent activity feed                                              |
| `get_traffic_breakdown`           | `read`        | Traffic by device, location, referrer, and UTM parameters                                |
| `get_traffic_entry_exit_pages`    | `read`        | Top entry and exit pages for a date range                                                |
| `get_pages_breakdown`             | `read`        | Per-page performance: views, scroll depth, bounce rate, top sources                      |
| `get_pages_details`               | `read`        | Detailed metrics for a specific page path                                                |
| `get_clicks_breakdown`            | `read`        | Click tracking across all pages — top targets, CTR, UTM breakdown                        |
| `get_clicks_details`              | `read`        | Per-element click data for a specific page                                               |
| `get_forms_breakdown`             | `read`        | Form submission rates and conversion by page                                             |
| `get_forms_details`               | `read`        | Detailed form submission data for a specific page                                        |
| `run_funnel`                      | `read`        | Run a multi-step funnel query with optional dimension breakdown                          |
| `get_funnel_sankey`               | `read`        | Funnel path flows showing where users drop off                                           |
| `get_funnel_suggestions`          | `read`        | AI-suggested funnels for a given landing page                                            |
| `list_saved_funnels`              | `read`        | List saved funnel configurations                                                         |
| `save_funnel`                     | `write`       | Create or update a saved funnel                                                          |
| `delete_saved_funnel`             | `destructive` | Permanently delete a saved funnel                                                        |
| `get_split_test_recommendations`  | `read`        | AI-generated A/B test recommendations for a page                                         |
| `get_ads_attribution`             | `read`        | Full-funnel ad attribution joining spend, sessions, and revenue across Google and Meta   |
| `list_google_ads_connections`     | `read`        | List Google Ads connections for the property                                             |
| `list_google_ads_campaigns`       | `read`        | List campaigns for a Google Ads customer account                                         |
| `list_meta_ads_connections`       | `read`        | List Meta (Facebook/Instagram) Ads connections                                           |
| `list_meta_ads_account_campaigns` | `read`        | List Meta campaigns for a specific ad account with optional performance metrics          |
| `get_meta_ads_daily_insights`     | `read`        | Day-by-day Meta campaign performance breakdown                                           |
| `list_meta_ads_in_campaign`       | `read`        | List all ads within a Meta campaign                                                      |
| `get_meta_ad`                     | `read`        | Full creative metadata for a single Meta ad                                              |

## Setup

**Required:** Humblytics API key and Property ID.

**Where to find them:** [app.humblytics.com](https://app.humblytics.com) → Settings → API.

1. In the Notara dashboard, go to **Tools**.
2. Click the **Humblytics** tile.
3. In Humblytics, go to **Settings → API** and generate an API key.
4. Copy your **Property ID** from the property settings.
5. Paste both into the connector fields and click **Verify & Save**.

Your API key is encrypted at rest with AES-256-GCM.

## Example Prompts

> "How many visitors did we get last week, broken down by day?"

> "What are our top exit pages this month?"

> "Run a funnel from /pricing to /signup and show where users drop off."

> "How are our Google Ads campaigns performing this quarter?"


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://notara.gitbook.io/notara-docs/connectors/humblytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.