Skip to main content

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?

Hey ​@Andy Batten this is by design. For what you’re looking to do, right now the SQL traits is going to be the way to go but if you can supply a random anonymous id you’d be able to leverage the rETL method. However it does provide more work for you. It’s possible that in the future we’d build the functionality in rETL.

Reply


Terms & Conditions