> For the complete documentation index, see [llms.txt](https://developers.getgeoflow.com/geoflow-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.getgeoflow.com/geoflow-docs/feature/optional-settings/meta-tags.md).

# Meta Tags

### Ignore Visitor Data Properties

Define a comma-separated list of the visitor data properties you would like to have ignored.

The property name is case-sensitive and must match the 'Property Variable' noted in the [Visitor Data Properties table](/geoflow-docs/overview/visitor-data-properties.md). The properties added here will be excluded from the 'geoflow' JS object.

```html
<meta name="geoflow-ignore" content="countryName, countryCode">
```

### Send The Visitor Data Somewhere

Define an endpoint that you would like the visitor data properties sent to when the visitor leaves your website. The endpoint must be a valid secure URL (including the https\:// part and a TLD); it can be anything that supports accepting a POST request (e.g. Zapier webhook).

If the URL that you provide is not valid, an error will be displayed in the browser console.

We recommend using our preferred webhook provider, [Hookdeck](https://hookdeck.com/), for your data endpoint.

```html
<meta name="geoflow-endpoint" content="https://hook.example.com">
```

### Script Extensions

Script extensions allow you to extend the functionality offered by the default Geoflow script without writing a single line of code.

Learn more about the different [script extensions](/geoflow-docs/feature/script-extensions.md).

```html
<meta name="geoflow-extensions" content="performance, marketing-params">
```

{% hint style="info" %}
**Developer Tip**: The \<meta> tags are helpful if you would like to adjust the default functionality on a page-level basis. The \<meta> tag will be ignored if the data attribute for the same optional setting is also applied to the Geoflow \<script> tag.
{% endhint %}


---

# 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://developers.getgeoflow.com/geoflow-docs/feature/optional-settings/meta-tags.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.