Welcome to Segment's Community! Here's everything you need to know.
Connect, Learn, Share, Build
Get answers to your questions and help others
Browse tutorials and other helpful resources
Register for webinars, office hours, and more
I was unable to attend Monday’s (4/15) webinar titled “Empower Your Team with Key Insights on ID Resolution and Profile Integrity”. Is it possible to get a link to the recording of that event? I accidentally permanently deleted the email that contained that link.
In this on demand session, Solution Architects Kurt & Anthony, cover:An in-depth look at the ID resolution process within Segment The significance of ID resolution in creating unified customer profiles Best practices for crafting and implementing ID resolution rules… like how to set up these rules in Segment, while avoiding common pitfalls Strategies for ensuring the effectiveness of ID resolution rules with tools and techniques for rule validation and maintenance in Segment Identifying corrupted profiles with practical steps Building trust through transparency and accuracy in your ID resolution process, along with continuous monitoring and quality assurance best practices, and ending with a Q&A session
Delivery Overview for Streaming Connections now GA With Delivery Overview, you can verify that your source receives your events, that any filters and Tracking Plans work as expected, and that events successfully flow to your destination. You can use Delivery Overview’s pipeline view to identify any event delivery errors or unexpected behavior, leading to quicker resolution of data quality issues. Source Volume Alerting for Streaming Sources now GAWhen viewing a source, access the Alert tab and provide a % threshold to alert against positive or negative changes in the event volume emitted from the source compared to the previous 24 hours. For example, if you set a change percentage of 4%, Segment notifies you when your source ingests less than 96% or more than 104% of the typical event volume.Additionally, for this new alert and the preexisting Destination Delivery alert, you can now specify a specific email address as the recipient for a triggered alert and/or a Slack channel of
Hello! I’m new to Segment and want to make sure we’re implementing user ID best practices.According to this document:A userId should be a robust, static, unique identifier that you recognize a user by in your own database systems. We anticipate sending events to Segment from multiple products, each of which has their own user database. Should each product use its own user IDs as the Segment user IDs? More concretely, suppose we have a user who has created accounts in product A and product B. They used the same email address when they created each account. Since product A and product B have different user databases, this user has two user IDs: uuidA and uuidB. When we send events for this user to Segment from product A, should the user ID be uuidA? That would mean we have two Segment users (uuidA and uuidB) that correspond to one user.Thanks in advance!
Simple question (I think)...is the screen call automatic on mobile with each screen change? Or does it have to be called manually? This section says:Segment automatically calls a Page event whenever a web page loads. This might be enough for most of your needs, but if you change the URL path without reloading the page, for example in single page web apps, you must call Page manually...but the subsequent section on screen does not mention one way or another.
Hey folks, sharing a discussion that kicked off in this thread about integrating Segment events into a data warehouse + bringing those events into data visualization tools. Sharing in case the conversation is helpful for others:At Wave, our team is just starting to tap into the potential of Segment events in our Redshift data warehouse - since we brought them into the warehouse a couple of month ago.We use Looker as our data visualization platform so there’s an added layer of complexity bringing Segment events into that platform in a way that is properly modelled and ready for presentation to stakeholders.Would love to hear of any other experiences others have had bringing Segment data into your warehouse and data visualization/dashboarding tools.
Since RETL was released I am debating whether or not RETL is a replacement for SQL Traits. What you think?
AboutBuilding a scalable and trustworthy model for identity resolution is challenging to say the least. It requires a consistent approach, a true universal identifier, and a flexible real time rules engine for profile merges.In this webinar, our Sr Data Scientist, Nathan Wang highlights how a deterministic approach for identity resolution, leveraging first-party data, enables 100% reliable profile unification.We'll demonstrate how to build rigidity around what should be fixed so that data science teams can focus on the highest impact areas for their specific business.AgendaKey considerations for data teams regarding identity resolution How to simplify the approach of building your data pipelines Pros and cons of building vs buying How to construct an effective ID graph Register here
Hey all -- we have a few different platforms that we push data into that aren’t native Segment destinations. For these, we rely on the Webhook Actions destination to create these integrations. One issue we’re experiencing is a fairly quick time-out rate that’s preset within these destinations. In short, if there’s no response from the endpoint we POST to within 5s, Segment auto-retries the request. What we’re seeing in actuality is that the endpoint is successfully receiving the request from Segment but due to some added platform latency, the response isn’t getting back to Segment in time. This causes multiple retries and duplicate data or actions to be taken by the destination platform. For the group, has anyone found a way to creatively solve for this retry rate? For the Segment Team end, is there the possibility to allow for configurable retry rates?
Hey, I’m Chris the Senior Marketing Operations Manager at Wave. I’ve worked in Segment at multiple career stops and we are just over our 1 year mark of onboarding with Segment here - and hopefully should finish implementation in another year with a ton of legacy items and connections to think about, as we look to send data to about 20 systems downstream and really empower our customer facing teams to know more about our customers.Outside of managing the Ops team, I live on a farm in what I like to refer to as the capital of the middle of nowhere - Commanda, where no cell service or wired internet can find me. Remote since before it was cool (2016), and proud Starlink customer. Casper (left), Riley (right)
Browse our docs or submit a ticket to support
Level up your Segment knowledge
Discover unique use cases across our product suite
Articles, whitepapers, customer stories, and more
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
