Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(docs): mobile considerations for identified events #10227

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+18 −0
Open

feat(docs): mobile considerations for identified events #10227

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions contents/docs/data/anonymous-vs-identified-events.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,24 @@ import HowToCaptureIdentifiedEventsFlutter from '../product-analytics/_snippets/
</Tab.Panels>
</Tab.Group>

## Mobile SDK version considerations

When using PostHog's mobile SDKs, any changes made to `personProfiles` configuration will only apply to users who have updated their app to the latest version. This is because mobile SDKs are bundled with your app and cannot be updated dynamically.

**Impact on existing users:**

Users running older versions of your app will continue using the `personProfiles` configuration that was bundled with their installed version, even after you release updates with new configurations.

**Managing version differences:**

To ensure consistent behavior across your user base, you can:

1. Use feature flags (with a version payload) to detect users running outdated app versions
2. Implement an update flow to guide users to install the latest version
3. Consider making app updates mandatory for critical changes

This will help maintain consistency in how person profiles are handled across your entire user base.

## Frequently asked questions

### What can and can't I do with anonymous events?
Expand Down
Loading