Client- vs. server-side ingest endpoints

[muety]

The docs mention three different endpoints for ingestion:

1. /ingest
2. /ingest/server
3. /ingest/server/pageview

Can you clarify specifically the difference between (1) and (3) and explain when to use what? The latter one seems to be the "go to" endpoint for server-side tracking, but it's not clear to me how using it is beneficial over (1). Also, why doesn't its payload specify the UTM fields?

Btw., the endpoint is not included in the openapi.json.

[PascaleBeier]

The docs are (right now) being updated to 2.4.0, which brings a proper server side ingestion documentation and endpoint, but the UTM fields are derived from the url.

I'm still considering if this is too clever. (Also this is currently not clear, as I'm
still moving things around)

https://hitkeep.com/guides/tracking/server-side-tracking/

This is the current preview

[PascaleBeier]

This should be much clearer in both specs and public documentation.