Connect, Learn, Share, Innovate
Get answers to your product questions
Share a use case or what you're working on
Browse tutorials and other helpful resources
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.
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?
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.
