Meta Pixel Implementation

The Meta Pixel tracks conversions and helps optimize your ad campaigns. For franchise organizations, implementing pixels correctly across multiple locations is critical for accurate attribution and campaign performance.

What is the Meta Pixel?

The Meta Pixel is a piece of JavaScript code that you place on your website. When someone visits your site after clicking a Facebook or Instagram ad, the pixel fires and tells Meta what happened — did they browse, add to cart, make a purchase?

This data helps Meta:

• Optimize ad delivery to people most likely to take action
• Build audiences of people who've interacted with your site
• Measure conversions from your ad campaigns
• Enable retargeting to reach people who've shown interest

Pixel Architecture for Franchises

Franchise organizations have unique pixel considerations because each location may have:

• Separate websites or landing pages
• Different conversion goals
• Independent ad accounts
• Shared brand campaigns

Hub-Level vs Location-Level Pixels

Approach	Best For	Considerations
Single Hub Pixel	Brand campaigns, unified tracking	Harder to attribute to specific locations
Location-Specific Pixels	Per-location campaigns, local attribution	More complex to manage
Hybrid	Both brand and local campaigns	Requires careful event deduplication

Most franchise organizations benefit from a hybrid approach: one Hub pixel for brand awareness campaigns and individual pixels for each location's conversion tracking.

Setting Up Meta Pixel in Flamel

Prerequisites

Before configuring pixels in Flamel:

1. Facebook Business Manager access with admin permissions
2. Pixel created in Meta Events Manager
3. Website access to install the pixel code (or a tag manager like Google Tag Manager)

Configuring the Hub Pixel

1. Go to Organization > Permissions and enable Meta Pixel visibility
2. Navigate to Ads > Settings > Meta Pixel
3. Enter your Hub's pixel ID
4. Save the configuration

This pixel will be used for brand-level campaigns and analytics.

Configuring Location Pixels

For location-specific tracking:

1. Each workspace needs its own pixel created in Meta Events Manager
2. Workspaces configure their pixel in Ads > Settings > Meta Pixel
3. Hub can view (but not modify) workspace pixel configurations

Verifying Installation

After configuration:

1. Use the Meta Pixel Helper browser extension
2. Visit your website and verify the pixel fires
3. Check Events Manager in Meta Business Suite
4. Look for test events appearing in real-time

Standard Events vs Custom Events

Meta recognizes standard events that you should use when applicable:

Standard Events

Event	When to Use
PageView	Every page load (usually automatic)
ViewContent	Product or service page viewed
Lead	Contact form submitted
AddToCart	Item added to cart
InitiateCheckout	Checkout process started
Purchase	Transaction completed
Schedule	Appointment booked
Contact	Phone call or direct message

Custom Events

For franchise-specific actions, create custom events:

// Example: Store locator search
fbq('trackCustom', 'StoreLocatorSearch', {
  search_query: 'Chicago',
  results_count: 5
});

// Example: Franchise inquiry
fbq('trackCustom', 'FranchiseInquiry', {
  location_interest: 'Illinois',
  investment_level: '100k-250k'
});

Multi-Location Considerations

Deduplication

When running both Hub and location campaigns, the same conversion might be attributed twice. Prevent this by:

1. Using server-side events with event_id for deduplication
2. Clear campaign attribution rules in your tracking setup
3. Separate landing pages for brand vs local campaigns

Event Parameters for Location Attribution

Add location data to events to enable per-location reporting:

fbq('track', 'Lead', {
  content_name: 'Contact Form',
  location_id: 'chicago-downtown',
  franchise_code: 'CHI-001'
});

Cross-Domain Tracking

If franchisees have separate domains (e.g., chicagofranchise.com, lafranchise.com):

1. Each domain needs its pixel installed
2. Consider using Meta's Conversions API for server-side tracking
3. Use UTM parameters to track which ads drive traffic across domains

Conversions API

For more reliable tracking, implement the Conversions API alongside the pixel:

Why Use Conversions API?

• Works despite ad blockers that might prevent pixel firing
• Server-side events are more reliable than browser-based
• Better match rates when combined with customer data
• Required for some optimization strategies like iOS 14.5+ campaigns

Implementation

The Conversions API requires backend development. Work with your development team to:

1. Set up server endpoints to receive conversion data
2. Hash customer information (email, phone) before sending
3. Send events to Meta's Graph API
4. Deduplicate with browser pixel events

Troubleshooting

Pixel Not Firing

Symptom	Likely Cause	Solution
No events in Events Manager	Pixel code not installed	Verify code on page
Intermittent events	Ad blocker interference	Test in incognito mode
Events on wrong pixel	Multiple pixels, wrong one configured	Check pixel ID in settings

Events Not Matching Ads

If conversions appear in Events Manager but don't attribute to campaigns:

1. Check attribution window — Events must occur within the window (typically 7-day click, 1-day view)
2. Verify UTM parameters — Ensure ads have proper tracking
3. Review iOS opt-outs — iOS 14.5+ users may opt out of tracking

Location Attribution Issues

If you can't tell which location drove a conversion:

1. Add location parameters to all events
2. Use separate landing pages with location-specific pixels
3. Implement server-side tracking with location data

Permission Requirements

Meta Pixel configuration in Flamel requires:

• Hub admins: Can configure Hub-level pixel and view all location pixels
• Workspace admins: Can configure their location's pixel only
• Other users: View-only access based on organization permissions

Enable pixel visibility in Organization > Permissions before users can access these settings.