# Technical Inquiry – First-Party Collector with Combell Shared Hosting

**URL:** https://community.piwik.pro/t/technical-inquiry-first-party-collector-with-combell-shared-hosting/5537
**Category:** Data collection and tags
**Created:** [April 3, 2026, 1:16pm UTC](https://community.piwik.pro/t/technical-inquiry-first-party-collector-with-combell-shared-hosting/5537 "2026-04-03T13:16:14Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Valentin\_W](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/valentin_w/32/4445_2.png) [@Valentin\_W](https://community.piwik.pro/u/Valentin_W)
#### Post date: [April 3, 2026, 1:16pm UTC](https://community.piwik.pro/t/technical-inquiry-first-party-collector-with-combell-shared-hosting/5537/1 "2026-04-03T13:16:14Z")

</div>

Dear Piwik PRO Support Team,

We are currently evaluating the implementation of a **First-Party Collector** for our Piwik PRO instance (hybrid server side tracking). However, we are facing a technical limitation due to our hosting environment at Combell (shared hosting).

### **Context:**

- We want to set up the First-Party Collector for our WordPress multisite (`website.eu` and `website.fr`).

- According to the Piwik documentation, this requires configuring a reverse proxy on our server to forward specific paths (e.g., `/t.js`, `/t.php`, `/containers/`) to your servers.

- Our hosting provider, Combell, does not allow the use of `ProxyPass` or `mod_proxy` on shared hosting.

### **Our Questions:**

1. **Is there a workaround or alternative method**

2. **Are there any specific recommendations** for WordPress multisite setups with shared hosting limitations?

### **Goal:**

We aim to validate the feasibility of implementing Piwik Pro Server Side Tracking in our current multisite.

Thank you in advance for your guidance and expertise.