Hello, We're unable to have duplicate (same expression) traits or segments assigned to the same data source. If you'd like to have multiple traits or segments with matching expressions, you'll need to keep them assigned to separate data sources. Is there any reason you wouldn't want to use the alrea...

Hi @maxmeyer3141 Could you please share the full DELETE URL here?Do you by chance also have access to a client ID / client secret to use the Oauth2 method? I'm curious if this is specific to the JWT tokens. Thanks,Shane

Hi @yatins78957443 , The 'stuff' object contains all the cookie names (cn) and cookie values (cv | segments) from the segments mapped to cookie destinations within your AAM instance. The segments returned will be the segments the device has qualified to.If you're looking to get traits and segments r...

Hi @gauravd85673172, Depends on the type of profile merge rule you're looking to implement. If you are looking to qualify customer IDs alongside device IDs into segments, you'll want to make sure the ID sync is in place to stitch those customer IDs and device IDs together.I would recommend looking i...

Hi Talan, Please look into our documentation for Audience Labs. Using Audience Labs, you can set aside a segment control group while testing the efficiency of the segment and test groups with different destinations.https://docs.adobe.com/content/help/en/audience-manager/user-guide/features/audience-...

Hi @keerthivasanj96, I would suggest opening a support ticket with the AAM team (amsupport@adobe.com). I just tried this as well on my end, and did not get any segments to return. We may need to look into what the visitor visitor API calls are request/returning. Regards,Shane

Hi @suhasRakam, Yes, using the DCS API to send a call to AAM with the d_sid=<trait ID> will still realize the device making the call into said trait. If your segments are configured with a profile merge rule that contains device options, and contains the traits in the segment rule, it should only ta...

Hi @MA1985CG, Frequency and recency are calculated on an occurrence basis... meaning every time AAM gets the signals to realize a trait, that will increase the frequency +1. If there is an implementation issue with Analytics sending two hits per load, the frequency would increase per hit (+2 in this...

@MA1985v1 interesting.. this should work, and just tested again to confirm... Does it seem to work when using another browser or sending the request via cURL or with another utility, such as Postman? As a side note d_dpid and d_dpuuid are deprecated (still work technically), but I would suggest usin...

@anhousto1 this is no longer the case. When using the d_sid key with the DCS API, it will qualify the device/profile to the trait, despite it being rule-based or onboarded.