Webnode Meta Pixel Event Tracking

Pixel base code must be installed first. See Webnode Meta Pixel Setup.

Webnode Implementation

Webnode allows custom code injection on Premium and Business plans only (Header/Footer Code in Settings). Free plans cannot use Meta Pixel. For Webnode ecommerce, track product views and purchases by adding event scripts to relevant page templates where Webnode's code injection allows.

Standard Events

Meta Pixel standard events are predefined actions that Meta's ad system recognizes for optimization. When you fire standard events with proper parameters, Meta can optimize ad delivery for those specific actions (e.g., optimizing for purchases, not just page views).

Event Priority Guide

Ecommerce Events

Track the full purchase funnel:

// Product viewed
fbq('track', 'ViewContent', {
  content_ids: ['SKU-123'],
  content_name: 'Product Name',
  content_type: 'product',
  content_category: 'Category',
  value: 29.99,
  currency: 'USD'
});

// Added to cart
fbq('track', 'AddToCart', {
  content_ids: ['SKU-123'],
  content_name: 'Product Name',
  content_type: 'product',
  value: 29.99,
  currency: 'USD'
});

// Checkout started
fbq('track', 'InitiateCheckout', {
  content_ids: ['SKU-123', 'SKU-456'],
  content_type: 'product',
  num_items: 2,
  value: 59.98,
  currency: 'USD'
});

// Purchase completed
fbq('track', 'Purchase', {
  content_ids: ['SKU-123', 'SKU-456'],
  content_type: 'product',
  num_items: 2,
  value: 59.98,
  currency: 'USD'
});

Parameter requirements for ad optimization:

• content_ids and content_type are required for Dynamic Product Ads (DPA/Advantage+ catalog).
• value and currency are required for value-based optimization and ROAS bidding.
• content_name and content_category improve Advantage+ audience targeting.

Custom Events

For actions not covered by standard events:

// Custom event — not used for standard ad optimization
// but available in Custom Conversions and custom audiences
fbq('trackCustom', 'ShareContent', {
  content_name: 'Article Title',
  method: 'email'
});

fbq('trackCustom', 'VideoWatch', {
  video_title: 'Demo Video',
  percent_watched: 75
});

Standard vs custom events: Always prefer standard events when they match your action — Lead instead of a custom FormSubmit, Purchase instead of a custom OrderComplete. Standard events unlock Meta's ad optimization algorithms. Custom events work for audiences and custom conversions but don't support value-based optimization.

Debugging Events

Meta Pixel Helper

Install the Meta Pixel Helper Chrome extension. Visit your site and click the extension icon — it shows every pixel fire with event name, parameters, and any errors. Green checkmark = working. Yellow/red = issues.

Events Manager Test Events

In Meta Events Manager → Test Events → enter your site URL → interact with your site. Events appear in real-time with full parameter details. This verifies events reach Meta's servers (Pixel Helper only verifies client-side firing).

Console Debugging

// Check if pixel is loaded
console.log('fbq loaded:', typeof fbq === 'function');

// Monitor all pixel fires
if (typeof fbq === 'function') {
  const origFbq = fbq;
  fbq = function() {
    console.log('Pixel event:', Array.from(arguments));
    return origFbq.apply(this, arguments);
  };
}

Custom Conversions

If you can't modify site code to fire standard events, create Custom Conversions in Events Manager that trigger on URL rules:

1. Events Manager → Custom Conversions → Create
2. Set rules: URL contains /thank-you or /order-confirmation
3. Assign a conversion category (Purchase, Lead, etc.)
4. Meta will count PageView events on matching URLs as conversions

This is a workaround — standard events with parameters are always more accurate for optimization.

Next Steps

• Meta Pixel Setup — base pixel installation
• GTM Setup — manage pixel via Google Tag Manager
• Events Not Firing — troubleshoot pixel issues