This tutorial covers how to set up Sources and Destinations, as well as a reverse ETL Demo and Q&A. 

Q&A

1. Do you recommend using the server or javascript to perform these?
   1. This comes down to your use cases.. If you are looking to do more front end website tracking and tracking other similar events, Javascript might be the option for you. If you’re looking more at back end events, more secure type of events (ex: order completions, opened an account) > server side tracking is likely what you’ll want
2. Can you talk more about custom integrations? What happens if Segment doesn’t have an integration in the catalog that I need?
   1. We have the ability to create custom integrations using either Source Functions or Destination Functions. If you’re looking to use Functions, check out Functions Copilot which helps you generate JavaScript code for functions using natural language prompts.
3. Does Segment check for data semantics etc.
   1. Yes, with Protocols (our data governance tool).  You’d be able to set up a tracking plan to enforce naming conventions, block certain events, create violations for certain events, create transformations etc.
4. Can you talk a little about using Segment without a data warehouse vs with a data warehouse? 
   1. Seeing the full scope of both sides working with alot of growth customers… What I’m seeing with DW is just more flexibility because you're doing the configurations, running the queries, building the models. Additionally, as your enterprise grows you’ll be collecting a lot more data, storing a lot more data - it becomes a critical part of your tech stack as time goes on. 
5. What kind of error handling is available with direct connected warehouses? Redshift specifically?
   1. Currently you’ll see errors if syncs are not working (sync failed error). We don’t have much error handling outside of sync status, syncs failing, events not uploading.