Events

Events are user behavioral data such as purchases and adding to cart. By using events, you can add behavior-based conditions to audience targeting.

---

What are Events?

Events are behavioral data representing actions users perform in apps or on the web. They record specific user actions such as purchases, adding to cart, sign-ups, and inquiry completions.

While properties represent user attribute information (age, gender, membership tier, etc.), events represent actions that users have actually performed.

Type	Description	Examples
Properties	User attribute information	Age, gender, membership tier, region
Events	User behavioral data	Purchase, add to cart, sign-up, inquiry completion

By using events, you can add behavior-based targeting conditions such as “users with purchase history,” enabling more precise audience groups compared to using properties alone.

---

Event Categories

Events are classified into three categories based on their nature.

Category	Description	Preset Events
Common User Actions	Basic in-service actions	App Open, Sign Up, Push Click, Page View, Element Click
Commerce & Payments	Actions at each stage of the purchase funnel	View Item, Add to Wishlist, Add to Cart, Begin Checkout, Purchase
Lead Collection & Inquiries	Actions that show inquiry intent	View Content, Begin Lead Form, Submit Lead

---

Event Presets

Ad Control provides frequently used events as system presets by default.

• Preset events can be used immediately without separate registration.
• Preset event names and parameters cannot be modified.
• Only preset events can be selected as targeting conditions.

The preset event list can be viewed on the Events page in the console.

---

Using the Events Page

Click Event in the console left menu to navigate to the Events page.

Event List

The Events page lists the preset events by category. For each event, you can see its name, event and user counts over the last 30 days, when it was last collected, and its collection status at a glance.

Event Details

Click an event to open the Event Detail modal. The detail modal shows the following information:

• Status, Events (30d), Users (30d), Last Collected: Collection status, event and user counts over the last 30 days, and when the event was last collected
• Parameters: Keys and data types of the parameters included in the event. Click Integration Guide to see the SDK Integration guide.
• Data Collection Log: Up to 100 event records collected in the last 24 hours

After integrating the SDK, check Last Collected and Data Collection Log to confirm that events are being collected.

---

Using Events in Audience Targeting

When creating audience targeting, you can add events as conditions in addition to properties.

Adding Event Conditions

1. Create targeting in Targeting → Audience.
2. Click + Filter in condition settings.
3. Select the Event tab.
4. Select the event to use.
5. Set the details of the condition, and add conditions on event parameters if needed.

An event condition is set in this order: who [did / did not do] [event] [aggregation] [operator and value] [period].

Item	Description
did / did not do	Choose whether to target users who performed the event (did) or users who didn’t (did not do)
Aggregation	Choose from Total Events, Sum, Average, Minimum, Maximum, and Distinct Count. Except for Total Events, you also select the event parameter to aggregate
Operator and value	Compare the aggregated result with a value using =, ≠, >, ≥, <, or ≤
Period	The last N hours, days, weeks, or months (Last). The default is 30 days, and the maximum is 90 days

If you select did not do, you don’t set the aggregation, operator, or value.

• You can add up to 5 event conditions per group.
• All event conditions in a targeting option must be connected the same way: all and or all or.
• The condition period is separate from the event data retention period (18 months).

Combining Properties and Events

Combining properties and events together enables more precise target groups.

Example: Commerce App Targeting

Targeting Option	Condition
Seoul Users with Purchase History	region is “Seoul” AND did Purchase (Total Events ≥ 1, Last 30 Days)
Cart Added but Not Purchased	did Add to Cart (Total Events ≥ 1, Last 30 Days) AND did not do Purchase (Last 30 Days)
VIP Purchasers	membership is “VIP” AND did Purchase (Total Events ≥ 1, Last 30 Days)

---

Technical Specifications

Item	Details
Data Collection	About every 10 minutes
Targeting (Audience) Update	Hourly
Data Retention Period	18 months

---

SDK Integration

To send events from your app, integrate event tracking in the SDK.

Android SDK

Set up event tracking in Android

iOS SDK

Set up event tracking in iOS

---

Next Steps

Creating Audience Targeting

Create targeting by combining properties and events

---

FAQ

What is the difference between events and properties?

Properties are user attribute information (age, gender, membership tier, etc.), while events are user behavioral data (purchases, add to cart, etc.). Properties indicate “who the user is,” and events indicate “what they did.”

Can I modify preset events?

Preset event names and parameters cannot be modified. They are standard events provided by the system and should be used as-is for consistent data collection and analysis.

How quickly is event data reflected?

Events sent from the SDK are collected about every 10 minutes. They are applied to targeting conditions at the hourly audience update, so it can take more than an hour.

How long is event data retained?

Event data is retained for 18 months. Data older than 18 months is automatically deleted.