I would ask the front end application to limit the characters because
you have a limit in AA. In my experience AA does not do well with such
long values in terms of getting insights. Or you can work with product
team to capture only first 255 character in evar. Best of luck.
Yea I was having hard time finding it in the java doc as well. I would
look closely at sample code to see where the value is typically set and
use the same options provided in the nodejs documentation. My
recommendation outside of documentation is confirm with client support.
The AAM API is specific for interacting with the same capabilities you
could have in the AAM UI. So creating/editing/deleting traits, segments,
data source, profile merge rules, getting data of a particular segment
as examples. It is not the API to do ID syncs or getting a specific
users data, or for sending user data.
Here is my recommendation. You have two instances, Website A will have
Appmeasurement for Analytics with ORG1. Website A should have S2S
forwarding with AAM. That is BAU. On Website A, you have two options for
sending the data to your second AAM instance. Option A using DIL or
Option B using your Website B Adobe Analytics instance also on Website A
(the instance with the same org ID as your second AAM instance). You
would have this set up as S2S as well. Either route, you will end up
You would have 1 DIL instance for the "website 2" AAM instance. Your AA
and AAM for website 1 should be using server side forwarding. You send
data to the website 2 AAM instance using DIL with the configured Adobe
Org ID. If you want to use the data sent to the AAM instance using the
DIL code you need to understand that for site activation both of the
instance need to be on the same web domain. WHen the DIL code creates an
instance it will create a cookie for that specific domain you are on.
So what I shared still applies, you can do it on the client side but
will need to have jobs to export the data and send it to the other
instance. I really think you should contact Adobe about the server side
Launch beta. I think it would be a great fit and it would be something
that would be more efficient and scalable. Here is documentation on it.
Here is the link, read under "Enable Launch Server Side"
Ok I follow now better I think. So yea you want to pass in
entity.category so Target can track the category of the product, if you
want to pass in specific category affinity about the user based on data
you might have you can pass that in as well under user.