List Pixels - Markifact

Lists the Spotify conversion pixels available to an ad account, optionally with their configured events and hourly event counts.


App	Spotify Ads
Operation ID	`spotify_ads_list_pixels`
Type	Action
Connection	`spotify_ads` (required)
Credits per run	1
Agent / MCP tool	Yes

Inputs

Field	Type	Required	Default	Description
`account`	DynamicAccount	Yes	-	Select a Spotify Ads account. Pixels belong to the business that owns the account, which is resolved automatically.
`include_events`	boolean	No	`False`	Include each pixel’s configured events (page view, purchase, lead, add to cart) with their last activity.
`include_historical_events`	boolean	No	`False`	Include hourly event counts per pixel. Requires date_range, and turns on include_events.
`date_range`	DateRange	No	-	Window for the hourly event counts. Required with include_historical_events.
`filters`	array of FilterItem	No	-	Additional filters to apply when retrieving pixels. The available fields to filter by are: - id: Filter by pixel ID - name: Filter by pixel name - domain: Filter by the website domain the pixel is installed on Filters are combined using AND logic. If you want to use OR logic, use relevant operators like REGEXP_MATCH or IN_LIST.
`limit`	integer	No	`100`	Maximum number of pixels to return. Default: 100.

DateRange

Field	Type	Required	Default	Description
`start`	string	No	-	The start date of the date range to query, format: YYYY-MM-DD or dynamic node reference like {{nodeId__data.start_date}}. Required when preset is ‘FIXED’ or ‘CUSTOM’.
`end`	string	No	-	The end date of the date range to query, format: YYYY-MM-DD or dynamic node reference like {{nodeId__data.end_date}}. Required when preset is ‘FIXED’ or ‘CUSTOM’.
`preset`	string	No	-	Predefined date ranges or input modes: - Use ‘FIXED’ or leave empty when you want to specify exact dates (YYYY-MM-DD format) in start/end fields - Use ‘CUSTOM’ when you want to use dynamic values from other nodes ({{nodeId__data.start_date}} format) in start/end fields - Use other presets (TODAY, YESTERDAY, LAST_7_DAYS, etc.) for predefined date ranges (start/end will be ignored) When using ‘FIXED’ or ‘CUSTOM’, both start and end fields are required.
`compare`	CompareOptions	No	-	Optional comparison date range settings. ALWAYS use this field for comparisons; DO NOT create additional requests or nodes, as the backend returns current, comparison, and delta metrics in a single call.

Field	Type	Required	Default	Description
`field`	string or SelectableOption	Yes	-	The field to filter on, must be one of the current selected metrics or dimensions.
`operator`	string	Yes	-	The operator to use for filtering. Must be one of the supported values. Use REGEXP_MATCH to search/filter by multiple OR values like ’.(summer\|holiday).’
`value`	string	Yes	-	The value to filter by. Can be a string, number, regex, or a list of strings.

CompareOptions

Field	Type	Required	Default	Description
`start`	string	No	-	The start date of the comparison range, format: YYYY-MM-DD. Optional if preset is provided.
`end`	string	No	-	The end date of the comparison range, format: YYYY-MM-DD. Optional if preset is provided.
`preset`	string	No	-	Predefined comparison ranges. When provided, start and end will be ignored.
`comparison_format`	string	No	`rows`	Comparison output layout: ‘rows’ returns separate rows for current, comparison, and delta along with date ranges; ‘columns’ returns a single row with delta values only as additional _pct or _change columns depending on comparison_value_type.
`comparison_value_type`	string	No	`percentage`	Value type: ‘percentage’ or ‘absolute’

SelectableOption

Field	Type	Required	Default	Description
`value`	string	Yes	-
`label`	string	Yes	-

Output

Type: List[Dict] Returns pixels with id, name, domain, dataset_id and, when requested, their events and hourly event counts. Fields: dynamic (depend on the inputs)