This AND NOT... That OR Them | Community
Skip to main content
Level 4
July 30, 2018
Solved

This AND NOT... That OR Them

  • July 30, 2018
  • 2 replies
  • 3706 views

Hello,

I'm curious, since AAM does not allow for individual containers to be built like AA does when building segments, will this report accurate results.

User visits site

ANDNOT

Visitor is a know Guest

OR

Visitor has placed ordered previously.

I do not want to qualify site visitors who I already know and I do not want to qualify site visitors who have placed orders.

Ideally it would be written as User Visits Site ANDNOT (people with a Guest ID OR people I know have already ordered from site)

Am I making sense? Please advise. Thanks. 

Glenn

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by snielson

Hi Glenn,

Yes, I believe your logic here should work.
In your example, let's give each variable a made up trait ID.

Site Visitor = 111222333

Has Guest ID = 222333444

Made Previous Order = 333444555

The segment rule may look something like:
(11122233T AND NOT (222333444T OR 333444555T))

Regards,

Shane Nielson

2 replies

snielson
Adobe Employee
snielsonAdobe EmployeeAccepted solution
Adobe Employee
August 16, 2018

Hi Glenn,

Yes, I believe your logic here should work.
In your example, let's give each variable a made up trait ID.

Site Visitor = 111222333

Has Guest ID = 222333444

Made Previous Order = 333444555

The segment rule may look something like:
(11122233T AND NOT (222333444T OR 333444555T))

Regards,

Shane Nielson

Level 4
August 16, 2018

Might I add that it should probably be noted somewhere in the documentation that, since in AAM there is no way to (sub-segment) the OR expression, that it does in fact work without parentheses.

I actually have an open ticket where I found a situation that the system is not correctly using the Boolean expression as you describe [Incident: 180814-000334]. If you reverse the order of trait 222333444T and 333444555T to 333444555T and 222333444T, rather than returning the same population estimate, the system incorrectly calculates erroneous estimates.

Engineering is working on it.

Have a nice day. Glenn