diff --git a/pages/docs/data-structure/events-and-properties.mdx b/pages/docs/data-structure/events-and-properties.mdx index 9bf1468d88..b5713cbc87 100644 --- a/pages/docs/data-structure/events-and-properties.mdx +++ b/pages/docs/data-structure/events-and-properties.mdx @@ -45,7 +45,7 @@ We recommend striking the right balance when defining your events. Events should * If your goal is to track different buttons from different user journeys: instead of tracking 1 event `Button Clicked` with `Button Name` property set to **"Play"**, or **"Profile"**, or **"X"**, track them as different events `Song Played` and `Profile Updated` and `Logout` with specific properties for each event to provide richer context. -### Name Events and Properties Consistently +### Use a Naming Convention for Events and Properties Mixpanel strings are case-sensitive; `sign_up_completed` and `Sign_Up_Completed` are considered two separate events.