Thanks for posting here @CCrowley and excuse the delay. Here are some potential pitfalls to keep in mind: 

• Respecting user privacy and being transparent about what data you’re collecting
• Ensuring data quality and filtering out any events that don’t represent real user behavior
• Selecting the right metrics that provide actionable insights 
• Not over-instrumenting with irrelevant events or properties; keep your implementation simple

I hope this helps! 

Thanks, @Jeremie Gluckman! I think your list can apply to any use of Amplitude Analytics. I was looking more specifically for ways a component library may differ from other applications. But your points are all valid and important to remember.

Thank you!

Thanks for the feedback @CCrowley. Please let us know if you need anything else!