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

# Cafe24 data reference

> See which Cafe24 user properties Notifly stores and which events it receives from your store. Use this data to target and personalize campaigns.

## User properties

The properties below are available for registered Cafe24 members only.

| Property | Type | Description |
| - | - | - |
| `name` | Text | Name |
| `nick_name` | Text | Nickname |
| `shop_no` | Int | Shop number. Defaults to `1` for single-store setups. |
| `job` | Text | Occupation |
| `job_class` | Text | Job category |
| `sms` | Text | SMS consent. `T` means opted in and `F` means not opted in. |
| `news_mail` | Text | Email newsletter consent. `T` means opted in and `F` means not opted in. |
| `member_type` | Text | Member type. `p` = individual, `c` = business, `f` = foreign member. |
| `member_authority` | Text | Member role. `C` means regular member, `P` means primary admin, `A` means secondary admin, and `S` means supplier. |
| `country_code` | Text | Country code provided at sign-up. For example, `KOR` for South Korea. |
| `city` | Text | City |
| `lifetime_member` | Text | Lifetime membership. `T` means lifetime member and `F` means regular member. |
| `gender` | Text | Gender. `M` means male and `F` means female. |
| `birthday` | Text | Date of birth (`YYYY-MM-DD`) |
| `group_no` | Int | Group number |
| `group_name` | Text | Group name |
| `interest` | Text | Interests |
| `created_date` | Text | Sign-up date and time (ISO 8601) |
| `last_login_date` | Text | Last login date and time (ISO 8601) |
| `member_authentication` | Text | Member verification status. `T` means verified, `F` means unverified, `B` means special management member, and `J` means member under 14. |
| `use_blacklist` | Text | Blocklist status. `T` = on the blocklist, `F` = off the blocklist. |
| `join_path` | Text | Sign-up platform. `P` means PC and `M` means mobile. |
| `available_points` | Int | Available reward points |
| `returned_points` | Int | Reward points pending refund |
| `total_points` | Int | Total reward points |
| `unavailable_points` | Int | Unavailable reward points |
| `used_points` | Int | Reward points spent |
| `all_credits` | Int | Available store credit |
| `member_total_credits` | Int | Store credit in the member table |
| `refund_wait_credits` | Int | Store credit with a pending refund request |
| `total_credits` | Int | Total store credit |
| `used_credits` | Int | Store credit spent |

## Built-in events

Cafe24 event names start with `cafe24__`.

> [!WARNING]
>
> Some Cafe24 events occur on the server and can't trigger web popups. Check the **Can trigger a web popup** column before choosing a trigger.

| Event name | Event parameters | When it fires | Can trigger a web popup | Notes |
| - | - | - | - | - |
| `cafe24__pageview_<pathname>` | None | User views a page | Yes | Legacy page-view event. Use `cafe24__pv` for new setups. |
| `cafe24__pv` | `full_url`: Full URL (Text) `pathname`: Page path (Text) `search`: Query string (Text) `hash`: Hash (Text) `hostname`: Page hostname (Text) `protocol`: Protocol (Text) `port`: Port number (Text) `origin`: Page origin (Text) `query.<key>`: Query string key and value (Text) | User views a page | Yes | Supported since 2024-08-21. |
| `cafe24__sign_up` | None | User signs up | No | |
| `cafe24__login` | None | User logs in | Yes | |
| `cafe24__add_cart` | `product_no`: Product number (Int) `product_price`: Product price (Int) `variant_code`: Product code (Text) | User adds an item to the cart | Yes | |
| `cafe24__add_wishlist` | None | User adds an item to the wishlist | Yes | |
| `cafe24__order_completed` | `shop_no`: Multi-store shop number (Int) `currency`: Currency (Text) `order_date`: Order date and time (Text) `name`: Buyer name (Text) `first_order`: Whether this is the first order (Bool) `total_price`: Total order amount (Int) `membership_discount_price`: Member discount amount (Int) `actual_payment_price`: Amount actually paid (Int) `mileage_spent_price`: Amount paid with reward points (Int) `product_codes`: Ordered product codes (Array) `product_names`: Ordered product names (Array) `product_names_text`: Ordered product names formatted as text (Text) `order_id`: Order number (Text) `bank_account_no`: Bank account number (Text, or null if unavailable) | Order completes | No | |
| `cafe24__order_canceled` | Single cancellation: all parameters from `cafe24__order_completed` plus `cancel_date` (Text) Batch cancellation: `shop_no`, `order_id`, `product_names`, and `product_names_text` | Order is canceled | No | |
| `cafe24__order_started` | `cart_items`: Product numbers on the checkout page (Array of Int) `total_price`: Total price of products on the checkout page (Int) | User opens the checkout page | Yes | |
| `cafe24__user_group_changed` | `new_group`: New group name (Text) | A Cafe24 member's group changes | No | |
| `cafe24__shipping_in_progress` | `order_id`, `shop_no`, `currency`, `order_date`, `name`, `first_order`, `total_price`, `product_codes`, `product_names`, and `product_names_text` `bank_account_no`: Bank account number (only for individual shipping updates) `shipping_type`: Shipping type (`국내` for domestic or `해외` for international) `wished_delivery_date`: Requested delivery date (yyyy-MM-dd) `wished_delivery_time`: Requested delivery time `store_pickup`: Whether the order is for store pickup (Bool) `shipping_message`: Shipping message (Text) | Shipping starts | No | |
| `cafe24__shipping_completed` | All parameters from `cafe24__shipping_in_progress` | Shipping is completed | No | |
| `cafe24__shipping_hold` | All parameters from `cafe24__shipping_in_progress` | Shipping is placed on hold | No | |

Notifly records order completion, cancellation, and shipping status updates only for Cafe24 members. Guest orders do not generate these events.

> [!WARNING]
>
> Use `cafe24__pv` to track page views in new campaigns. It includes the page path and other URL details. See how to [filter page views in a Cafe24 campaign](https://docs.notifly.tech/en/user-guide/integrations/cafe24/campaign-examples.md).

> [!TIP]
>
> `product_names` lists every product name in the order. In order and shipping events, `product_names_text` shows the first product name, followed by a count of the other items. For example, `['상품1', '상품2', '상품3']` becomes `상품1 외 2건` (상품1 and 2 more).

## Add custom events

You can use Google Tag Manager (GTM) to track custom events in addition to the built-in events. See [Track custom events with Google Tag Manager](https://docs.notifly.tech/en/user-guide/integrations/cafe24/cafe24-gtm.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.