Persisting Session Via 2 Properties

[JulienRi]

Hi all,

I am using the Adobe Web SDK to send data to AEP to then be ingested by additional services (CJA). I want to set up 2 launch properties, one for the anonymous marketing website (logged out) and one for the logged in user. This is for the same website but I want to utilize 2 properties to split the logged in and logged out experiences and therefore what I deploy on each side.

How would I be able to maintain 2 different launch properties but not consider one consumer moving from the logged out experience to the logged in experience as 2 different sessions, if a consumer moves to the part of the web that utilizes 1 launch property to the other I still want to persist the same session/ECID and not have it considered a new session/user if I join those 2 properties data together in CJA.

Thanks and appreciate any responses.

[bjoern__koth]

Hi @JulienRi ,

in general the cookies the Edge network is writing in the Web SDK responses aren't bound to one specific Launch property and should work without any adaptations as long as you are using datastreams that are set up under the same AdobeOrg ID.

At least I am not aware of any limitations. Or are you talking about two different domains?

Bear in mind that adding another Launch property comes with overheads like additional maintenance, plus you will likely redefine many same data elements in two locations.

Ultimately, the visitor must download a second Launch library where his browser could have used a cached version when moving between the sections.

I would likely go with one Launch property and a clear rule naming strategy that indicates which rules are triggered under which conditions.

Just this morning, I read this interesting blog post by @kenmckell about exactly this topic.