Targeting Option Rules Detailed Guide

When creating targeting options, you set conditions on properties or contexts. This guide explains available operators by data type and how to combine filters.

---

Value Format by Data Type

Formats used when passing property values from the SDK.

Type	Format	Example
String	Text	"seoul", "premium", "[e-mail]"
Number	Integer or decimal	0, 123, -456, 1234.56
Boolean	true / false	true, false
Date	ISO 8601 (recommended)	2024-01-18, 2024-01-20T08:20:00

ISO 8601 format (YYYY-MM-DD) is recommended for dates. YYYYMMDD and timestamps (ms) are also supported.

---

String Operators

Operators available for string type properties.

Operator	Description	Example
is	Include users that match exactly	region is “Seoul”
is not	Exclude users that match exactly	region is not “Seoul”
contains	Include users that contain the value	email contains “gmail”
does not contains	Exclude users that contain the value	email does not contains “test”
starts with	Include users that start with the value	username starts with “admin”
ends with	Include users that end with the value	email ends with “.com”

String operators are case-sensitive. “Seoul” and “seoul” are treated as different values.

The is and is not operators allow selecting multiple values. Example: region is “Seoul”, “Busan”, “Jeju”

For the default properties Country, Language, and Gender, only the is operator is available.

---

Number Operators

Operators available for number type properties.

Operator	Description	Example
is	Include users that match exactly	age is 25, 30, 35
is not	Exclude users that match exactly	age is not 0
= (equals)	Include users equal to value	trade_count = 10
≠ (not equals)	Include users not equal to value	trade_count ≠ 0
> (greater than)	Include users greater than value	trade_count > 5
≥ (greater than or equals)	Include users greater than or equal to value	trade_count ≥ 5
< (less than)	Include users less than value	trade_count < 20
≤ (less than or equals)	Include users less than or equal to value	trade_count ≤ 20
between	Include users between two values	age between 20, 29
not between	Exclude users between two values	age not between 20, 29

In the console, operators are shown in English regardless of the display language, and number comparison operators are shown as symbols (=, ≠, >, ≥, <, ≤). The is and is not operators allow selecting multiple values. between / not between require two values.

---

Boolean Operators

Operators available for boolean (true/false) type properties.

Operator	Description	Example
is True	Include users with true value	is_premium is True
is False	Include users with false value	is_premium is False

---

Date Operators

Operators available for date type properties.

Operator	Description	Example
last	Include users within past period	last_login last 7 days
before the last	Include users before past period	last_login before the last 30 days
next	Include users within next period	subscription_end next 7 days
after the next	Include users after next period	subscription_end after the next 30 days
before	Include users before specific date	created_at before 2024-01-01
after	Include users after specific date	created_at after 2024-01-01

---

Combining Targeting Option Rules

This section applies to audience targeting options. Context targeting options consist of a single is condition in which you enter context IDs.

You can set multiple conditions for a single targeting option. Use the following buttons in the condition editor.

• + Filter: Adds a condition row to the group. The first row starts with where, and the following rows are connected with and by default. Click and to change it to or.
• + Group: Adds a new group. Groups are connected with AND by default. Click the AND button between groups to change it to OR.

In the examples below, conditions in parentheses belong to the same group.

AND Conditions

To include only users who satisfy all conditions, add the conditions to the same group with + Filter and keep them connected with and.

Example: Seoul Power Seller

• region is “seoul” and
• trade_count ≥ 20

→ Users in Seoul region with 20+ trades

OR Conditions

To include users who satisfy any of the conditions, add a group for each condition with + Group, then change the connection between the groups to OR.

Example: Capital Region Users

• (region is “seoul”) OR
• (region is “gyeonggi”)

→ Users in Seoul or Gyeonggi region

Complex Conditions

Use AND and OR together to create complex conditions.

Example: Capital Region Power Sellers

• (region is “seoul” and trade_count ≥ 20) OR
• (region is “gyeonggi” and trade_count ≥ 20)

→ Seoul power sellers or Gyeonggi power sellers

---

Context Targeting Operators

In context targeting, only the is operator is available for context IDs. In the console, the condition field is shown as Category ID.

Operator	Description	Example
is	Matches context ID exactly	Category ID is “phone”, “laptop”, “tablet”

When selecting multiple context IDs with the is operator, ads display if any of those IDs match.

• Excluding specific contexts: Instead of an is not operator, create a targeting option with the context IDs you want to exclude. Then set that option as Required Exclude on the ad product, or advertisers can exclude it when booking a campaign. For details, see Selling Targeting.
• Partial matching: Operators such as contains are not supported. Pass more specific context IDs from the SDK, and enter every value you want to match with is.

---

Next Steps

Booking Campaigns

Learn how advertisers select targeting to book campaigns

---

FAQ

What's most important when setting targeting option conditions?

Entering exactly as passed from the SDK is critical. Especially for strings, which are case-sensitive—“Seoul” and “seoul” are treated as different values. Confirm actual passed values with your development team.

When are date conditions useful?

Useful for targeting user states that change over time. For example, “active users who logged in within the last 7 days”, “users with subscription expiring within 30 days”, “long-term members who joined over 1 year ago”.

How do I distinguish when to use AND vs OR conditions?

Use AND when all conditions must be satisfied simultaneously. Use OR when any one of multiple conditions can be satisfied. Conditions added with + Filter and groups added with + Group are connected with AND by default; click the and or AND button to change it to OR. For example, “Seoul power seller” is region=Seoul AND trade_count≥20, while “Capital region users” is region=Seoul OR region=Gyeonggi.