---
title: "Custom Service"
manual: "Klaro! Consent Manager"
version: "3.0"
permalink: "https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:howto-custom-service@3.0"
source: "Integrator/HowTo/CustomService/Index.rst"
rendered: "2026-09-24T10:59:28+00:00"
---

# Custom Service {#howto-custom-service}

-   [Backend](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:backend@3.0)
-   [XLIFF](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:xliff@3.0)
-   [Frontend](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:frontend@3.0)

## Backend {#backend}

Create your new service (for example with the name `mycoolservice`) as a new
[service record](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:for-editors-service@3.0) in the backend:

![Custom Klaro service record in the TYPO3 backend](../../../Images/HowTo-CustomService-Backend.png)

## XLIFF {#xliff}

In your [custom XLIFF](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:howto-reference-xliff@3.0) file, create new labels
for your custom key:

```xml
<trans-unit id="services.mycoolservice.title">
    <source>My Cool Service</source>
</trans-unit>
<trans-unit id="services.mycoolservice.description">
    <source>This is the description of the new service.</source>
</trans-unit>
```

## Frontend {#frontend}

If the service was referenced in the [Klaro configuration](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:for-editors-configuration@3.0), it also appears in the Consent Management modal
in the frontend.

![Custom service displayed in the Klaro consent modal](../../../Images/HowTo-CustomService-Frontend.png)