---
title: Pixel Pool
url: "https://b13.com/products/vg-wort-pro-for-typo3/documentation/pixel-pool"
date: 2026-09-19
modified: 2026-09-19
lastUpdated: 2026-09-19
---

# Pixel Pool

![Black icon featuring a stylized letter "A" with sparkles, set against a light blue and green abstract background.](https://b13.com/fileadmin/_processed_/c/d/csm_sharing-ext-VGWortPro-S_9821f76de1.webp)

 Documentation
===============

 TYPO3 Extension “VG Wort Pro”
 Version 0.10.0 (2026-09-19)

  A counting pixel has two codes: a public one, which goes into the page and is what readers fetch, and a private one, which identifies the pixel when you report a text. The field on the page holds only the public code. **A pixel typed in by hand therefore cannot be reported**—the private code is missing, and nothing in the page record can supply it.

The pool is where both halves live. Each site has its own.

  ![The VG Wort module showing a site’s pixel pool: how many counting pixels are still free, how many are assigned to pages, and one that was retired after a rejected report.](https://b13.com/fileadmin/_processed_/6/6/csm_Documentation-Images-pixel-pool-overview_ab05968aa0.webp)

   Getting pixels in
-------------------

  ###  Order through the API

The direct way, and the one without a file.

1. **Web > VG Wort > Pool Management**
2. Select a page inside the target site—the module reads the site from it and uses that site’s credentials.
3. Enter how many pixels you want (1 to 1,000 per request) and order.

The pixels arrive from `/pixel/v1.0/order` and land in the pool in one step, ready to assign. Repeat to replenish; the pool is additive and nothing is ever removed automatically.

Needs `api.enabled`, credentials, and the `order_pixels` permission.

  ###  Import a CSV

The way that works without API access.

1. Download the pixel codes as CSV in the METIS portal.
2. **Web > VG Wort > Pool Management**, select a page inside the site, upload the file.

Expected format—semicolon separated, one header line, both codes 32 hex characters:

     Copy

```
"Öffentlicher Identifikationscode";"Privater Identifikationscode"
"abc123def456...";"789abc012def..."
```

   Upgrading pixels that were entered by hand
--------------------------------------------

If pages already carry pixels that were typed into the field, import the CSV afterwards. The import recognises the public codes, adds the matching private codes, and marks those pool entries as assigned to exactly those pages. From that point the pages can be reported like any other.

This is the migration path—no re-assignment, no touching the pages.

   Several sites, one VG Wort account
------------------------------------

Importing the same CSV into several sites is safe. Per site, the import decides:

- a pixel assigned to a page **on another site** is skipped,
- a pixel matching a page **on this site** is imported as assigned,
- everything else is imported as available.

So the same file can be uploaded everywhere, and no two sites end up claiming the same pixel.

   Retiring a pixel after a rejected report
------------------------------------------

When VG Wort rejects a report in their manual review—most often because the minimum length is not reached once non-eligible parts are excluded—they **deactivate the counting pixel**. It is permanently retired and must never be used again.

**The API does not tell you this.** Rejections go out by e-mail to the owner of the reporting account and nowhere else, so this step is deliberately manual:

1. **Web > VG Wort > Pool Management > Deactivate Counting Pixel**
2. Enter the public code from the e-mail and search.
3. Check the page it names, then confirm.

On confirmation the extension marks the pool entry as deactivated—kept for the record, never handed out again, not counted as available—removes the pixel from the page, and clears that page’s registration data. Then, by default, it assigns the next free pixel so the page starts the workflow again. Uncheck that and the page is flagged `rejected` with the reason stored instead.

Needs the `deactivate_pixels` permission.

**Not every rejection retires a pixel.** If the pixel was not deactivated, the message can be corrected or deleted in the T.O.M. portal and sent again with the same pixel. Nothing needs to happen in TYPO3.

   What the module shows you
---------------------------

Pool statistics per site, the list of assigned pixels with an export, and the pages that have no pixel yet.

The dashboard widget warns before the pool runs dry—see [Backend Module](https://b13.com/products/vg-wort-pro-for-typo3/documentation/backend-module).

  ![The list of pages that carry a counting pixel, each with its public identification code.](https://b13.com/fileadmin/_processed_/9/1/csm_Documentation-Images-assigned-pixels-list_3e6c41c10d.webp)

 Pixel Pool