I am attempting to use the integrations object to filter which identify and track messages are sent to my Customer.IO destination. The reason I want to send a subset of these messages is to avoid creating a Customer.io ‘person’ for every identify call.I am not sure exactly what to put in as the key value where I have CustomerIO here:curl -X POST https://api.segment.io/v1/track \ -H "Content-Type: application/json" \ -d '{ "writeKey": "'$WRITE_KEY'", "messageId": "track-john-test-'$COUNTER'", "timestamp": "'$TIMESTAMP'", "userId": "'$USERID'", "integrations": { "All": false, "CustomerIO": true }, "event": "'$EVENT'" }'Should I have { “integrations” : { “Customer.io Dev” }} which is the name of the specific destination? I think not, as the integration filtering is “applied to all instances of the destination” (from https://segment.com/docs/guides/filtering-data/).Should it be `actions-customerio`, as this is the slug displayed in the URL when accessing
It looks like the five Suggested Predictive Audience categories (e.g., Ready to Buy, High LTV) are primarily ecommerce-focused, relying heavily on purchase and revenue-related events like Order Completed.Are there options to build custom Predictive Audiences that don't depend on a revenue-based conversion event? And is there a roadmap to support non-ecommerce use cases—for example, audiences built around content engagement, form fills, or other non-purchase signals?Would love to hear how others are handling this or if Segment has guidance on broader applications.
I wanted to run this by the community for advice and best practice.We use Account SQL Traits to enrich Account profiles today, so each computation generates a Group call and adds the traits to the Account.I built out a rETL model and have looked at the Segment Profiles destinations to replicate this approach with rETL. However, when configuring the Group mapping in the Segment Profiles destination, it requires that I set either an anonymousId or userId, neither of which I would have since I just want to enrich the Account profile.I don’t see a way to replicate Account SQL traits for this unless I generate/populate an arbitrary anonymous ID to use. I’ve noticed that the Group calls that get generated from the account SQL Trait use a static anonymous ID - __segment_internal_personas_group. Would it be safe to simply use this exact same value in the Group mapping of the Segment Profiles destination in order to get it to work?
We are excited to announce the release of the next phase of Segment Consent Management: Storing end-user consent preferences on their Unify Profiles is now in Private Beta!Last year, we launched the ability to collect and enforce end-user consent preferences within Segment Connections and Reverse ETL when sharing data with 3P Destinations.Now, using these same events, Segment will stamp these preferences on to the Segment Profile as traits. With this beta release, customers can leverage consent traits on the profile to manually enforce consent in Engage Audiences. For more information, see the Storing Consent on the Profile documentation and demo. If you would like to participate in this Beta, send me a message with your workspace id or slug.
Hello,We’re looking to implement Subresource Integrity (SRI) for enhanced security on our site and are importing the following script from your CDN:https://cdn.segment.com/analytics.js/v1/[key]/analytics.min.jsBefore proceeding, could you please confirm whether this JavaScript file is immutable—that is, once published at a given versioned path the content never changes?This is important for us to safely apply SRI, since the hash must remain valid over time.Thank you,
Already have an account? Login
Enter your 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.