acceptable-salesmen-7165709/26/2023, 8:19 PM
happy-autumn-4093809/26/2023, 8:36 PM
acceptable-salesmen-7165709/26/2023, 9:01 PM
happy-autumn-4093809/26/2023, 9:25 PM
acceptable-salesmen-7165709/26/2023, 9:37 PM
happy-autumn-4093809/26/2023, 9:58 PM
acceptable-salesmen-7165709/28/2023, 12:54 PM
happy-autumn-4093809/29/2023, 8:15 AM
sort of variable and do away with the saved group entirely. Unless you need to do specific targeting based on user id that isn't captured by this (in which case you might introduce a new variable summarizing which custom group they're in). Also when you say "send fresh attributes to GB" do you mean updating the user attributes at the GB SDK level? There isn't any sort of round trip to GB servers that happens here; instead features should be loaded from the GB server and cached in the SDK - typically after the SDK is constructed. Then any user attribute changes causes a local on-the-fly re-evaluation of the user's features / experiments. This happens within the SDK rather than on a GB server.
customerType: "vip" | "paid" | "battle pass"