> 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/raw-data-exports/raw-data-tag-configuration-use-cases.md).

# Raw Data Tag Configuration Use Cases

## Raw Data configuration use cases

Use the Raw Data tool to export standard and custom tracking values. This guide covers two common configurations:

1. Add the landing referrer to the session document.
2. Export a dedicated event when a specific trigger fires.

Configure and test each tag in JENTIS Tag Manager before publishing.

### Add the referrer to the session document

Use the default **Session** tag when the Raw Data Connector is installed and customize it. As the referrer should be available with session-level data. The tag writes the value as a custom property in each exported session document.

#### Create the custom property

1. Open the Raw Data **Session** tag in JENTIS Tag Manager.\
   ![](https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2FcSHSYOwpgAlNcU9rZl6U%2Fimage.png?alt=media\&token=6e831a03-6401-4c33-9e9c-2e2831ae38f7)
2. Add a custom property (String) with key `session_referrer`.\
   ![](https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2FtTtqm7gkMu5IUhIW6hdt%2Fimage.png?alt=media\&token=a3fa7683-ccb5-4359-9ed6-53a27ffc87ba)
3. Set the property value to the default variable named `Referrer`.
4. Save the tag.

The export stores the value as `property.session_referrer` in the session document. You'll find it in the CSV files column "session\_referrer" or in the JSON file property "session\_referrer".

### Export a custom event on a specific trigger

Create a dedicated **Event** tag when a value should be exported only after an event occurs. Examples include form submissions, sign-ups, or checkout completion.

#### Create the event tag

1. Create a new tag for the Raw Data tool. Navigate to the JENTIS Tag Manager: Tags section. Add a new tag and select your Raw Data connector instance. 
2. Select the **Event Data** tag template.
3. Give the tag a clear name, such as `Newsletter signup`.
4. Add the event properties required for the export, you can also set static defaults that identify this event if it isn't a generic event (ie. triggered only on the specific Newsletter Signup event)\
   ![](https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2FgpsehiftRMikwHU3dcb3%2Fimage.png?alt=media\&token=d037eac4-088a-4303-b834-8e656bc5bc10)
5. Continue to select the appropriate trigger for your configuration.

Common event properties include:

* `event_name` — identifies the event, such as `newsletter_signup`.
* `event_group` — groups related events, such as `engagement`.
* `event_value` — carries an optional event value.

#### Assign the event trigger

1. Create or select a trigger for the required event.
2. Define the condition that identifies the event.
3. Assign that trigger to the Event tag.
4. Save the configuration.

The Raw Data tag fires only when its assigned trigger matches. The export then contains a new event document (JSON and CSV files) with the configured properties.

### Validate the configuration

Use the JENTIS Container Preview to verify that the correct tag fires. Check that the Session tag contains `property.referrer`. Check that the Event tag fires only for its intended trigger.

After publishing, Raw Data exports include the configured documents during the next export cycle. See [Configuration of Raw Data Exports](/raw-data-exports/configuration-of-raw-data-exports.md) for setup and export availability.


---

# 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/raw-data-exports/raw-data-tag-configuration-use-cases.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.