Event $ff-accepted-invite

[gstout52]

Current Behavior

With PR #4381 , tracking of accepted invites in PostHog under the event name $ff-accepted-invite was moved server-side to improve reporting accuracy. As of August 26, no activity is shown with $ff-accepted-invite: https://eu.posthog.com/project/2209/insights/SC2qeQaU

Expected Behavior

When a user accepts a team join invitation, that action should be recorded under $ff-accepted-invite.

Steps To Reproduce

See PostHog chart: https://eu.posthog.com/project/2209/insights/SC2qeQaU

Environment

n/a

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[cstns]

Could not find anything wrong with the mentioned pr or the telemetry configuration in production.

I was able to trigger the $ff-accepted-invite event using my local setup hooked up to the staging environment on posthog which captured it successfully.

After doing a similar test on production, the flow appear to work successfully (had no way of checking logs or outbound events) but the event was not visible on posthog production project.

Messing with the $ff-accepted-invite insight and disabling the 'Filter out internal and test users' filter, I was able to find my event among others from the 27' of august and onward.

Posthog is not something I'm extremely familiar with, @joepavitt could you please take a look and investigate further

[joepavitt]

Thanks @cstns - can confirm that PH has been receiving these events in production, you can see that via the "Activity" tab on the left, and then select the $ff-accepted-invite in the filter:

As for why they're being treated as internal/local though, that's a trickier one, these are the filters we have applied:

I can see from the original Insight shared, that it's not every accepted invite being filtered.

Update:

Ooh, okay, I've found the problem. We identify the user in this event via their e-mail address, not their username as done when they register. Entirely my fault when setting this up. @cstns can you check if we have access to their username at this point and fix this please?

It's setting up a new user with the same e-mail, but a different PostHog ID/Person. That new person then doesn't have the properties required to be identified as a "Real User", and is instead being classified as a Bot, so being excluded from the charts.