# Serverside Tracking - Session exceeded max configured length

**URL:** <https://community.piwik.pro/t/serverside-tracking-session-exceeded-max-configured-length/3954>\
**Category:** Data collection and tags\
**Created:** [April 28, 2024, 9:39am UTC](https://community.piwik.pro/t/serverside-tracking-session-exceeded-max-configured-length/3954 "2024-04-28T09:39:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bi\_Bass](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/bi_bass/32/3379_2.png) [@Bi\_Bass](https://community.piwik.pro/u/Bi_Bass)\
**Post date:** [April 28, 2024, 9:39am UTC](https://community.piwik.pro/t/serverside-tracking-session-exceeded-max-configured-length/3954/1 "2024-04-28T09:39:43Z")

</div>

Hello,

we send our requests via own serverside app. The target is to count requests, like e.g. clicks on links vs. clicks on buttons. User recognition is not wanted. Each request should be assigned to a new user and to new session - only one request needs to be recorded in each session. IP adress ist constant. That’s the theory and actually it’s going well, but…

There are a lot of requests “Session exceeded max configured length”.  
Every request have following parameter:

method: POST,  
query\_params: {  
{  
“cs”: “UTF-8”,  
“dimension14”: “[https://domain/](https://domain/)…”,  
“e\_a”: …,  
“e\_c”: …,  
“e\_n”: …,  
“h”: “09”,  
“idsite”: “…”,  
“lang”: “de-DE”,  
“m”: “38”,  
“rec”: “1”,  
“s”: “18”,  
“send\_image”: “0”,  
“ua”: “…”,  
“uid”: “1714289898270”,  
“url”: “…”,  
“urlref”: “[https://www.google.com/](https://www.google.com/)”  
}  
uid = timestamp. So every neu request have neu unique uid.  
cip not provided

Why is the user recognized again and the session continues to be written?

 ![session exceeded](https://europe1.discourse-cdn.com/flex005/uploads/piwikpro/original/2X/0/060b07db94a05a37074d4011750fa1c3c153745e.png)

On the screenshot you can see, it will be searching for the Visitor ID = “6a278427f6aded94”, but all users on the screenshot have another Id´s. Uid is always different.

---

<div class="post-metadata">

**Author:** ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)\
**Post date:** [April 28, 2024, 9:46am UTC](https://community.piwik.pro/t/serverside-tracking-session-exceeded-max-configured-length/3954/2 "2024-04-28T09:46:26Z")

</div>

Hi @Bi_Bass,

> [@Bi\_Bass](#):
>
> IP adress ist constant.

Not sure if that’s supposed to be `is` or `isn't` 😅.

My guess is that you have session hash enabled and since each request is sent by the same app/machine each event is added to the same session.

You can either disable the session hash in the Administration settings of your Piwik PRO site or use the `sh` [HTTP Tracking API](https://developers.piwik.pro/en/latest/data_collection/api/http_api.html) parameter to disable it on-demand:

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/piwikpro/original/2X/a/acdf0811ae7456a8147537dcb11f09ea35fc9688.png)

---

<div class="post-metadata">

**Author:** ![Bi\_Bass](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/bi_bass/32/3379_2.png) [@Bi\_Bass](https://community.piwik.pro/u/Bi_Bass)\
**Post date:** [April 28, 2024, 9:53am UTC](https://community.piwik.pro/t/serverside-tracking-session-exceeded-max-configured-length/3954/3 "2024-04-28T09:53:33Z")

</div>

Hi Antoni!  
Thank you for the support on Sunday. 😀  
Thanks for the tip. We’ll try it out.

---

<div class="post-metadata">

**Author:** ![anthonybartczak](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/anthonybartczak/32/2430_2.png) [@anthonybartczak](https://community.piwik.pro/u/anthonybartczak)\
**Post date:** [April 28, 2024, 10:15am UTC](https://community.piwik.pro/t/serverside-tracking-session-exceeded-max-configured-length/3954/4 "2024-04-28T10:15:11Z")

</div>

By the way, would you mind providing 2 tracking requests from the same session? Either here or in a private message.

Even with session hash enabled I think that the change of user ID should result in a session split.

---

<div class="post-metadata">

**Author:** ![Bi\_Bass](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/bi_bass/32/3379_2.png) [@Bi\_Bass](https://community.piwik.pro/u/Bi_Bass)\
**Post date:** [April 28, 2024, 10:16am UTC](https://community.piwik.pro/t/serverside-tracking-session-exceeded-max-configured-length/3954/5 "2024-04-28T10:16:29Z")

</div>

The IP ist almost always the same.

 ![ip](https://europe1.discourse-cdn.com/flex005/uploads/piwikpro/original/2X/e/e8fde6975c7bd7e2c49c63475619e167f2e63af8.png)  
As you can see, Visitor ID, User ID and Cookie Id are always different.  
For my understanding, in this case every new request belongs to the new visitor and new session should be opened. But we will adjust Administration settings und extra use sh=0 in the request.

---

<div class="post-metadata">

**Author:** ![Bi\_Bass](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/bi_bass/32/3379_2.png) [@Bi\_Bass](https://community.piwik.pro/u/Bi_Bass)\
**Post date:** [April 28, 2024, 10:22am UTC](https://community.piwik.pro/t/serverside-tracking-session-exceeded-max-configured-length/3954/6 "2024-04-28T10:22:32Z")

</div>

As soon as a solution is found, I will also post it here for the community