Start of the reporting period (inclusive). Format: YYYY-MM-DD.

End of the reporting period (inclusive). Format: YYYY-MM-DD.

Specify one or more metric names to include in the response. Only the selected metrics will be returned within the metrics object for each result item.

Supported values: likes, comments, shares, clicks, impressions, reach, engagements, views, engagementRate, postsCount, estimatedValueGenerated, cpe, cpm, paidLikes, paidComments, paidShares, paidImpressions, paidEngagements, paidEngagementRate, paidReach, paidViews

Metric availability depends on the applied platform or contentType filters. Some metrics are restricted to specific content types (for example, crosspostedFacebookOnlyViews is only available for Instagram Reels). Requesting unsupported metrics will result in a 400 error, along with a list of valid metrics for the current filters.

Supported array formats: param=a,b,c (comma-separated), param=a&param=b (repeated key), or param[]=a&param[]=b (bracket syntax).

Filter results to specific instances. When omitted, the request is evaluated against every instance associated with your OAuth client; supply one or more values to narrow the response to a subset. Values must be drawn from the set bound to your client credentials — requesting an instance outside that set returns 403 with type: ANL_00403.

Supported array formats: param=a,b,c (comma-separated), param=a&param=b (repeated key), or param[]=a&param[]=b (bracket syntax).

Filter results to specific campaigns. When omitted, all campaigns are included.

Supported array formats: param=a,b,c (comma-separated), param=a&param=b (repeated key), or param[]=a&param[]=b (bracket syntax).

Filter by top-level platform. Selecting a platform includes all its content types (e.g. instagram includes instagram_post, instagram_reel, instagram_story).

Cannot be combined with contentType — provide only one of the two.

When omitted (and contentType is also omitted), all platforms are included.

Supported array formats: param=a,b,c (comma-separated), param=a&param=b (repeated key), or param[]=a&param[]=b (bracket syntax).

Filter by specific content type for granular filtering beyond top-level platforms.

• instagram_post, instagram_reel, instagram_story — specific Instagram content formats
• facebook_post, facebook_live, facebook_group, facebook_reel — specific Facebook content formats
• tiktok, youtube_video, youtube_shorts — platform-specific types

Cannot be combined with platform — provide only one of the two.

When omitted (and platform is also omitted), all content types are included.

Supported array formats: param=a,b,c (comma-separated), param=a&param=b (repeated key), or param[]=a&param[]=b (bracket syntax).

Controls which date dimension is used for filtering.

• post_date (default): filters by the date the content was originally published. Best for analyzing content output and creator activity over time.
• performance_date: returns metrics recorded within the requested date range, regardless of when the content was originally published. Best for understanding how campaigns performed during a specific reporting window.

Example: a post published on Jan 5 that receives engagement on Feb 10 will appear in a Feb 1–28 query with performance_date, but in a Jan 1–31 query with post_date.

Maximum number of items to return per page. Choose any value on the first request, then keep it unchanged on every subsequent request that passes a nextCursor from this endpoint. To change the page size, start a new walk by omitting nextCursor.

Opaque cursor returned by the previous page. Omit on the first request. Cursors are tied to the query parameters of the request that produced them; to paginate, keep every parameter identical across requests and only vary nextCursor. To change filters, sort, or limit, start a new walk by omitting nextCursor.

Controls the time bucket size for the timeseries data.

Each data point includes startDate (inclusive) and endDate (inclusive) indicating the bucket boundaries. Partial buckets are returned at the edges of the requested date range.

Buckets with no activity for the selected instances, filters, and date range are omitted from the response — the returned series can therefore contain gaps. For example, a month-granularity request over six months may return fewer than six data points if some months had no posts, impressions, or paid spend. Clients that need a contiguous series should fill missing buckets locally from the requested date range and granularity.