Feature Request: Allow duplicate IMS org ID in Launch configuration

[and-poulsen]

We have a use case where we want to send the event to two different Edge configurations, based on whether or not the user consented to cookies. Currently it seems as there is no way to do this.

Allow duplicate IMS org ID across Alloy instances
The 2 edge configurations we have are under the same IMS org ID - but they're simply configured differently (different AA report suites etc)

Hot-switch / change configuration in the "Send Event" action
To avoid having 2 rules of every single tracking type, it would be great if you could in the "Send Event" action somehow target what configuration ID you are targeting, possibly through a Data Element.

return hasConsent ? alloy : alloyCookieless;

[jonsnyder]

In launch you can use a data element for the edge configuration id, but the element needs to be available when Launch loads. On the page you could wait to load Launch until the consent is loaded or selected, then create a data element that chooses the edge configuration based on the consent level.

I still think this is a valid feature request, but I'm interested to know if this work-around would solve your use case.

[and-poulsen]

but the element needs to be available when Launch loads.

Unfortunately on the first page view of a browser we don't know the decision of the users consent choice, and am awaiting his interaction with the CMP before we can decide what Configuration ID we are using

you could wait to load Launch until the consent is loaded or selected

We have other uses for Launch besides tracking this page view, so we can't delay it

[jfkhoury]

Unfortunately on the first page view of a browser we don't know the decision of the users consent choice, and am awaiting his interaction with the CMP before we can decide what Configuration ID we are using

@and-poulsen Can you have a default value for the Data Stream in your Data Element, and that would be the data stream you send data to when consent is pending? Can that be a solution?

Thank you for bringing this issue up.
Joe

[and-poulsen]

@jfkhoury
Well that would have to be the "no consent" configuration - but in the case that the user actually then gives consent 2 sec after (Which is 75% of cases), then we would lose that valuable first page view tracking where all attribution logic is available.
That's a dealbreaker.

Note that the two configurations would send data to two different AA suites - a "consented suite" and a "not consented suite" - so we would not be able to hook up the two visits if one started in the latter, and then continued in the former.

In AppMeasurement we could do s.account = <suite>