Skip to main content
Configure targeting categories based on the activity category the user is viewing.

​
What is Context?

Context is contextual information about the page the user is currently viewing. Any data that can distinguish pages—such as product categories, article classifications, or search keywords—can be context. Context is passed via SDK during ad requests, and targeting categories are created by combining passed contexts.

​
Passing Context ID

Context IDs are defined by the publisher. If you already have a content classification system in your service, you can use it directly. When requesting ads via SDK with a context ID, ads matching that context are displayed.
Context targeting applies only to banner and native ad requests that include a Context ID (banner and native ads in the Android and iOS SDKs, the Web SDK, and the REST API). Interstitial, rewarded, popup, and splash ads, as well as the Flutter and React Native SDKs, do not send a Context ID. If an ad product that contains these placements uses context targeting, campaigns that include context options are not shown in those placements, and context exclusions are not applied there.
Context IDs are case-sensitive and must exactly match a value entered in a context targeting option’s condition in the console. Do not use commas (,) in Context IDs, because a comma separates multiple values both in the console and in an ad request. When requesting ads, pass the value exactly as entered in the console, without leading or trailing spaces.
If you don’t pass a Context ID, or pass a value that isn’t registered in the console, no error occurs. Only campaigns with context targeting are excluded, and other ads can still be served.

​
Passing Multiple Context IDs

A placement can send more than one Context ID in a single ad request. Separate them with commas.
Repeating the parameter, as in ?contextId=hiking&contextId=outdoor, works the same way as the comma-separated form.

​
Example: Local Activity App

Assuming a local activity app passes the category of the activity detail page the user is viewing as context.

​
Creating Context Targeting

​
Step 1: Create Targeting

  1. Click Targeting in the left menu, then select the Context tab at the top.
  2. Click the Create Targeting button. If you don’t have any context targeting yet, click the Create button on the empty screen.

​
Step 2: Enter Targeting Name

Enter the targeting name that will be displayed to advertisers.

​
Step 3: Add Targeting Options

  1. Click the + Add Option button.
  2. For Type, select Option. To offer several options as one, select Option group instead (see Option Groups).
  3. Enter the Option name.
  4. In Context ID, enter the value your placement sends when it requests an ad. Separate multiple IDs with commas.
  5. Click the Add button.
Example: Configuring targeting options for a local activity app Combine Context IDs to build an “Activity Category” targeting.
Targeting names and option names can contain only Korean, English letters, numbers, spaces, and the symbols ~ % & + -.

​
Step 4: Save

Click the Create Targeting button to save.

​
Option Groups

You can group several targeting options into one and offer them to advertisers. A group is a folder of options, and advertisers select the whole group or the options inside it.

​
Creating an Option Group

  1. Click the + Add Option button and select Option group for Type.
  2. Enter the Group name.
  3. Enter the Context ID. You can leave it empty if the group has sub-options.
  4. Set the Show sub-options to advertisers switch.
  5. Click the Add button.
To group options you already created, check the targeting options and click the Group options button.

​
Showing Sub-options

The Show sub-options to advertisers switch only changes what advertisers can select. It doesn’t affect ad serving.

​
Matching Scope

A group matches both its own Context IDs and the Context IDs of its sub-options.

​
Limits

  • An option group needs at least one sub-option or one Context ID of its own.
  • A group can’t contain another group. Sub-options are always regular options.
  • An option group’s own Context IDs can’t overlap with the own Context IDs of another option group in the same project.
  • You can’t change an option’s type after you create it, and you can’t choose a type when adding a sub-option.

​
Editing, Ungrouping, and Deleting

Use the menu (⋮) on a targeting option row to select Edit group, Ungroup, or Delete. In the edit group window, click Complete to save.
  • Ungroup: The group’s Context IDs are deleted with it, and its sub-options stay as top-level options.
  • Delete: Deleting a group also deletes its sub-options. Move them out of the group first to keep them.
  • If a running campaign uses the group, ungrouping or deleting it can change that campaign’s reach or let it serve without this targeting condition. We recommend doing this after the campaign ends.
You can also create and change option groups with the Context Targeting API. Note that deleting a group through the API promotes its sub-options to top-level options, while deleting it in the console also deletes them.

​
Next Steps

Selling Targeting

Learn how to connect to ad products and set required targeting

Context Targeting API

Manage targeting options and Context IDs automatically from your server

​
FAQ

It’s best to use your existing content classification system as-is. You don’t need to create new ones—just pass existing category codes or tags as context IDs.
Yes, context targeting is based on the content of the page the user is currently viewing. Since no user information is needed, it applies equally to non-logged-in users.
Effective for services with clear content classification. If page context is distinct—like news app article categories, commerce product categories, or real estate app listing types—you can provide valuable targeting to advertisers.