> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/destinations/destinations-catalog/tableau-online.md).
# Tableau Online
For this connector, the concept is to send to Tableau each X minutes new events in **append** mode (ex : pageviews, clicks, impressions, ...)
We are able to push Data to Tableau every 10 minutes (full export or delta).
\
Append mode will add new lines to existing table in Tableau, so the stream has to be configured to **differential** (export only new events), like this :
\
For **users** universe, it's different, you can't choose "append" because users are updated continously and you don't want to add each times the same users, so you have to choose **overwrite** mode for this univers, with an export each night (because it will take hours to send all users to Tableau) (edited)
\
Tableau online doesn't support updates\
It offers only append or overwrite
### Help to fill the connectors input :
\
**Url Server**\
The URL for the Tableau server on which the data is published.\
For Tableau Online, specify [https://online.tableau.com](https://online.tableau.com/).\
\--\
**Site name**\
The site id is independent of the site name, and it is indicated in the URL when you view the site in a browser. For example, if the URL for the page you see after signing in to Tableau Online is\
\
the site id is vernazza.\
\--\
**date source name**\
The name of the data source, as published to Tableau Online.\
\--\
**username**\
Valid Tableau Online user.\
\--\
**password**\
The password for the specified Tableau Online user.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.commandersact.com/features/destinations/destinations-catalog/tableau-online.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
