Skip to content

Create sync-with-mirror#2523

Merged
amymadden-bit merged 8 commits intomainfrom
amymadden-mirror
Apr 1, 2026
Merged

Create sync-with-mirror#2523
amymadden-bit merged 8 commits intomainfrom
amymadden-mirror

Conversation

@amymadden-bit
Copy link
Copy Markdown
Collaborator

No description provided.

@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 31, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Apr 1, 2026 8:10am

Request Review

@amymadden-bit amymadden-bit marked this pull request as ready for review March 31, 2026 18:07
@amymadden-bit amymadden-bit requested a review from a team as a code owner March 31, 2026 18:07
@amymadden-bit amymadden-bit requested review from argenisf and removed request for a team March 31, 2026 18:07
@amymadden-bit amymadden-bit merged commit fb874a4 into main Apr 1, 2026
11 checks passed
@amymadden-bit amymadden-bit deleted the amymadden-mirror branch April 1, 2026 14:36

\* *User ID or Device ID is technically optional in connector setup, but without one, events can't be linked to a user profile or attributed to a consistent identity.*

Each event supports a maximum of 255 properties. Property names and values longer than 255 characters are truncated.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just noticed this (was from the Original doc which I just corrected)

  1. We should say "Each event supports a maximum of 255 properties. Property names longer than 255 characters are truncated."
  2. One thing I notice using the AI is that it failed to mention data type link here https://docs.mixpanel.com/docs/data-structure/property-reference/data-type
  3. It also failed to perhaps link the technical limits: https://docs.mixpanel.com/docs/data-structure/events-and-properties#what-are-the-limits-of-events-and-properties

Since there are essentially more limits beyond what we state here I think we should at least add that link

For group-level analysis using [Group Analytics](/docs/data-structure/group-analytics), the Group Key (e.g. `account_id`) plays the same role — make sure it's consistent across event and group profile tables.

<Callout type="info">
**Pro tip**: Unlike client-side SDK tracking, Mirror doesn't handle ID bridging automatically. Validate your identity mapping before your first sync, not after. A mismatch across millions of rows is expensive to fix.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thinking we should link the ID management page in "Validate you identity mapping" https://docs.mixpanel.com/docs/tracking-methods/id-management

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants