Is the device tied to a authenticated profile which contains the segment by chance? If not, I would also try a private / incognito browser, just to verify this device is seen as totally new.

Hi Mike, Absolutely! using the h_ prefix you can target values such as the user-agent. I would recommend viewing our documentation here:https://docs.adobe.com/content/help/en/audience-manager/user-guide/features/traits/trait-device-targeting.html As for the actual user-agent, you should be able to f...

Hello, The d_sid=traitID should qualify the device ID to the trait. How are you checking to make sure the device has qualified into the trait?If you're reviewing the trait in the AAM UI, please note that this is updated once daily. I would recommend reviewing your traits in the UI the next day after...

If you wanted to same device (browser) to qualify into the segment, you'd have to either adjust the frequency/recency, set up a new segment with different frequency/recency, or clear the demdex cookie. If you were to clear the cookie, AAM would see this as a new device with no traits, but works for ...

Hello, The recency/frequency is stored on the profile with the trait. If your relying just on the non-authenticated ID (AAM UUID), and the cookie is cleared after they close the browser, that device will be seen as a entirely new user the next time they come back. However, if they authenticate on th...

Hello, Pixels for emails are usually implemented by putting the img script tag into the body of the email. This pixel will need to contain your AAM subdomain, as well as any key-value pairs you'd like to send into AAM to track the emails.For example the impression could look like this: https://subdo...

Hello,Currently there is no built in option within the UI. However, this is possible to pull using our REST API. You'll want to send a GET request to https://api.demdex.com/v1/users/ with your bearer token, and this should provide a list of all your AAM users in a format that can be converted to CSV...

@seanm97690176, turns out there is an issue with some checks on deleting a model that was tied to folder trait. This should be resolved in a future fix. In the meantime our API team manually removed this model for you.

Hi Val, I would go with the "last authentication (up to three cross-device data sources) + device profile".When selecting the cross-device data sources, be sure to select the data source where your CRM IDs are onboarded. By using last auth, this will target authenticated profiles in both real-time, ...

Hey Sean, I was hoping to see more.. but seems the message you provided initially was all there was? {"message: Trait must be RULE-BASED or ONBOARDED", "code":"ILLEGAL_ARGUMENT"}However, your comment did provide the model ID so I checked on this myself and couldn't see what the issue was. I've opene...