Event/Conversion FAQ

Why Is Session Data Different from Event Data

Attribution Logic

Event count: Each time a configured event occurs, an event packet is sent and collected. Session count: When a user begins a session and revisits before the session ends, it is counted as 1 session regardless of how many visits occur.

A user may trigger the same event multiple times within a single session, so it is normal for session count to be less than or equal to event count.

Conversion and Page Group Are Set Up but Data Is Not Flowing In Correctly

1. Conversions and page groups only begin accumulating data after they are configured. Please verify that the observation time range is correct.

2. The user's visit may not have ended yet. Ptengine's default session timeout is 30 minutes, and some data will only appear after the session is settled.

3. If conversion data cannot be confirmed, it may be because the tracking code is not installed on the page where the conversion is configured. Additionally, Ptengine records conversions on a per-session basis. Even if a user completes multiple conversions in a single session, only one will be counted.

4. If the conversion page is reached by crossing domains, there may be a cross-domain issue. When crossing domains, the session is interrupted, so you need to configure cross-domain settings to link cross-domain sessions.

Visual Event Is Set Up but No Data Is Flowing In

When the event is correctly configured Time delay -- If the event has been correctly set up, data will typically be reflected in the management dashboard within approximately 2 hours. The observation time range may be incorrect. Almost all Insight features begin accumulating data only after setup. If data is not appearing, please check the selected time period. After setting up an event, measurement generally begins about 5 minutes later.

When the code is not correctly deployed Common setup errors: a. The page you want to measure does not match the measurement scope. In the screenshot above, source = the URL used when setting up the event, element = the selector for the specified element, measurement scope = the page condition for event measurement scope. For example, if you want to measure the following three URLs but specify the measurement scope as pages containing "https://www.aaa.com/event/", then URLs 2) and 3) will not be included: 1)https://www.aaa.com/event/ 2)http://www.aaa.com/event/ 3)https://aaa.com/event b. The specified element does not exist on the page or its position has changed. If the element designated as an event does not exist on the page or its position has changed, the previously configured event will not be tracked.

Solution -- When the configuration is incorrect a. Measurement scope mismatch. Please reconfirm whether the measurement scope you specified matches the actual page URLs you want to measure. For details on matching rules, refer to the following article: About Matching Rules. If there is a mismatch, delete the event and reconfigure it. Currently, it is not possible to modify an event that has already been set up.

b. The specified element does not exist on the page. In this case, please reconfigure the event.