We are syncing fields nested under the object to Intercom, but it seems it is not working.we have the following tracking plan for Identify and Group calls.For the Identify call, we are trying to sync the pickupOutsourcingEnabled field, which is under the settings object. To enable this sync in Intercom, we updated the filters and created a Transformation to move the property to the root level.Although we are not encountering any errors in the Event delivery when sending fields to the Intercom destination, we are unable to see the field in Intercom.Group Call Tracking plan{ "$schema": "http://json-schema.org/draft-07/schema#", "type": "object", "labels": {}, "properties": { "context": { "id": "/properties/context" }, "traits": { "type": "object", "properties": { "settings": { "description": "Buyer company settings.", "id": "/properties/traits/properties/settings", "properties": { "pickupOutsourcingEnabled": {
Hi everyone,I am writing to inquire if any of you have been experiencing issues with audience match using the Google Ads destination. We are currently seeing a 20% decrease in match rate compared to manual uploads to the Google platform. It seems this may be related to API limitations, but I wanted to check if you have also observed a decrease and, if so, what steps you have taken to mitigate it.Any insights or suggestions would be greatly appreciated.Thank you,
I’ve created a predictive LTV trait and want to leverage it via FB ads, especially for new customer acquisition. Is this limited to pushing it as an audience and creating a lookalike etc or is there a more sophisticated way to use this to find likely high LTV new customers?
We have been having difficulties getting GA4 to properly load and ingest data from Segment. Anyone have tips or settings they recommend we use both within GA and within Segment?
Hello everyone,We've integrated Segment with both Pixel destination and Conversion API destination on our web properties. The documentation emphasizes the importance of passing the `fbc` (Facebook click ID) and `fbp` (browser ID) cookies in the API events to allow Meta to deduplicate events effectively. However, we're encountering a synchronization issue described as follows:A user clicks a Facebook ad and lands on the landing page. Segment initiates, downloading the Pixel via its CDN and sends the `page_view` event to itself. At this point, Meta’s Pixel has not yet activated, so the event sent to Segment may contain either outdated cookies from a previous session or no cookies at all. Meta’s Pixel then activates and performs the following: Extracts the Facebook click ID from the URL and either updates the `fbc` cookie or creates a new one if it's not present. Similarly, it handles the `fbp` cookie, updating or creating it to store the browser identifier. Meta’s Pixel sends the `page
Our company currently uses Google and Facebook for most of our paid advertising, and we're trying to tie our customer's journey from web through to sign up of our app. We use Segment so started using their "Unify" service to try to figure out where our customers came from. However, after much tweaking and even reviewing our setup with Segment, we're still landing at about 48% of our customers signed up with no visibility into any pre-sign up activity (web viewing or ads clicked). Our customers mostly interact via mobile (very little desktop usage).The question I'm trying to answer for the team is if 48% non-attribution indicates a problem with our setup, or if due to the tightening of privacy and security lately, that's just the "new normal" for tracking user's journeys from web to sign-up? We tried asking Segment, but their response didn’t tell us much, so would love to get some feedback from this community. Any insight is greatly appreciated!
When we send JSON object type columns to Snowflake, Segment flattens them and create separate columns for each key. This exceeds the 5000 properties limit. What would be a good workaround for this? We are thinking of sending data in Array format but it will require more effort in Snowflake to use such data.
Hello all!We currently sync all of our Segment data into Snowflake but there is one event which has a format that upon Segments automatic un-nesting of properties into columns creates a column explosion and sync failure.To overcome this we have been proposed creating the below flow. Segment Source via Function - this function is defined to intercept the malformed property and correct it. Creating an identical event besides that one event property being changed. Segment webhook Destination - this is a webhook (actions) destination which has as input our source which brings in the malformed event. This destination has a mapping configured to send to the webhook url defined by the Segment Source via Function.All Testing is showing that the Source Function is behaving as expected where I can pass in an event with the malformed event and it corrects it. The webhook Destination when sending a test event shows that the event being sent was a success. The problem is that the Source, powered by
Date & TimeWednesday, April 24, 2024 · 12:00 p.m. Eastern Time 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, 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. Register here. 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 to watch live. On demand version will be available shortly after and shared to community.
This is session #3 of 3 where we cover intelligently leveraging data to deliver personalized, multi-channel customer experiences at scale. Once you’ve built your customer data foundation and use customer data to drive KPIs you’re ready for the Adaptive stage of customer data maturity. What’s covered: Unifying your data across all touch points Deploying automation for data governance processes Implementing predictive analyticsSessions one and two.
This is session #2 of 3, where we discuss how you can start to add more complexity to your data strategy: whether by introducing more instrumentation, building more audiences, or by joining profiles together in more creative ways. What’s covered: Deciding what data should be collected to achieve meaningful engagement Resolving data into unified golden profiles that provide a single view of the customer Activating data and profiles to achieve positive business outcomesSessions one and three.
This is session #1 of 3 where we start at the beginning and focus on how to build a strong customer data foundation to set your engagement strategy up for success.What’s covered: Deciding what data should be collected to achieve meaningful engagement Resolving data into unified golden profiles that provide a single view of the customer Activating data and profiles to achieve positive business outcomesSessions two and three.
New to Segment? This 30 minute introductory overview covers: The key concepts behind Segment Setting up Connections, Sources & Destinations How data flows from Source to Segment to Destinations Overview of Protocols & Engage
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)
AboutIf you could easily uncover patterns in historical customer data, predict your customers’ future behavior, and discover audiences primed for engagement, would you seize the opportunity to do so?What if you could do it without having to lean on your data science teams, learn a complicated new program, or enter even a bit of code? AgendaWhat is CustomerAI? What is available right now? A demo of our pre-built AI/ML driven Predictive Traits & Predictive Audiences What is upcoming on our CustomerAI roadmap? Q&A Watch On Demand
Here’s a quick demo showcasing "Consent Enforcement in Segment Connections". This demo utilizes OneTrust as a CMP, but feel free to swap it out with your preferred CMP. You only need to ensure that every Segment event is stamped with the consent object, per specification.
The main focus of this community post is to highlight how Segment handles offline situations using its React Native SDK, also having a closer look at the iOS library code to see how it works. Offline Handling in Segment React Native SDK When the React Native SDK tries to send an event and the device is offline, the event is not lost. Instead, it is saved into a queue. The SDK keeps attempting to send these queued events whenever the device regains its network connection. This queueing mechanism ensures that no events are lost due to temporary network connectivity issues.The offline handling mechanism is actually part of the underlying native libraries (iOS and Android). Offline Handling in Native Libraries (iOS example) To illustrate how offline handling works in native libraries, let's look at the iOS library (Objective-C).The core of the offline handling logic resides in a method called flush within the SEGSegmentIntegration.m file. Here's a simplified version of the flush method f
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.
