ECONDA Specific Information

Ensuring pIRequ-ID Consistency in ECONDA Tracking

Overview
When implementing ECONDA tracking via JENTIS, it is essential to maintain pIRequ-IDconsistency with the previously tracked pageview. If the pIRequ-ID does not match the previous pageview's ID, events will not be registered correctly in ECONDA.

Identifying the Issue
You may encounter this issue if your events fail to register in ECONDA. Upon inspection, if the pIRequ-ID does not match the preceding pageview's ID, tracking continuity is disrupted, leading to inaccurate data collection.

Preventing the Issue
To ensure pIRequ-ID consistency and avoid tracking errors, follow these best practices:

• Ensure Proper ID Passing

  • Always pass the correct pIRequ-ID between pageviews and events.

• Test Tracking in a Preview Environment

  • Before deploying any changes, verify tracking in a preview environment.

  • Use debugging tools to confirm that the pIRequ-ID aligns correctly with the intended pageview.

• Keep Your JENTIS DCP Updated

  • Regular updates help prevent tracking issues by incorporating bug fixes and improvements.

By maintaining correct pIRequ-ID assignments, you ensure seamless event tracking and reliable user activity reporting in ECONDA.