> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/data-activation/connectors/hubspot/client-side-implementation-details.md).

# Client-Side Implementation Details

Hubspot in JENTIS can be implemented in two separate ways on the client-side. Please make sure that you do not mix the two approaches, and you only use either.

### Implementation **with** Hubspot Base Tag

If you configure and add the base tag to be triggered on all pages, then the Hubspot Tracking code library code snippet is loaded and it will track all page views and other form related events, automatically.

In this case all Hubspot cookies will be added to the page by their library.

### Implementation **without** Hubspot Base Tag (Hubspot cookieless)

You can choose this way for implementation if you would like to avoid the Hubspot tracking code library setting any cookies on your page.

The following 4 tags need to be setup:

1. `Pageview`: This tag is used to track page views on your website. Should be triggered on all pages.\
   Trigger: 'Pageview without exclude'
2. `Pageview with form`: This tag is used to track page views on your website where there is also a Hubspot Form included.\
   Trigger: 'Pageview with Hubspot form'
3. `Pageview with form visible`: This tag is used to track when a Hubspot form becomes visible for a user on your website.\
   Trigger: 'Pageview with Hubspot form visible'
4. `Form interaction`: **This tag is mandatory to track previous page views to a Hubspot form submit.** It also tracks when a user has interacted with a Hubspot form.\
   Trigger: 'Hubspot form submit'

It is important to clarify that the Hubspot form's implementation JavaScript snippet handles the actual form submission to Hubspot.


---

# 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://docs.jentis.com/data-activation/connectors/hubspot/client-side-implementation-details.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.