Mapp Intelligence supports two main request types: Page and Event. Each type is suited for a different kind of interaction and determines how tracking data is processed.
Request Type | Use Case | Triggers |
|---|---|---|
Page | Full page loads | Generates a page impression |
Event | User actions without reload (e.g. clicks, scrolls, video views) | Generates an event, media view, or form view |
You choose the request type when configuring your tag in GTM.
You can find a detailed list of supported parameters here.
Page Request
Used to track full page loads and related page-level information
Each page request creates a page impression in Mapp Intelligence
Required as a base for all further tracking
Best Practice
Every GTM implementation should include at least one tag with Page request type to track page views reliably.
Event Request
Use this request type to track user actions within a page. It covers various interaction types and supports automatic as well as custom tracking.
Common Use Cases:
Clicks on buttons or non-HTML links (e.g., AJAX)
Scroll tracking or time-based engagement
Form submissions and cancellations
Media playback tracking (e.g., video/audio players)
SPA navigation or lazy-loaded content
Subtypes:
Media Request – tracks player actions like play, pause, seek, etc.
Form Request – tracks form field status and submit behavior
Trigger Behavior:
Event requests should always fire after the Page request
Multiple event requests can be triggered on a single page load
Options for Automatic Event Tracking
When configuring the GTM Template, you can enable:
Track HTML links automatically → fires an event on every link click
Enable form tracking → fires an event when a form is submitted or cancelled