List Account Pixels

The List Account Pixels node retrieves all Facebook pixels associated with your Meta Ads account, providing comprehensive tracking and configuration information for each pixel.

When to Use It

Audit all pixels connected to your Meta Ads account
Get pixel IDs for use in other tracking operations
Monitor pixel configuration and status
Check pixel ownership and business associations
Identify inactive or outdated pixels
Prepare data for pixel management workflows
Analyze first-party cookie status across pixels
Review automatic matching settings

Inputs

Field	Type	Required	Description
Account	Select	Yes	Select a Meta Ads account to list pixels from

Output

Returns an array of pixel objects with detailed information:

[
  {
    "id": "123456789012345",
    "name": "Website Pixel",
    "account_id": "act_123456789",
    "creation_time": "2023-01-15T10:30:00+0000",
    "owner_business_id": "987654321",
    "owner_business_name": "My Business",
    "last_fired_time": "2024-10-16T08:45:00+0000",
    "enable_automatic_matching": true,
    "first_party_cookie_status": "FIRST_PARTY_COOKIE_ENABLED",
    "has_1p_pixel_event": true,
    "is_crm": false,
    "is_unavailable": false,
    "match_rate_approx": 0.85,
    "matched_entries": 125000
  }
]

Key Fields Explained:

Field	Description
id	Unique pixel identifier
name	Display name of the pixel
creation_time	When the pixel was created
last_fired_time	Last time pixel received data
enable_automatic_matching	Whether automatic matching is enabled
first_party_cookie_status	First-party cookie configuration status
has_1p_pixel_event	Whether pixel has first-party events
match_rate_approx	Approximate match rate (0-1)
matched_entries	Number of matched data entries

Credit Cost

Cost per run: 1 credit

FAQs

What information does this node provide about my pixels?

This node provides comprehensive pixel information including:Basic Information:

Pixel ID and name
Creation date and owner business
Last activity timestamp

Configuration Details:

Automatic matching settings
First-party cookie status
CRM integration status

Performance Metrics:

Match rate approximation
Number of matched entries
Recent activity status

Use this data to:

Identify which pixels are active
Check configuration settings
Monitor performance metrics
Plan pixel optimization strategies

How do I use the pixel IDs from this output?

The pixel IDs returned by this node can be used in other Meta Ads operations:Common Use Cases:

Get Pixel Details: Use ID in “Get Pixel Details” node for configuration info
Get Pixel Stats: Use ID in “Get Pixel Stats” node for analytics data
Check CAPI Health: Use ID in “Check CAPI Health” node for conversion API metrics
Event Setup: Reference pixel ID when setting up conversion tracking

Pro tip: Save the pixel IDs as variables in your workflow to use across multiple tracking and analytics nodes.

What does the match rate indicate?

The match rate (match_rate_approx) indicates how well your pixel data matches with Meta’s user profiles:Match Rate Ranges:

0.8-1.0 (80-100%): Excellent - High-quality data with strong matching
0.6-0.8 (60-80%): Good - Decent matching with room for improvement
0.4-0.6 (40-60%): Fair - Moderate matching, optimization needed
Below 0.4 (40%): Poor - Significant matching issues

Factors Affecting Match Rate:

Quality of customer data (emails, phone numbers)
First-party cookie implementation
Conversion API setup and data quality
Privacy settings and user consent

Improve Match Rate:

Implement Conversions API (CAPI)
Use high-quality first-party data
Enable automatic matching
Ensure proper cookie consent flows

What does first_party_cookie_status mean?

How can I tell if my pixels are working properly?

Use these fields to assess pixel health:Activity Indicators:

last_fired_time: Recent timestamp indicates active pixel
has_1p_pixel_event: True means pixel is receiving first-party events
is_unavailable: False means pixel is functioning

Quality Metrics:

match_rate_approx: Higher rates (above 0.6) indicate good data quality
matched_entries: Higher numbers show good data volume
enable_automatic_matching: Should be true for optimal performance

Red Flags:

Very old last_fired_time (weeks/months ago)
Low match rates (below 0.4)
is_unavailable = true
No first-party events (has_1p_pixel_event = false)

Next Steps for Issues:

Check pixel installation on your website
Verify event configuration
Review Conversions API setup
Test pixel with Facebook Pixel Helper browser extension

What's the difference between CRM and regular pixels?

The is_crm field indicates the pixel type:Regular Pixels (is_crm = false):

Standard website tracking pixels
Track user interactions on your website
Used for retargeting and conversion tracking
Collect browsing behavior and events

CRM Pixels (is_crm = true):

Customer Relationship Management integration
Track offline conversions and customer data
Used for uploading customer lists
Focus on known customer interactions

Use Cases:

Regular pixels: E-commerce websites, lead generation, content sites
CRM pixels: Stores with offline sales, B2B businesses, subscription services

Data Sources:

Regular: Website visits, online purchases, form submissions
CRM: In-store purchases, phone orders, subscription renewals

How often should I check my pixel list?

Regular Monitoring Schedule:Weekly Checks:

Monitor last_fired_time for all active pixels
Check for any pixels showing is_unavailable = true
Review match rates for significant changes

Monthly Reviews:

Analyze match rate trends
Review automatic matching settings
Check for new or outdated pixels

Quarterly Audits:

Full pixel inventory and cleanup
Review ownership and business associations
Optimize pixel configuration based on performance

Immediate Checks Needed When:

Launching new campaigns or websites
Making significant website changes
Experiencing tracking or attribution issues
Setting up new conversion tracking

Automation Tip: Set up automated workflows to check pixel health and alert you to issues.

Can I manage multiple business accounts with this node?

Yes, but you need to run the node separately for each Meta Ads account:Multi-Account Management:

Select different accounts in the Account field
Run the node once per account you want to audit
Combine results if you need a consolidated view

Business Manager Considerations:

Pixels can be shared across business accounts
owner_business_id shows which business owns each pixel
Same pixel ID may appear in multiple account lists

Best Practices:

Document which pixels belong to which businesses
Use consistent naming conventions across accounts
Regular audits to identify shared or duplicate pixels
Set up workflows for each major account or business unit

Pro tip: Create a master spreadsheet combining pixel data from all your accounts for easier management.

Documentation Index

​When to Use It

​Inputs

​Output

​Key Fields Explained:

​Credit Cost

​FAQs