Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Equivalent to _satellite.getVar in Apps


Level 4


Hey guys,


for websites we have the awesome ability to set up a data element in Launch and call _satellite.getVar to get the value of that data element, as described on Launch object reference. We are using this with constant data elements from the core extension to provide some config values to our websites (as described here). Awesome!


Now we would like to do the same thing with our apps. Is there any equivalent way of getting the value of a constant data element configured in Launch via the SDK in apps? This would be a killer use case for us and safe us a lot of headache with our agencies.








Hi Frederik - Can you illustrate some examples where you would set a value in Launch for a Data Element that you would want to pick up in the app? Also how often would this value change? Who is the persona that would be determining the value? 


Level 4


Hey @Ivan_Mironchuk, of course 🙂 On the Blog post linked above, I outline the case of Analytics, where we could save on Server Calls through sampling and adjust the sampling rate through Launch. Other Analytics cases would be to prefix or postfix a variable on the fly. All this would be done by the Analyst and would not change that often (maybe once a week at max?).


The other case would be for our Developers. This is the even bigger case in my opinion, since they would not need a separate "tag management" or "configuration management" solution in the app but only Launch, reducing the tool footprint and increasing Launch usage. They would be able to change any configuration keys on the fly without a new app release (changing backend endpoints, marketing accounts, CTA texts, etc. on the fly). Even some mild A/B Testing or Feature Flagging could be possible. This could happen multiple times a day through the Devs.


All in all, this would be a very "hackable" feature with lots of creative applications. It would save us time and/or money, when we don't need a separate solution for this.