PostHog / PostHog/posthog-elixir
Add server-side group_identify helper
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Elixir
- Stars
- 65
- Forks
- 30
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 16
Description
Summary
Add a public server-side group identify helper.
Why
sdk-specs marks group-identify as applicable to both client and server SDKs. Server SDKs commonly expose this directly to create/update group profiles.
Current status
No public group identify API is present in public_api.snapshot.
Suggested scope
- Add an idiomatic Elixir API for
$groupidentify. - Accept group type, group key, and optional group properties.
- Emit
$group_type,$group_key, and$group_set/properties according to backend SDK behavior. - Support an optional distinct ID or synthesize one from group type/key if omitted.
- Route through normal capture/batching and future
before_sendhook. - Add tests and docs.
References
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with public_api.snapshot and the referenced sdk-specs group-identify specification, then trace the normal capture and batching entry points. Done means a public server-side helper emits the specified group fields, handles the optional distinct ID and properties, routes through capture/batching, and includes tests and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- analytics, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100