Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Pixel based tracking and conversion attribution platform for advertisers. Sets a first party identifier cookie, captures page and event signals, and forwards hashed events to ad networks via Conversions APIs.
Pixenio is a pixel based tracking and conversion attribution platform aimed at advertisers and performance marketing teams. It installs a small JavaScript snippet that loads a tracking pixel, sets a first party identifier and listens for events such as page views, add to cart, lead and purchase. The events are sent in real time to the Pixenio backend, which deduplicates them and forwards hashed versions to advertising partners through the Conversions API of Meta, Google Ads, TikTok and similar networks.
Pixenio writes a first party identifier cookie named px_id that stores a unique visitor identifier, plus a session cookie that records the active campaign and traffic source. Each event carries the URL, the user agent, the IP address, the timestamp and a payload that may include the product identifier, the conversion value, the currency and hashed user attributes such as the email address, the phone number, the first name and the last name when the advertiser passes them to the pixel.
The Pixenio pixel is not strictly necessary for the requested service, so Article 5(3) of the ePrivacy Directive requires prior informed consent before the script loads and writes any cookie. The processing of visitor identifiers and hashed personal attributes for advertising measurement relies on consent under Article 6(1)(a) GDPR. The CNIL, the Italian Garante, the German DSK and the Belgian APD have all confirmed that tracking pixels of this kind cannot rely on legitimate interest.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
The Pixenio script must be blocked by the consent management platform until the marketing or advertising category has been actively accepted. Refusal must be as easy as acceptance, the banner must list Pixenio and its downstream partners, and the privacy policy must explain the hashing, the retention and the rights of the visitor under Articles 15, 17 and 21 GDPR. Pixenio also exposes an opt out endpoint that resets the identifier cookie.
Pixenio operates on a global cloud infrastructure with AWS regions in the United States and the European Union. At least one ingestion endpoint is hosted in the United States, and the forwarded events reach advertising partners that are themselves established outside the EEA. Transfers from the EEA rely on the EU US Data Privacy Framework or on standard contractual clauses, complemented by a transfer impact assessment maintained by Pixenio.
Block the Pixenio script behind the consent management platform, use EU ingestion endpoints when available, restrict the event payload to the strict minimum, avoid sending special category data, configure short retention for raw events, sign the Pixenio data processing addendum, document the transfer mechanism, declare Pixenio in the privacy policy and run periodic checks with the browser developer tools to confirm that no event fires before consent is given.
Websites using Pixenio must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is strongly recommended because Pixenio combines visitor identification, large scale tracking and the export of hashed personal data to several advertising partners. Document the scope of the events sent, the hashing method, the retention period, the partners that receive the data and the legal basis for any special category data exposed by the events.
Sample consent text
We use Pixenio to measure the effectiveness of our advertising. This sets a first party identifier cookie and sends hashed events such as page views and conversions to our advertising partners. We need your consent to enable this tracker. You can accept, refuse or withdraw your consent at any time.
Third-party domains contacted
pixenio.comcdn.pixenio.comevents.pixenio.comapi.pixenio.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| px_id | http_persistent | 13 months | First party identifier cookie that stores a unique visitor ID used to attribute events to a single user across sessions. |
| px_sess | http_session | Session | Session cookie that records the active campaign, ad source and landing page during the current visit. |
| px_conv | http_persistent | 30 days | Stores the most recent conversion event reference to deduplicate browser and server side events. |
| px_optout | http_persistent | 5 years | Records the visitor opt out choice so that Pixenio stops setting identifier cookies on future visits. |
Pixenio collects user analytics data — you legally need a consent banner. Try FlowConsent free.
Pixenio sets a first party identifier cookie called px_id that stores a unique visitor identifier, plus a session cookie that records the active campaign and traffic source. These cookies are written by the Pixenio pixel running on the publisher domain.
Yes. The Pixenio pixel is an advertising tracker that writes non essential identifiers and forwards hashed personal attributes. Prior opt in consent is mandatory under Article 5(3) of the ePrivacy Directive. The script must remain blocked until the visitor has accepted the marketing category.
Consent under Article 6(1)(a) GDPR for the cookies and the hashed events. If the events expose special category data such as health, religion or political views, explicit consent under Article 9(2)(a) GDPR is additionally required.
Yes. At least one Pixenio ingestion endpoint is hosted in the United States, and the events reach advertising partners like Meta, Google or TikTok that are also US based. Transfers from the EEA rely on the EU US Data Privacy Framework or on standard contractual clauses, with a transfer impact assessment.
Yes. The combination of visitor identification, large scale tracking and the export of hashed personal data to multiple advertising partners triggers Article 35 GDPR. A DPIA must cover the scope of events, the hashing, the retention, the partners and any special category data risk.
Load the Pixenio pixel through your consent management platform only after the marketing category has been accepted, restrict the event payload to the strict minimum, avoid special category data, sign the data processing addendum, prefer EU ingestion endpoints and document the transfer mechanism.
Alternative pixel and Conversions API products include Meta Pixel paired with the Meta Conversions API, Google Ads Enhanced Conversions, TikTok Events API, server side Google Tag Manager and Stape. All of them face similar GDPR obligations.
Add a dedicated entry for Pixenio, list the px_id and session cookies, describe the retention, mention that hashed events are forwarded to the advertising partners chosen by the publisher and provide a direct link to the Pixenio privacy notice and the opt out endpoint.