Hi matt-gardner,The specific use case you outlined can actually be
achieved a few different ways with Adobe Target. As Shruti mentioned
device co-op can bridge cross device scenarios. Though it can even help
before login. Mbox3rdPartyId is another way that will allow you to share
profile data across devices post login. Here's the main help doc:
Real-time profile syncing for mbox3rdPartyID. However, the specific
scenario you mention could also be achieved with a simple profile
parameter and an a...
I think one of the reasons why they're separated like this is so you
have that choice. I will say that I've only seen lookup table data added
to, and never removed. The removal of lookup data would have an adverse
effect on historical data collected.If denormalizing and storing is the
better option for you, then I don't anticipate any issues with the
clickstream lookup tables interfering.
Hello Matt,First of all, I don't understand your condition,
please may you explain it, what is meant for?FYI, there are security
flaws with SHA-1, so it is deprecated.And normally, in Query activity,
you should see only SHA-2 algorithms (in addition of MD5), so
Sha256Digest(string) and Sha512Digest(string).In the JSAPI, due to
backwards compatibility, there are JS functions such as digestStrSha1
and sha1() but please use rather digestStrSha256 (string) (or 512).Then,
the time-out/SQL performanc...