Openpanel-dev / Openpanel-dev/openpanel
identify is not working
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7k
- Forks
- 481
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 21
Description
Hello folks. Nice product.
So, here's my problem. Looks like identify is not working properly. I have a self-hosted instance and a Django application.
Looking at the documentation on the main site and in the Python SDK, there is a divergence. I've tried both if I remember correctly, but none worked (https://github.com/Openpanel-dev/python-sdk/issues/2).
Here's my identify method:
def identify_openpanel(user: User) -> None:
profile_id = str(user.pk)
op = get_openpanel()
if op:
traits = {
"firstName": user.first_name,
"lastName": user.last_name,
"email": user.email,
"properties": {
"organization": None,
"last_login": user.last_login,
},
}
op.identify(profile_id=profile_id, traits=traits)
We are experimenting with tracking also from the front-end side, but mostly will perform tracking with backend.
You can see from the screenshot below that we are tracking correctly (popular events is filled in) and it's getting associated with current user when doing these actions. Is there any configuration we have to tweak?
Contributor guide
No contributing guide indexed for this repository
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 by comparing the main-site documentation with the Python SDK guidance and the linked Python SDK issue #2, then inspect the identify call shown in this report. Reproduce it with the self-hosted instance and Django application; done means identify succeeds and the user profile traits appear consistently with tracked events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- analytics, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100