kapa.ai

The knowledge sources do not mention any grace period or overlap where both the old and new project API secrets work at the same time.

All that’s documented is:

There is no explicit statement that the old secret remains valid after reset, nor that there is any overlap window. For an authoritative answer on behavior at the exact moment of rotation, you’d need to contact Mixpanel Support.

Sorry Denny J., I'm not sure what you mean. Please try again. 👋

You can rotate (reset) a project’s API secret yourself from the Mixpanel UI:

This will generate a new project secret; you’ll then need to update any scripts or integrations that authenticate with the old secret.

The docs are explicit about when events can be attributed to groups, but they do not say that group_set timing affects that attribution.

What is documented:

The docs do not state that you lose attribution for events that:

just because group_set was added later. In other words, as long as the group key existed in Project Settings at ingestion time and the events carried that property, those events should already be attributed to the group; adding group_set later just creates/enriches the profile object.

What you can do now:

Because the docs don’t explicitly describe any limitation tied to late group_set (only to late group key setup), I can’t point to a statement that says those events will or won’t be back-attributed based on when you start calling group_set. The only hard cutoff the docs guarantee is the date the group key was added to Project Settings.

You’re correct: based on the docs, you cannot retroactively attribute past events to groups if the group key wasn’t fully set up.

Two separate constraints apply:

Putting those together:

So, as far as the documentation shows, there is no supported way to backdate group profiles to retroactively attach past events that were not already attributed to a group at ingestion time.