---
search:
  tags:
    - Pixels
    - GET
seo:
  description: >-
    Available on: Meta. Reference for the GET
    /observe/{advertiserId}/pixels/{pixelId}/events endpoint in the AdCrunch
    API.
sidebar:
  label: List the events of a Meta Pixel
  badge: GET
title: List the events of a Meta Pixel
type: openapi-operation
---
**Available on:** [![Meta](/providers/meta.svg)](https://docs.adcrunch.dev/connect/providers)

Live read. Asks Meta now for the events that one Meta Pixel received in the last `days` days, with one row for each event name: its `count` in the window, and `lastSeenAt`, the start of the last hour with an event of this name.

Read it before you create an ad set that optimizes for an event. An ad set that optimizes for an event that never fires gets no delivery. The counts are the ones that Meta reports for the Pixel. Meta keeps 7 days of events in hourly results, and the top 100 event names of each hour.

The Pixel must be a Pixel of the ad account of the advertiser: a row of `GET /observe/{advertiserId}/pixels`. Another Pixel answers `404`, with `error` of `not_found`, and AdCrunch reads none of its events.

An advertiser that your organization does not own answers `404`, with `error` of `not_found`. An advertiser that does not exist, and one that is not a Meta ad account, answer the same.

AdCrunch stores nothing from this read. Each request counts against the rate limits of Meta.

The answer has no page: it holds every event name of the window.

`GET /observe/{advertiserId}/pixels/{pixelId}/events`