Check a product analytics event list for naming drift, vague events and personal data in properties.

After: what comes back

The first lines of a real run on that input. Nothing here is edited by hand.

6 events, 5 high, 2 medium, 3 low. Dominant style: snake_case.

HIGH   event names use PascalCase (1), snake_case (3), Title Case (1), single word (1); pick one (snake_case is the most used here)
HIGH   SignUp: property "email" looks like personal data; hash it, use an id, or leave it out
HIGH   user_signed_up: means the same as SignUp; two names for one event split the data
HIGH   purchase_completed: property "phone_number" looks like personal data; hash it, use an id, or leave it out
HIGH   page: too vague to answer a question; name the object and what happened to it (checkout_button_clicked is still weak; checkout_started is better)
MEDIUM Button Clicked: names a UI element or embeds a number; track the meaning (what the person did) and put the element in a property
MEDIUM 3 events use a past-tense verb and 2 do not (sign_up against signed_up); events record something that already happened, so use past tense
LOW    checkout_started: no properties listed while other events have them
LOW    page: no properties listed while other events have them
LOW    no event lists user_id, anonymous_id, timestamp, platform; if the tool adds them automatically, note that in the plan
... full output on the tool page