> For the complete documentation index, see [llms.txt](https://support.gamoshi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.gamoshi.com/gamoshi-wiki/general-information/payment-events-review.md). # Payment Events Review ## Overview This article explains the payment events used by the Gamoshi platform, when each event is included in an ad response, and how the corresponding events are counted in the Analytics module. The applicable payment events depend on: * The media type. * Whether the activity occurs on a site or in an app. * The OpenRTB version supported by the advertiser and publisher. * The format of the ad response. *** ## Understanding Payment Events In Real-Time Bidding (RTB), a payment event is the moment when an advertiser is charged. The applicable event depends on the campaign’s media type and pricing model. After an auction is won, the ad response can include one or more tracking pixels or event URLs. When the relevant event occurs, the corresponding tracking mechanism sends a server call indicating that the event was recorded. Multiple events can be included in a single response. However, not every recorded event is considered the default billable event. *** ## Payment Event and Pixel Types ### Page Pixel A Page pixel fires when the advertiser’s script is served on a page. It confirms that the script reached the page, but not that it was executed. This event can assist with troubleshooting when no other events are recorded. For example, it can indicate that the script reached the page but was not executed due to a technical or other delivery issue. **When it is used:** Display activity, including banner and native activity, on sites and in apps. ### BURL Event OpenRTB 2.5 and later support the BURL, or Billable URL, object across media types and sources. The BURL is used by the publisher to indicate that a billable impression occurred. **When it is used:** The BURL object is included in the response when it is provided and supported by the advertiser. It can be used across all media types and in both site and app environments. ### ADM Pixel In OpenRTB, ADM stands for Ad Markup. The ADM field in the bid response contains the advertisement or a reference or script used to retrieve it. Depending on the campaign and inventory, the ad markup can include an image, text, video, another multimedia format, or a reference to a content delivery system. An ADM pixel is embedded in the advertisement and fires when the applicable impression event occurs. **When it is used:** The ADM pixel is included in display responses for banner and native activity on sites and in apps. For MRAID responses in app activity, the ADM pixel is omitted, and an MRAID pixel is included instead. The ADM pixel is the default billable event for non-MRAID banner activity on the Gamoshi platform. ### MRAID Pixel MRAID, or Mobile Rich Media Ad Interface Definitions, is an IAB standard for rich-media advertisements in mobile applications. It provides standardized commands that allow supported ads to perform actions such as expanding, resizing, and closing within the application. For an MRAID creative to run, the publisher’s incoming request must declare MRAID support in the request’s API attribute. The API values identify the frameworks supported by the ad placement, such as MRAID, VPAID, or ORMMA. An MRAID pixel is embedded in an MRAID-compliant creative and records the MRAID impression. An impression generated by an MRAID ad is called an **MRAID impression**. **When it is used:** The MRAID pixel is included when the ad response uses MRAID. The response also includes a Page pixel and, when supported by the protocol version, a BURL. The ADM pixel is omitted. The MRAID impression is the default billable event for MRAID banner activity. ### VAST Events VAST, or Video Ad Serving Template, is an IAB specification for serving and tracking video advertisements across video players, platforms, and devices. VAST supports multiple tracking events. When an event occurs, its tracking pixel fires, sending the event information to the ad server. The principal VAST events are: * **Video Impression:** Fires when the video ad is loaded on the page. * **Start:** Fires when the video begins playing. This is the default billable event for video activity on the Gamoshi platform. * **First Quartile:** Fires when 25% of the video has played. * **Midpoint:** Fires when 50% of the video has played. * **Third Quartile:** Fires when 75% of the video has played. * **Complete:** Fires when the video finishes playing. * **Pause:** Fires when the video is paused. * **Resume:** Fires when playback resumes. * **Mute:** Fires when the video’s sound is muted. * **Unmute:** Fires when the video’s sound is restored. * **Fullscreen:** Fires when the video is expanded to fullscreen mode. * **Close:** Fires when the video is closed before playback finishes. * **Skip:** Fires when the user skips the video before it finishes. **When they are used:** Video activity on sites and in apps. *** ## Default Billable Events The Gamoshi platform uses the following default billable events: * **Display activity:** ADM impression or MRAID impression. * **Video activity:** Video Start event. *** ## Payment Events in Analytics ### Page Views **Availability:** Hidden metric that can be added to the default view. **Counts:** Page pixels. This metric counts events in which the ad was loaded on a page. ### Imp **Availability:** Included in the default view. **Counts:** ADM pixels and MRAID pixels. This metric counts events in which an ADM or MRAID impression pixel fired. ### MRAID Imp **Availability:** Hidden metric that can be added to the default view. **Counts:** MRAID pixels. This metric counts events in which an MRAID ad ran and an MRAID impression fired. ### BURL Event **Availability:** Hidden metric that can be added to the default view. **Counts:** BURL events. This metric counts events in which the BURL fired, indicating that the publisher declared a billable event when supported by the publisher’s protocol version. ### Video Impression **Availability:** Included in the default view. **Counts:** Video Impression pixels included in the VAST object. This metric counts events in which a video ad was loaded on a page. ### Video Start **Availability:** Included in the default view. **Counts:** Video start pixels included in the VAST object. Fires when the video begins playing. ### Other Video Events All other VAST video events are available as hidden metrics and can be added to the default view. *** ## Related articles * [Available payments events](/gamoshi-wiki/general-information/available-payments-events.md) * [Analytics](/gamoshi-wiki/analytics.md) * [How to create a PE Campaign](/gamoshi-wiki/how-to-guides/how-to-create-a-pe-campaign.md) * [How to Implement Third-Party Pixel Tracking](/gamoshi-wiki/how-to-guides/how-to-implement-third-party-pixel-tracking.md)