> 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/best-practices/how-to-dynamically-override-static-tool-constants-in-jentis-using-lookup-tables.md).

# How to Dynamically Override Static Tool Constants in JENTIS Using Lookup Tables

{% hint style="info" %}
Important Maintenance Note:

Newly created tags for this tool added in the future will default back to using the static tool constant set in connector settings. Whenever you add new tags for a multi-language setup, run Multi Tag Edit again or manually assign your lookup table variable to the new tag.
{% endhint %}

When setting up server-side tracking connectors (such as Econda or Dymatrix) in JENTIS, tool constants defined at the connector settings level only accept fixed, static values per domain.

For countries with multiple official languages on the same domain (e.g., Belgium or Switzerland), a static tool constant cannot dynamically report whether a visitor is on the French, Dutch, or German version of your site.

This guide explains how to dynamically override a connector's site language constant using a Lookup Table Variable and Multi Tag Edit in the JENTIS Server Tag Manager.

### Technical Overview

Instead of hardcoding the language at the connector level, you will:

1. Create a variable that reads the active language from the page (e.g., URL path prefix like `/fr/` or `/nl/`).
2. Replace the standard tool constant placeholder across all associated tags using JENTIS Multi Tag Edit.

### Step-by-Step Implementation

#### Step 1: Create a Lookup Table Variable

1. Navigate to Server Tag Manager > Variables.
2. Click Add Variable and select Lookup Table.
3. Set the Input Variable to an element that identifies the active page language (e.g., URL Path, Page Language Data Layer variable, or HTML `lang` attribute).
4. Configure the mapping rules:
   * `/fr/` $$ $\rightarrow$ $$ `FR`
   * `/nl/` $$ $\rightarrow$ $$ `NL`
   * `/de/` $$ $\rightarrow$ $$ `DE`
5. Set a Default Value (e.g., `EN` or `FR`) for any edge cases or unmapped URL patterns.
6. Save the variable (e.g., name it `econda_site_language`).

#### Step 2: Replace Constant via Multi Tag Edit

To avoid manually updating every individual tag, use JENTIS Multi Tag Edit to bulk update all connector tags at once:

1. Navigate to Server Tag Manager > Tags.
2. Click Multi Tag Edit.
3. Select the target tool/connector (e.g., Econda / Dymatrix) and check all tags associated with it.
4. Locate the configuration setting/placeholder holding the default site language tool constant.
5. Replace the placeholder reference with your newly created Lookup Table Variable (`{{econda_site_language}}`).
6. Click Update Tags.

#### Step 3: Test and Publish

1. Open the JENTIS Preview / Debug Mode.
2. Navigate to different language versions of your website (e.g., `example.be/fr/` and `example.be/nl/`).
3. Verify in the tracking console that outgoing server-side requests transmit the correct dynamic language code (`FR`, `NL`, etc.) corresponding to the active page.
4. Publish the container workspace.


---

# 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://docs.jentis.com/best-practices/how-to-dynamically-override-static-tool-constants-in-jentis-using-lookup-tables.md?ask=<question>&goal=<user_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.
