Check CAPI Health - Markifact

The Check CAPI Health node provides comprehensive health diagnostics for your Meta Conversions API (CAPI) implementation, helping you optimize server-side tracking performance and data quality.

When to Use It

Monitor Conversions API implementation health
Diagnose data quality and matching issues
Optimize event match quality and attribution
Assess potential for improved ad performance (ACR)
Review event coverage and deduplication
Troubleshoot server-side tracking problems
Prepare CAPI optimization recommendations
Audit data freshness and upload frequency

Inputs

Field	Type	Required	Description
Account	Select	Yes	Select the Meta Ads account containing the pixel
Pixel	Select	Yes	Select the pixel/dataset to check CAPI health for
Health Metric	Select	Yes	Select the specific health metric to analyze

Health Metric Options

Metric	Description	Focus Area
event_match_quality	Overall match quality scores and feedback	Data matching optimization
emq_acr_potential	Potential ACR improvement from better matching	Performance opportunity
emq_diagnostics	Detailed diagnostics for match quality issues	Troubleshooting
event_coverage	Percentage of events with tracking coverage	Implementation completeness
coverage_acr_potential	ACR improvements from better event coverage	Coverage optimization
event_deduplication	Browser vs server event deduplication analysis	Data quality assurance
data_freshness	Event upload timing and frequency analysis	Real-time tracking performance
event_acr_potential	Overall ACR improvement potential by event	Strategic prioritization
overall_acr	Current Aggregated Conversion Rate performance	Baseline measurement

Output

Returns health metrics specific to your selected metric type:

Event Match Quality Example:

[
  {
    "event_name": "Purchase",
    "composite_score": 8.5,
    "identifier": "email",
    "coverage_percentage": 85.2,
    "potential_acr_increase_percentage": 12.3
  }
]

Event Coverage Example:

[
  {
    "event_name": "Purchase",
    "coverage_percentage": 78.5,
    "goal_percentage": 90.0,
    "description": "Good coverage but room for improvement"
  }
]

Data Freshness Example:

[
  {
    "event_name": "Purchase",
    "upload_frequency": "real_time",
    "description": "Events uploaded within minutes of occurrence"
  }
]

Credit Cost

Cost per run: 1 credit

FAQs

What is CAPI and why should I monitor its health?

Conversions API (CAPI) Explained: CAPI is Meta’s server-side tracking solution that sends conversion data directly from your server to Meta, bypassing browser limitations.Key Benefits:

Better data quality: Not affected by ad blockers or privacy settings
Improved attribution: More accurate conversion tracking
Enhanced matching: Higher-quality customer data connections
Privacy compliance: Better control over data sharing

Why Monitor Health:

Optimization opportunities: Identify areas for improvement
Technical issues: Catch implementation problems early
Performance impact: Better CAPI = better ad performance
ROI measurement: Understand attribution accuracy

Business Impact:

Higher match rates: Better ad targeting and optimization
Improved ROAS: More accurate attribution leads to better budget allocation
Future-proofing: Reduced dependence on browser tracking
Privacy readiness: Compliant with evolving privacy regulations

How do I interpret event match quality scores?

Composite Score Ranges:

9-10: Excellent - Optimal data quality and matching
7-8: Good - Strong performance with minor optimization opportunities
5-6: Fair - Moderate quality, significant improvement potential
Below 5: Poor - Major issues requiring immediate attention

Key Components:

Email matching: How well email addresses connect to Meta profiles
Phone matching: Quality of phone number matching
External IDs: Custom identifier matching performance
Data formatting: Proper hashing and format compliance

Improvement Strategies by Score:Score 9-10 (Excellent):

Maintain current practices
Monitor for any degradation
Consider expanding to additional events

Score 7-8 (Good):

Fine-tune data collection processes
Improve data quality validation
Consider additional match keys

Score 5-6 (Fair):

Review data collection implementation
Improve customer data quality
Add missing match keys

Below 5 (Poor):

Audit CAPI implementation completely
Fix data formatting issues
Implement proper data validation

What does ACR potential mean and how can I improve it?

ACR (Aggregated Conversion Rate) Explained: ACR measures how well Meta can attribute conversions to your ads. Higher ACR means better attribution and ad optimization.ACR Potential Insights:

High potential (above 20%): Significant room for improvement
Medium potential (10-20%): Good optimization opportunities
Low potential (below 10%): Already well-optimized

Common Improvement Areas:Match Quality Enhancement:

Better email collection: Improve form completion rates
Phone number validation: Ensure correct formatting
Data cleansing: Remove duplicates and invalid entries
Hashing implementation: Proper customer data formatting

Event Coverage Expansion:

Track more touchpoints: Add missing conversion events
Complete user journey: Capture all funnel stages
Mobile app events: Include app conversions
Offline conversions: Upload in-store purchases

Technical Optimization:

Real-time uploads: Reduce data lag
Deduplication setup: Prevent double counting
Server infrastructure: Improve reliability and speed
Error handling: Fix failed event uploads

Strategic Priorities: Focus on high-value events first (purchases, leads) before optimizing engagement events.

How do I improve event coverage percentages?

Understanding Coverage Goals:

Goal percentage: Meta’s recommendation for optimal performance
Current percentage: Your actual implementation coverage
Gap analysis: Difference shows improvement opportunity

Common Coverage Issues:Missing Events:

Incomplete tracking: Not all conversion points covered
Technical failures: Events not firing properly
Mobile gaps: App events not integrated
Offline missing: In-store conversions not uploaded

Implementation Solutions:Website Coverage:

Audit all conversion points: Forms, checkouts, downloads
Test event firing: Use Facebook Pixel Helper
Fix broken implementations: Address technical issues
Add missing pages: Ensure complete site coverage

Cross-Platform Coverage:

Mobile app integration: Implement Facebook SDK
Email conversions: Track newsletter signups and clicks
Phone conversions: Upload call tracking data
In-store events: Upload offline conversion data

Technical Improvements:

Event validation: Ensure events fire consistently
Error monitoring: Track and fix failed events
Load time optimization: Prevent events being dropped
Backup tracking: Implement redundant event capture

Prioritization Strategy:

High-value events first: Purchases, qualified leads
High-volume events: Page views, content engagement
Attribution events: Mid-funnel interactions
Optimization events: Custom conversions

What should I know about event deduplication?

Deduplication Explained: Prevents the same conversion from being counted multiple times when sent via both browser pixel and CAPI.Key Metrics:

Browser events with dedupe key: Percentage of web events with deduplication IDs
Server events with dedupe key: Percentage of CAPI events with deduplication IDs
Overall coverage: How well deduplication is implemented

Why Deduplication Matters:

Accurate attribution: Prevents inflated conversion numbers
Budget optimization: Avoids over-attribution to ads
Reporting accuracy: Cleaner data for analysis
Platform trust: Better data quality improves Meta’s optimization

Implementation Best Practices:Dedupe Key Requirements:

Unique identifiers: Order IDs, transaction IDs, lead IDs
Consistent across sources: Same ID for browser and server events
Proper timing: Events sent within deduplication window
Formatted correctly: Follow Meta’s formatting guidelines

Common Patterns:

E-commerce: Use order/transaction IDs
Lead generation: Use form submission IDs
App installs: Use app event IDs
Content engagement: Use session or interaction IDs

Troubleshooting:

Low coverage: Add dedupe keys to more events
Mismatched IDs: Ensure consistency between sources
Timing issues: Send events within deduplication window
Format errors: Check ID formatting and character limits

How does data freshness impact CAPI performance?

Data Freshness Importance: Fresher data leads to better attribution, optimization, and user experience.Upload Frequency Categories:

Real-time: Within minutes (optimal)
Near real-time: Within hours (good)
Batch: Daily uploads (acceptable for some events)
Delayed: Multiple days (problematic)

Performance Impact by Timing:Real-time (Best):

Attribution accuracy: Events connected to recent ad interactions
Optimization speed: Faster campaign optimization
User experience: Better retargeting and personalization
Competitive advantage: React quickly to user behavior

Near real-time (Good):

Acceptable performance: Minor impact on optimization
Simplified infrastructure: Easier to implement
Cost-effective: Lower server resource requirements

Batch/Delayed (Suboptimal):

Attribution loss: Connections to ads may be missed
Slower optimization: Campaigns take longer to improve
Missed opportunities: Real-time targeting not possible

Improvement Strategies:Technical Solutions:

Real-time APIs: Implement immediate event sending
Queue systems: Buffer events for reliable delivery
Error handling: Retry failed uploads quickly
Infrastructure scaling: Handle traffic spikes

Business Considerations:

Event prioritization: Send high-value events immediately
Resource allocation: Balance speed vs cost
Monitoring systems: Track upload timing and failures
SLA definition: Set acceptable timing thresholds

Which health metric should I check first for optimization?

Recommended Checking Order:1. Overall ACR (Baseline):

Purpose: Understand current performance level
Action: Establish baseline for improvement measurement
Frequency: Monthly monitoring

2. Event Match Quality (Foundation):

Purpose: Assess data quality fundamentals
Action: Fix basic match quality issues first
Frequency: Weekly monitoring during optimization

3. Event Coverage (Completeness):

Purpose: Ensure comprehensive tracking implementation
Action: Add missing events and fix coverage gaps
Frequency: Bi-weekly reviews

4. EMQ/Coverage ACR Potential (Opportunity):

Purpose: Quantify improvement opportunities
Action: Prioritize high-impact optimization areas
Frequency: Monthly strategic reviews

5. Event Deduplication (Accuracy):

Purpose: Ensure data accuracy and prevent double-counting
Action: Implement proper deduplication
Frequency: Quarterly audits

6. Data Freshness (Speed):

Purpose: Optimize real-time performance
Action: Improve upload timing and infrastructure
Frequency: Continuous monitoring

Quick Wins Priority:

Fix obvious implementation errors (broken events)
Add missing high-value events (purchases, leads)
Improve data quality (proper formatting, validation)
Implement deduplication (prevent double-counting)
Optimize upload timing (faster data delivery)

Pro tip: Start with event_match_quality and event_coverage for the biggest impact.

How often should I check CAPI health metrics?

Monitoring Schedule by Metric:Daily Monitoring:

Data freshness: Ensure events are uploading properly
Overall ACR: Track sudden changes or issues

Weekly Reviews:

Event match quality: Monitor data quality trends
Event coverage: Check for implementation issues
EMQ diagnostics: Address specific problems

Monthly Analysis:

ACR potential metrics: Strategic optimization planning
Event deduplication: Comprehensive accuracy review
Overall performance: Compare against goals and benchmarks

Quarterly Audits:

Complete health assessment: All metrics review
Strategy adjustment: Update optimization priorities
Infrastructure review: Assess technical improvements

Triggered Checks:

After website changes: Verify continued functionality
Campaign performance issues: Diagnose attribution problems
New feature releases: Validate implementation
Privacy regulation updates: Ensure continued compliance

Automation Recommendations:

Set up alerts: Notify team of significant changes
Regular reports: Automate weekly/monthly summaries
Dashboard integration: Include key metrics in existing dashboards
Threshold monitoring: Alert when metrics fall below acceptable levels

Resource Planning:

Initial setup: Daily monitoring for first month
Optimization phase: Weekly deep dives until stable
Maintenance phase: Monthly reviews with triggered checks
Continuous improvement: Quarterly strategic assessments

Documentation Index

​When to Use It

​Inputs

​Health Metric Options

​Output

​Event Match Quality Example:

​Event Coverage Example:

​Data Freshness Example:

​Credit Cost

​FAQs