Unanswered questions

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 this destination?

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?