Skip to main content

Community Chatter

Submit your question or join a discussion

116 Topics
S
Saransh
asked in Product Q&A
Integrating JSON type columns to Snowflake instead of flattening

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.

821
Andrew Rawson
Segmenter
J
juan pablo duque
posted in Discussion
In your companies, which roles are currently responsible for creating audiences in Segment?

Hi everyone, I'm curious to learn more about how your companies are currently building their audience creation processes. Specifically, I'm interested in understanding which roles are involved in this process. Is it primarily handled by the marketing team, the data team, or the product teams? 

2804
Chris Johnston
S
Sagar Viradiya
asked in Product Q&A
Not able to sync nested fields under object in Intercom

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": {

1033
Andrew Rawson
Segmenter
Tiffany Darwish
Segmenter
Tiffany DarwishSegmenter
published in News & Updates
New in Predictions: Predict on the event propertyNews

You can now build granular predictions based on the specific properties of any event tracked in Segment.What’s that mean for you?Here’s a couple of use cases that show what’s possible:Predict the propensity that Marketers will buy tickets for your upcoming industry expo - filter on the property that identifies Marketers in your customer base. Predict the likelihood of a customer adding an item to their cart that cost more than $20 - filter on the property that identifies the cost of your product. Predict how likely someone is to share a social media post on Facebook - filter on the property that identifies the specific platform.Watch this quick video from Product Manager Troy Bolus on why we are so excited about this release! 

900
Tiffany Darwish
Segmenter
J
juan pablo duque
posted in Product Q&A
Problems with Google Ad Remarkting list destination

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,

1182
J
S
Stephen Plesko
asked in Product Q&A
Setting up Google Analytics 4 Web Destination

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?

2483
J
J
James Larsen
posted in Discussion
Segment Unify Attribution Expectations

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!

2287
J
P
Segmenter
Peter TuhtanSegmenter
published in News & Updates
Delivery Overview & Source Volume Alerts now GANews

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 GA​​​​​​When 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

770
P
Segmenter
H
Hannah B
asked in Product Q&A
Product user IDs as Segment user IDs

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!

1222
H
Andy Pickler
Andy Pickler
asked in Product Q&A
'screen' call on mobile

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.

552
Chris Johnston
Rob Craig
Rob Craig
posted in Discussion
Integrating Segment with Data Warehouse/Visualization Tools

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.

1792
Denys Tkalich
C
Corey Egan
asked in Product Q&A
eTimedout errors for Webhook Destination

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?  

1814
Luke Bussey
P
Segmenter
pcooperSegmenter
posted in Discussion
React Native SDK Offline Handling

  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

930
P
Segmenter
Chris Carrel
Chris Carrel
asked in Product Q&A
Segment EdgeSDK and payload modification

We are starting to use the Segment EdgeSDK and I currently have some analytics.js middleware functions that I would like to move to my edge worker so that they can be maintained across our properties.  Specifically, I am modifying the campaign context to normalize UTM parameters to improve the adhoc reporting in GA.Does anyone have any experience doing this? Or maybe an example they could share?Thanks,Chris

1323
Chris Carrel
Chauntel Greaves
Segmenter
Chauntel GreavesCommunity Manager
published in News & Updates
Databricks integrations is now in GANews

The blog highlights our partnership with Databricks and three features which enable bidirectional data integration, unlocking new use cases for actionable insights and personalized experiences at scale.Key features include:Databricks as a Storage Destination: Sync events into the Lakehouse. Databricks as a Profiles Sync Destination: Hydrate the Lakehouse with unified and identity-resolved customer profiles. Databricks as Reverse ETL Source: Activate data directly from the Lakehouse via Segment to unlimited destinations including over 450 prebuilt, battle tested, APIs with the world's most popular martech applications.Marketers and data teams can leverage these integrations for powerful machine learning capabilities, enabling critical use cases like marketing attribution and predictive analytics. Read more here.

300
Chauntel Greaves
Segmenter
Chauntel Greaves
Segmenter
Chauntel GreavesCommunity Manager
published in News & Updates
Trait activation now supports all destinationsNews

March 2024 - Trait Activation now supports all Destination Actions and includes both Trait Enrichment and ID Sync:  With Trait Enrichment, use custom, SQL, computed, and predictive traits to enrich the data you map to your destinations.  Use ID Sync to select identifiers and a sync strategy for each identifier when syncing Engage Audiences to Destinations. Reference our docs to learn more.

670
Chauntel Greaves
Segmenter

Badges

Show all badges
Terms & Conditions