Real-time Logs

Real-time logs is a screen for instantly checking whether events collected to the server are actually arriving, used when verifying SDK integration, deep link configuration, and conversion events. You access it from the left menu under 이벤트 > 실시간 로그, and events are displayed in reverse chronological order starting from the most recent.

1. Use Cases

Situation	Usage
New SDK integration	Check whether events triggered from the app/web reach the server.
Deep link / tracking link verification	Check the link type (`DEEPLINK`/`TRACKING`) and the redirect result.
Attribution debugging	Check whether Click ID, channel, and campaign are mapped as intended.
Event parameter validation	Check the original transmitted parameters (JSON) in the detail view.

Event data in real-time logs is queried from MongoDB. Therefore, there may be a time lag in when it is reflected compared to aggregation-based statistical data such as attribution reports. We recommend checking immediate receipt on this screen, and viewing aggregated figures on the report screen.

2. Filters

You can narrow down the logs using the following conditions in the toolbar at the top of the screen. Changing a filter moves you to the first page.

Filter	Description
Search box (`이벤트명으로 검색...`)	Searches by event name. It is applied after entering text and pressing the `[검색]` button or the Enter key.
`발생시간`	Select a date range. The default is the last 7 days, and the end date includes up to the end of that day (23:59:59).
`링크 타입`	Select from All / `DEEPLINK` / `TRACKING`.
`리다이렉트 타입`	Select from All / `APP` / `STORE` / `WEB`.
`디바이스`	Select from All / Mobile / Desktop / Tablet / Other.
`플랫폼`	Select from All / iOS / Android / Web / Windows / macOS / Linux.

The search box must be applied by pressing the [검색] button or the Enter key, while the remaining dropdowns (link type, redirect type, device, platform) and the date range are applied immediately upon selection.

3. List Columns

The list is sorted in reverse chronological order by occurrence time, and each row displays the following columns.

Column	Description
Occurrence time	The time the event occurred (year-month-day hour:minute:second).
Event name	The name of the collected event (e.g., `install`, `purchase`, `login`).
Source	The environment where the event occurred. Displayed as App or Web.
Channel	The inbound channel mapped through attribution.
Click ID	The click identifier used for attribution (e.g., gclid, fbclid, ttclid, etc.).
Attribution ID	The attribution identifier linked to the event. It is used as the key to additionally look up attribution information in the detail view.
Link type	Either `DEEPLINK` or `TRACKING`.
Redirect type	The destination reached after clicking the link (`APP`/`STORE`/`WEB`).
Campaign	The campaign name mapped through attribution.
Ad group	The ad group name mapped through attribution.
Device	The device category (Mobile/Desktop/Tablet, etc.).
Platform	The device platform (iOS/Android/Web, etc.).

Columns with no value are displayed as -.

4. Detail View

Clicking a row in the list opens the detail view drawer on the right.

Area	Description
Top header	Displays the event name, occurrence time, and event ID (`_id`). You can copy the ID using the copy button next to the ID.
Event data	Displays the original event as JSON. It includes device/user/attribution information, transmitted parameters (`params`), SDK version, and more. You can copy the entire JSON using the copy button at the top right.
Attribution detail	Displayed only when the event has an Attribution ID. It shows the linked attribution device information (channel, Click ID, install time, expiration time, etc.) as JSON.

5. Pagination