Segment + Amplitude: Best Practices

Frequently Asked Questions: 

• How do we avoid sending “Viewed /-” or “Loaded a Page” events to Amplitude?

• What settings should we enable in the Amplitude Destination for Page/Screen calls?

• What is the difference between Segment’s Cloud Mode vs. Device Mode? 

• What are the pros + cons of using Amplitude’s client-side bundled Segment integration? 

• How do we set session in Amplitude while using Segment in Cloud Mode?

• I set up the Amplitude Destination in Segment - why am I not seeing any data in Amplitude?

• What is Amplitude’s definition of a Session? 

Handy Resources: 

Note: for Segment Support: please contact your designated Segment Rep or Segment support (friends@segment.com) 

• Getting Started with Segment  

• Segment Tracking Plan (for all Segment customers)

• Introduction to Segment Guide 

• Segment/ Amplitude Developer Docs

• Segment Product Docs

• Segment Developer Docs

• Segment + Amplitude Recipes

• Maximize the ROI of your Data Management Platform | January 2021

About the Author!  

My name’s Sam, Solutions Engineer @ Amplitude.

As a self-professed in-house Amplitude+Segment SME, I spend a TON of time troubleshooting, instrumenting, and debunking the inner workings of our dynamic partnership with Segment.

Over the past 4+ years as partners, we’ve experienced strong market pull for Segment and Amplitude, creating a deep base of mutual customers. 

Joint customers can also take any user-level data in Redshift, BigQuery, or Snowflake and push into Amplitude to enable deeper analysis.  By leveraging Segment, the TTV for a tool like Amplitude is reduced greatly and potential data silos are removed.