What is your primary use case for Segment?

My main use case for Segment is to share a practical experience about how we used Segment at XP Investimentos bank to transform behavioral data into business intelligence and high-impact marketing campaigns, where we worked in the MarTech arm with a very clear goal: to turn Segment into our CDP, making it the main source of truth about our customers while understanding how they interacted with the XP app to personalize the end-to-end experience. Before giving a specific example of how I used Segment to personalize customers' experience in the XP app, I will talk about the challenge and the technological solution, where my role as a software engineer was directly tied to implementing, maintaining, and optimizing this pipeline. I knew the tool very well inside and we created and configured sources, structured the receipt of events via HTTP calls or webhooks, and developed specific scripts to trigger two fundamental types of events: track, focused on capturing behavioral events within the app, and identify, responsible for capturing customers' registration data, ensuring we continuously used and updated customers' registration data for a solid, enriched, and always up-to-date base. The architecture of the solution and the data flow was the way to make this work at bank scale, managing millions of daily events through a robust architecture where events generated in the app passed through an intermediary application responsible for collecting these actions through messaging services like Kafka and RabbitMQ, allowing us to format the events with custom fields for proper identification, processing, and standardized sending to Segment, which let us segment and create highly qualified audiences crossing in-app browsing behavior and product acquisition with the client's investor profile, opening a huge range of operational and marketing opportunities like abandoned cart campaigns and personalized banners displaying real-time customized offers. The process to create those qualified audiences involves a multidisciplinary approach seeking a successful final impact, where building this ecosystem is not a one-person job and requires deep integration between multiple technology and business fronts, as we worked side by side with the Mobile, interface, hub, advisors, BFF, backend, and database teams to ensure that front-end collection was performant and did not impact the app experience, while serving the Revenue team directly as it used Segment as its main work tool and source of truth, enabling them to create dynamic audiences, trigger targeted campaigns, and extract precise reports for strategic decision-making in a summarized implementation of Segment at the XP bank, transforming our communication approach into a fully personalized strategy focused on the investor's journey, an enriching technical project where I applied software engineering to leverage MarTech results generating real business value. I believe that the offer banners were successful cases from my experience with Segment, as we tracked the entire flow from click, view, and conversion of marketing campaigns, which brought in significant revenue reaching about 650 million in monthly revenue.

My main use case for Segment is as a CDP to create a centralized view of the customer and help integrate the activation of audiences to downstream services. A specific example of how I use Segment for this purpose is that we collect data from different data sources, and we then leverage the activation layer within Segment to populate data within Braze as the customer engagement platform. In practical terms, this could be somebody browsing our website or interacting with our loyalty system, and based on those user behaviors, we share those events and the data with those events with Braze, which is then used for personalized communications such as email, SMS, and push notifications. That is the primary use case, and we have also implemented custom functions and transformation layers within Segment.

I have been using Segment for the last two and a half years as part of my role as a Product Analyst. During this period, I have worked extensively with the platform for customer data collection, event tracking, analytics integration, and user behavior analysis across multiple digital touchpoints. My experience with Segment has involved implementing and managing tracking plans, integrating with third-party analytics and marketing tools, monitoring the customer journey, and ensuring data consistency between different platforms. Over time, I have also collaborated with the product marketing and engineering teams to streamline the data workflow and improve decision-making through centralized customer data. My main use case for Segment is to centralize customer data management and product analytics. As a Product Analyst, I mainly use the platform to collect, standardize, and distribute customer event data across multiple analytics, marketing, and reporting tools for a single integration point. Segment plays a critical role in tracking user behavior across web and mobile applications. I also use it to monitor the customer journey, analyze feature adoption, and measure engagement metrics. This helps me understand how users interact with different parts of the product. Overall, this enables my product and business team to make data-driven decisions regarding feature improvements, customer experience optimization, and retention strategies. Our team uses Segment as a central data orchestration layer across multiple business functions. What makes our implementation somewhat unique is the close collaboration between the products, marketing, analytics, and engineering teams through a shared tracking framework. We have also established a standardized event taxonomy and governance process with Segment, which helps to ensure consistency in how customer interactions are tracked across all digital platforms.

Segment serves as my primary tool for event routing and Profile Unify Sync. I utilize event routing because multiple tools exist in our stack, including a website, mobile application, and server. All these sources need to be connected to Google Ads, Facebook Ads, TikTok Ads, Snapchat Ads, our data storage bucket, a data warehouse, and various third-party tools. I implement numerous transformations between these connections and route different functions while sending data to HubSpot CRM, which significantly simplifies the process. This relates directly to events implementation. For product exploration, I connect different sources using the profile sync features. Back-end sources, Android sources, and iOS sources are enabled, which creates a complete unified profile of users with different metadata and marketing sources.

I mostly use Segment for our marketing plan to clarify our target audience. We were trying to run a program to reach out to a large number of audiences, and we had to use Segment to break down and clarify all the target audience and specify how we were going to be reaching out to them. With Segment, we were able to clean the data and also break the data into different classes to reach specific targets with a specific message. The outcome was very superb.

I have used Segment for more than a year. I was working with Addx and Segment was used to align profiles and different user profiles. I used it for journey building, unifying different emails or profiles, and tracking profile behavior. My primary use case was an abandoned cart journey where when users were viewing their cart, we would get an event. Whoever was going to view their cart would be added to our journey, and we had journey steps where they would receive emails that helped us in getting more money and subscriptions.

Segment is currently the main customer data source of truth and the CDP we use. Our CDP has become more important over the last few years and is basically the center of all of our customer data from both B2C and part of our business. In my day-to-day work, I collaborate with marketing in order to set up audiences and make sure that they're feeding into the correct sources so that they can activate. Regarding our main use case, we're also checking profiles and making sure that the data that's flowing into Segment is what we're getting into our CRM, which is called Iterable.

We don't have a partnership, but we're a consulting organization. We've proposed Segment as a solution to a few of our clients, and some of them have adopted it. We've helped them with the configuration and integrations. One example is in the InsurTech space. The client had a direct-to-consumer (D2C) channel for selling and distributing policies, along with other channels like an agent portal for sales, leads from partners and purchased databases, and ads from Google and Facebook. We had a lot of different data sources, and we wanted to consolidate all those leads into a CDP instead of just sending them straight to the CRM, which was HubSpot. So, we used Segment to ingest all the leads from those sources, and then integrated with a few third-party tools like Verisk to qualify the leads within the CDP. The qualified leads were then sent directly to the CRM, where they became MQLs—marketing qualified leads—and entered the sales funnel.