# Verifying Event Firing

> **SUCCESS** **Overview**
>
> You can verify in real-time whether the visual events you have configured are being measured correctly (firing) using your browser's Developer tool (inspection mode).

## Benefits

There is approximately a 30-minute to 1-hour time lag before data is reflected in Ptengine's event analysis screen. By using this feature, you can verify that it's working correctly right after configuring the event without having to wait. Additionally, if there are any configuration errors, you can quickly discover and fix them.

## Common Use Cases

When you want to test whether a newly configured visual event is being measured correctly right after setup

When event values are not reflected in the analysis screen and you want to investigate the cause

When you want to confirm that events are firing normally on both PC and smartphone

## Verification Method

You can verify the event firing status by following the steps below.

### 1. Open the page where the event is configured

Open the web page in your browser where the event you want to verify is configured.

### 2. Open Developer tool (Inspection mode)

Launch the "Developer tool" (also called developer tools or inspection mode), a feature of your browser.

**Windows**: `F12` key or `Ctrl + Shift + I`

**Mac**: `Command + Option + I`

### 3. Set up Developer tool

Once Developer tool is open, refer to the image below and perform the following 4 settings.

**① Device switching**: Switch between PC view and smartphone view as needed. Settings are often configured on the PC screen, but if you can confirm event firing on the smartphone screen, you can assume the PC screen is also working fine. However, for responsive pages, verification on the smartphone screen is recommended.

**② Select the "Network" tab**

**③ Check "Preserve log" and "Disable cache"**

**④ Enter "Ptengine"**

### 4. Click the element where the event is configured

On the page, click once on the element (such as a button or link) that was configured as the target for event measurement. ※ To prevent malicious clicks, consecutive clicks within 3 seconds are counted as one click. Please leave an interval of 3 seconds or more when testing.

### 5. Verify the measurement status

When you click the element, a line starting with "collect\~" will appear in the Network tab of Developer tool.

Click on the "collect\~" line that appears.

Select the "Payload" tab (or "payload") in the details screen.

If the displayed information contains both **"event: the event name you configured"** and **"type: "track""**, the event is firing and being measured correctly. When you can confirm this, the values will be reflected in Ptengine's "Event Analysis" screen after 30 minutes to 1 hour.

> **DANGER** If an OC packet like the image below is displayed, it means the event is not firing. There may be a need to configure events for each device, so please check [this article](/en/insight/event/verify-firing.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://helps.ptengine.com/en/insight/event/verify-firing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.