Event Management shows how your User Event API integration is performing over time. You can see how many events Moloco accepted, how many requests were rejected, which event types you are sending, and which response codes your rejected requests returned.

The page is read-only. It visualizes data that Moloco Commerce Media already collects from your event requests, so opening it has no effect on ad serving, budgets, billing, or attribution, and you do not need to change your integration to use it.

Availability

Currently the Event Management UI is enabled per platform and is not enabled automatically. If you do not see it in your Portal, contact your Moloco representative.

Where to find it

In the MCM Portal, open the Developer section and select Event Management.

Choose a date range

Use the date range control at the top of the page to set the period you want to review, up to the last 90 days. Every metric, chart, and table on the page reflects the range you select.

Summary metrics

 

A single request can carry more than one event, so Accepted Events and Total API Requests are not expected to match.

Accepted events over time

The volume chart plots accepted events across the selected range, broken down by event type, such as 

• HOME
• PAGE_VIEW
• ITEM_PAGE_VIEW
• SEARCH
• ADD_TO_CART
• PURCHASE
• ADD_TO_WISHLIST

Use it to confirm that traffic patterns look the way you expect, for example a drop after a release or a spike during a promotion.

For the full list of event types and the fields each one requires, see User event data specifications.

Breakdown by event type

The breakdown table lists each event type you sent in the selected range with:

• Accepted event count
• Share of total accepted volume
• Rejected request count
• Rejection rate

This is the fastest way to tell whether a problem affects your whole integration or only one event type. A healthy integration usually shows browsing events as the largest share and conversion events as a much smaller share; a conversion event type that drops to zero, or a single event type with a high rejection rate, points to a change on the sending side.

Rejected requests and response codes

The rejection charts show rejected requests over time grouped by the response code Moloco returned, alongside the rejection rate trend for the same range.

Use the response codes to narrow down the cause:

• A rise in client error codes usually means the payload changed – a missing required field, an invalid value, or an unexpected format.
• A rejection rate that climbs at a specific time of day often points to a batch job or a scheduled export rather than live traffic.
• A rate that stays flat and low while volume moves is normal.

Once you know which event type and response code are involved, correct the payload on your side and confirm on this page that the rejection rate returns to its previous level. For guidance on outages and on resending events that were never delivered, see User Event API failure protocol.

A typical check

1. Set the date range to cover the period you want to compare.
2. Read the four summary metrics to see whether the issue is volume, rejections, or both.
3. Open the breakdown table to find the event types involved.
4. Check the response codes for those rejections.
5. Fix the payload or the sending job, then return to the page to confirm the rejection rate has recovered.

Related pages

• User event data specifications — event types, required fields, and payload rules that determine whether a request is accepted.
• User Event API failure protocol — what to do when events are lost or the API is unavailable, including how to resend events.
• Google Tag Manager integration guide — sending user events through a server-side tag manager container.