Hi MP community, Quick question about server-side implementation: I'm passing several client-side properties to the backend, and then triggering Mixpanel events from the server. I'm using Mixpanel's reserved property names in the payload — for example:
{
"$browser_version": "119.0.6045.199",
"$device_id": "abc123-device-id",
"$screen_height": 1080,
"$screen_width": 1920,
"$current_url": "
https://example.com/products/1",
"current_url_path": "/products/123",
"$referrer": "https://google.com"
}
Is it okay to use these reserved keys manually in a server-side event payload? Will Mixpanel treat them the same way as if they came from the client SDKs? Or is there any limitation or potential conflict I should be aware of?
Hello Mixpanel community,, I’m running into an issue with Mixpanel: In the UI, the Browser column shows (not set) — but when I expand the event details, I can see that the Browser is correctly set to Chrome in the Mixpanel Properties JSON. Setup context:
This is a server-side implementation.
The client sends browser info (e.g., Chrome) to my backend, and then the event is triggered from the server using that data.
Screenshot attached (You can see Browser: Chrome in the detailed view, but not in the table column.) Questions:
Why does the Browser column still show (not set)?
Is this because the browser info isn’t coming from the Mixpanel client SDK directly?
Can we somehow promote or map our custom browser field to appear in the column?