> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adrop.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 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 and measure ad performance with conversion tracking.

***

## 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              | Key Events                                |
| ------------ | ------------------------ | ----------------------------------------- |
| **COMMON**   | Common app/web actions   | Sign-up, login                            |
| **COMMERCE** | Commerce-related actions | Purchase, add to cart, checkout initiated |
| **LEAD**     | Lead generation actions  | Inquiry completion, consultation request  |

***

## 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.

<Note>
  The preset event list can be viewed on the Events page in the console.
</Note>

***

## Using the Events Page

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

### Event List

The Events page displays all registered events in a list. You can view each event's category, name, and description at a glance.

### Event Details

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

* **Parameter Tree**: Structure and data types of parameters included in the event
* **Data Log**: Sample logs of recently received event data

***

## 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 **Event** as the filter type.
4. Select the event to use.
5. Set additional conditions on event parameters if needed.

### 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 Purchase event occurred            |
| **Cart Added but Not Purchased**      | AddToCart event occurred AND Purchase event not occurred |
| **VIP Purchasers**                    | membership is "VIP" AND Purchase event occurred          |

***

## Technical Specifications

| Item                      | Details          |
| ------------------------- | ---------------- |
| **Data Refresh Interval** | Every 10 minutes |
| **Data Retention Period** | 18 months        |

***

## SDK Integration

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

<CardGroup cols={2}>
  <Card title="Android SDK" icon="android" href="/sdk/android/targeting#event-tracking">
    Set up event tracking in Android
  </Card>

  <Card title="iOS SDK" icon="apple" href="/sdk/ios/targeting#event-tracking">
    Set up event tracking in iOS
  </Card>
</CardGroup>

***

## Next Steps

{/* <Card title="Conversion Tracking" icon="chart-line" href="/targeting/conversion-tracking">
Learn how to measure conversions after ad clicks
</Card> */}

<Card title="Creating Audience Targeting" icon="users" href="/targeting/audience">
  Create targeting by combining properties and events
</Card>

***

## FAQ

<AccordionGroup>
  <Accordion title="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."
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="How quickly is event data reflected?">
    Event data is reflected every 10 minutes. It may take up to 10 minutes for events collected via SDK to be applied to targeting conditions.
  </Accordion>

  <Accordion title="How long is event data retained?">
    Event data is retained for 18 months. Data older than 18 months is automatically deleted.
  </Accordion>
</AccordionGroup>