You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, there is a difference between groupIdentify and groups - for server side SDKs we don't "attach" groups to the user as the $groups property has to be sent with every event and hence it is generally a client-sdk thing.
For server side you call $groupidentify to set properties on that group. When capturing events for a given user you would specify the property $groups: { [key]: value }. Those $group_type,$group_key,$group_set properties are unique to the $groupidentify event and are ignored for normal events.
Ah I see, so groupIdentify doesn't set the group for the rest of the session, makes sense. However that creates an invalid "person" in PostHog, is that expected?
As for the fix you suggested for events (not groupIdentify), it works, thank you!
groupIdentify()
doesn't workIt pushes events that are attached to a broken user:
Full payload:
The problem lies here:
I think this line is wrong:
posthog-php/lib/PostHog.php
Line 98 in 9010c6d
$group_type
in capture is not workingBecause of the problem above, I tried attaching the group to every event instead:
The event is now attached to the user but not the group.
Full payload:
If we only look at user and group-related data:
That looks incorrect. If I compare to an event reported by the web (JavaScript) SDK:
Properties don't look formatted the same way.
Is the PHP SDK using an obsolete format for the events API?
To be clear:
web
SDK are attached to the groupThe text was updated successfully, but these errors were encountered: