Get Pixel Details

The Get Pixel Details node retrieves comprehensive configuration and status information for a specific Facebook pixel, providing detailed insights into its setup and performance.

When to Use It

Get detailed configuration for a specific pixel
Troubleshoot pixel tracking issues
Verify pixel settings and permissions
Analyze pixel performance metrics
Check business ownership and access rights
Review tracking capabilities and limitations
Prepare for pixel optimization or migration
Audit pixel compliance and data usage

Inputs

Field	Type	Required	Description
Account	Select	Yes	Select the Meta Ads account containing the pixel
Pixel	Select	Yes	Select the specific pixel to get details for

Output

Returns detailed pixel configuration and status information:

{
  "id": "123456789012345",
  "name": "Website Tracking Pixel",
  "creation_time": "2023-01-15T10:30:00+0000",
  "last_fired_time": "2024-10-16T08:45:00+0000",
  "code": "<!-- Facebook Pixel Code -->...",
  "owner_business": {
    "id": "987654321",
    "name": "My Business"
  },
  "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,
  "permissions": ["EDIT", "ANALYZE"],
  "data_use_setting": "ADVERTISING_AND_ANALYTICS"
}

Key Fields Explained:

Field	Description
code	Complete pixel installation code
permissions	Your access level to this pixel
data_use_setting	How pixel data is configured for use
owner_business	Business that owns this pixel
match_rate_approx	Data matching quality (0-1)
last_fired_time	Most recent data received

Credit Cost

Cost per run: 1 credit

FAQs

What configuration details can I see for my pixel?

This node provides comprehensive pixel configuration including:Installation Information:

Complete pixel code for website installation
Pixel ID and display name
Creation date and ownership details

Performance Metrics:

Last activity timestamp
Match rate and data quality indicators
Number of matched customer entries

Settings & Permissions:

Your access level (EDIT, ANALYZE, etc.)
Data use configuration
Automatic matching status
First-party cookie setup

Business Context:

Owner business information
Sharing permissions across accounts
CRM integration status

Use this information to verify proper setup and optimize performance.

How do I use the pixel code from this output?

The code field contains the complete Facebook Pixel installation code:Installation Steps:

Copy the code from the output
Paste it in your website’s header (between <head> tags)
Add to all pages you want to track
Test with Facebook Pixel Helper browser extension

Code Structure:

<!-- Facebook Pixel Code -->
<script>
  !function(f,b,e,v,n,t,s)
  {if(f.fbq)return;n=f.fbq=function(){n.callMethod?
  n.callMethod.apply(n,arguments):n.queue.push(arguments)};
  if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';
  n.queue=[];t=b.createElement(e);t.async=!0;
  t.src=v;s=b.getElementsByTagName(e)[0];
  s.parentNode.insertBefore(t,s)}(window, document,'script',
  'https://connect.facebook.net/en_US/fbevents.js');
  fbq('init', 'YOUR_PIXEL_ID');
  fbq('track', 'PageView');
</script>
<!-- End Facebook Pixel Code -->

Important: Always use the exact code provided to ensure proper tracking.

What do the different permission levels mean?

The permissions field shows your access rights to the pixel:Permission Types:

EDIT: Full control - modify settings, view data, manage access
ANALYZE: Read access - view pixel data and analytics
ADVERTISE: Use pixel for ad targeting and optimization

Common Combinations:

[“EDIT”, “ANALYZE”, “ADVERTISE”]: Full ownership access
[“ANALYZE”, “ADVERTISE”]: Marketing team access
[“ANALYZE”]: Analytics-only access
[]: No access (shouldn’t see this if you can query the pixel)

Business Scenarios:

Agency Access: Usually ANALYZE + ADVERTISE
Business Owner: All permissions
Analytics Team: ANALYZE only
Developer: May have EDIT for implementation

Managing Access: Contact the pixel owner business to request additional permissions.

What does data_use_setting control?

The data_use_setting determines how your pixel data can be used:Setting Options:

ADVERTISING_AND_ANALYTICS: Full use for ads and measurement
ANALYTICS_ONLY: Measurement and reporting only, no ad targeting
ADVERTISING_ONLY: Ad targeting only, limited analytics

Impact on Features:ADVERTISING_AND_ANALYTICS (Recommended):

Custom audience creation
Lookalike audience building
Conversion optimization
Full attribution reporting
Advanced analytics

ANALYTICS_ONLY:

Conversion tracking and reporting
Attribution analysis
Performance measurement
No retargeting capabilities

ADVERTISING_ONLY:

Retargeting and lookalike audiences
Limited reporting capabilities
Basic conversion tracking

Choosing the Right Setting: Most businesses benefit from ADVERTISING_AND_ANALYTICS for maximum flexibility.

How can I tell if my pixel is working correctly?

Use these indicators to assess pixel health:Positive Indicators:

Recent last_fired_time: Shows active data collection
is_unavailable = false: Pixel is operational
has_1p_pixel_event = true: Receiving quality first-party data
High match_rate_approx (above 0.6): Good data quality
enable_automatic_matching = true: Optimized for best performance

Warning Signs:

Old last_fired_time: No recent activity (check installation)
Low match_rate_approx (below 0.4): Poor data quality
has_1p_pixel_event = false: Missing first-party events
is_unavailable = true: Pixel not functioning

Troubleshooting Steps:

Check pixel installation on your website
Verify event configuration matches your tracking needs
Test with Pixel Helper browser extension
Review Conversions API setup for better match rates
Check privacy settings and consent management

Pro tip: Regular monitoring helps catch issues before they impact ad performance.

What's the significance of the match rate?

The match_rate_approx indicates how well your pixel data connects with Meta’s user profiles:Match Rate Quality:

0.8-1.0 (80-100%): Excellent - Strong user matching
0.6-0.8 (60-80%): Good - Solid performance with optimization potential
0.4-0.6 (40-60%): Fair - Needs improvement
Below 0.4 (40%): Poor - Significant issues

Factors Affecting Match Rate:

Data Quality: Clean, accurate customer information
First-Party Cookies: Proper implementation improves matching
Conversions API: Server-side tracking enhances data quality
User Consent: Privacy compliance affects data collection

Improvement Strategies:

Implement CAPI: Add server-side tracking
Optimize data collection: Use high-quality first-party data
Enable automatic matching: Let Meta optimize connections
Fix technical issues: Ensure proper pixel installation

Business Impact: Higher match rates lead to better ad targeting, attribution, and ROI.

How do I handle pixels owned by other businesses?

When working with pixels owned by other businesses:Understanding Ownership:

owner_business shows who controls the pixel
You may have limited permissions
Changes require owner approval

Common Scenarios:

Agency-Client Relationship: Agency manages client’s pixel
Partnership Integrations: Shared pixels across business partners
Acquired Businesses: Legacy pixels from mergers/acquisitions

Working with Shared Pixels:

Identify your permissions from the permissions field
Contact pixel owner for additional access if needed
Request specific changes through proper channels
Use available data within your permission scope

Best Practices:

Document ownership and access arrangements
Establish clear communication channels with pixel owners
Respect permission boundaries and data usage policies
Plan for pixel migration if needed for business changes

Pro tip: Maintain good relationships with pixel owners for smooth collaboration.

When should I create a new pixel vs. using an existing one?

Use Existing Pixel When:

Tracking the same website or business
You have appropriate permissions
Data sharing is acceptable
Consistent tracking is needed across campaigns

Create New Pixel When:

Different website or domain
Separate business entity
Different data privacy requirements
Need independent control and ownership
Specific tracking requirements that conflict with existing setup

Technical Considerations:

Each website should typically have one primary pixel
Multiple pixels on the same site can cause data duplication
Cross-domain tracking requires special configuration

Business Considerations:

Data ownership and access rights
Privacy policy and compliance requirements
Reporting and attribution needs
Team access and management structure

Migration Planning:

Historical data considerations
Campaign setup and optimization impact
Training and process updates
Testing and validation requirements

Get Started

Guides

Nodes

When to Use It

Inputs

Output

Key Fields Explained:

Credit Cost

FAQs

Get Started

Guides

Nodes

​When to Use It

​Inputs

​Output

​Key Fields Explained:

​Credit Cost

​FAQs

When to Use It

Inputs

Output

Key Fields Explained:

Credit Cost

FAQs