Hi there @bill_wishgarden ,

If I am understanding correctly, you want to show/hide something in your email #2 based on whether or not they used the coupon correct?
You can use the following syntax in your Show/Hide logic to show or hide blocks in your template if someone has a particular Coupon on their profile: person.Coupon == "couponname".  One thing to note is that Klaviyo doesn't have visibility into whether or not someone has used a Coupon, so we will show that Coupon on their profile whether they have used it or not, as long as it has not yet expired.  I'd recommend testing this to confirm whether it meets your needs, and generally recommend putting a conditional split in the flow before the email where you want to show this reminder to determine whether the customer has Placed an Order since starting the flow.  This would avoid showing the block to profiles who might have the Coupon on their profile but may have already used it.

@bill_wishgarden  Unless you’re specifically adding the Buyer is false field you’ll actually want the condition to confirm that the field doesn’t exist on their profile at all with this syntax. 

not person|lookup:'Buyer'

Note: The field name (ie. buyer) is case sensitive. 

If you are adding a value of false after checking whether or not they made a purchase, it might be an error in your logic. It looks like you’re missing the space between the == and the 0 in the first condition example. 

person|lookup:'Buyer' == 0

You can see all the conditional references here: 

https://help.klaviyo.com/hc/en-us/articles/7655926841499

Lastly, you can use a text field instead. I find them easier to work with. 

So right before email two, add a conditional split. those who make a purchase, add the profile property Made First Purchase with a value of Yes. 

Then in the email, you’ll confirm that the field does not exist on the profile with:

not person|lookup:'Made First Purchase'

Hope that helps!

Thank you @Jessica eCommerce Badassery and @alex.hong for your great input. I missed the “not” function on the Help Center page. (e.g. not person|lookup:'Buyer' == 0).

I found that not person|lookup:'Buyer' works perfectly, as expected and as hoped!

Thank you again for your help!

-Bill