fbq('track', 'LaunchCTA')
Primary call-to-action
Simulates a mission-critical conversion button. Useful for validating revenue metadata before a high-intent launch.
On this page
Analytics Lab / Instrumentation
Observe how Meta Pixel events bind to common interface elements. Trigger any interaction to inspect the exact payload that would reach Events Manager in a production deployment.
Each component below mirrors a production instrumentation pattern. Data attributes declare the
fbq command, action source, and payload blueprint so you can map the UI directly to the
          Events Manager feed.
Buttons and forms that power acquisition programmes. These examples cover hero CTAs, meeting bookings, and lead capture flows.
fbq('track', 'LaunchCTA')
Simulates a mission-critical conversion button. Useful for validating revenue metadata before a high-intent launch.
Idle — waiting for interaction.
fbq('track', 'ScheduleConsultation')
Demonstrates a meeting-booking CTA that passes context about the requested mission review. Use it to validate custom conversion goals before launch.
Idle — waiting for interaction.
fbq('track', 'LeadSubmission')
Mimics a short lead capture flow with hashed identifiers. Submission is intercepted so you can review the outbound payload without leaving the page.
Idle — waiting for interaction.
Mid-funnel behaviors spanning resource downloads, media milestones, and newsletter sign-ups. These events power retargeting and propensity models.
fbq('track', 'ViewSpecifications')
Represents a mid-funnel content click. The payload records link context and document classification for downstream attribution.
Idle — waiting for interaction.
fbq('track', 'VideoView')
Trigger start, midpoint, and completion signals for a mission briefing. Mid-roll checkpoints use
trackCustom to avoid polluting standard reporting.
Idle — waiting for interaction.
fbq('track', 'Subscribe')
Captures lifecycle engagement by logging a newsletter opt-in. The payload includes consent and topic preferences for downstream syncing.
Idle — waiting for interaction.
Full-funnel commerce events for catalog optimisation. Fire each step to validate attribution and ensure value and currency properties map correctly.
fbq('track', 'AddToCart')
Signals that a payload containing mission hardware has been staged for purchase. Includes product category metadata for catalog segmentation.
Idle — waiting for interaction.
fbq('track', 'InitiateCheckout')
Represents a cart advancing to checkout. The payload mirrors required parameters for the Meta Conversions API including item IDs and order value.
Idle — waiting for interaction.
fbq('track', 'Purchase')
Completes the funnel with a simulated purchase event. Toggle it last to confirm deduplication logic downstream.
Idle — waiting for interaction.
Post-purchase experiences matter as much as acquisition. These interactions cover chat, case resolution, and satisfaction tracking mapped to custom pixel events.
fbq('trackCustom', 'ChatInitiated')
Simulates launching a live chat from the command console. The payload includes channel and issue taxonomy to help support teams triage inbound conversations.
Idle — waiting for interaction.
fbq('trackCustom', 'CaseResolved')
Records when a mission-critical ticket is closed. Feed this event into retention audiences to suppress resolved users from additional outreach.
Idle — waiting for interaction.
fbq('trackCustom', 'SatisfactionSurvey')
Captures a post-engagement satisfaction score and verbatim. Pair it with case metadata to unlock closed-loop reporting.
Idle — waiting for interaction.
Operational telemetry for preferences, alerts, and contextual helpers. These patterns ensure your measurement plan covers the nuance of day-to-day product usage.
fbq('trackCustom', 'ThemePreference')
Records preference changes when visitors toggle between light and dark control room themes. The payload captures previous and next state so personalisation systems can respond.
Current theme: Light
Theme set to light.
fbq('trackCustom', 'ConsentUpdate')
Demonstrates how optional communications preferences should emit explicit consent status in the payload for compliance-ready event streams.
Consent granted.
fbq('trackCustom', 'ModalOpen')
Launching the alert emits a ModalOpen payload. Buttons inside the dialog showcase
                follow-up tracking for dismiss and acknowledge events.
Modal idle — closed.
fbq('trackCustom', 'TooltipToggle')
Contextual helpers deserve instrumentation too. Toggle the tooltip to emit a payload that notes visibility state and referenced knowledge article.
The tooling primer highlights script sequencing, event validation, and QA cadences.
Tooltip hidden.
fbq('trackCustom', 'FeedbackScore')
Capture qualitative satisfaction scores directly in the pixel payload. The range input emits the selected score and upper bound for downstream dashboards.
Awaiting feedback.
Extend measurement beyond direct conversions with sharing, print, and scroll-depth signals that illuminate how mission intelligence propagates across teams.
fbq('trackCustom', 'ShareLink')
Copy-to-clipboard events indicate organic sharing. The helper mirrors instrumentation wired to a custom HTML tag with clipboard feedback.
No copy attempts recorded.
fbq('trackCustom', 'ShareSocial')
Emits a channel-specific sharing payload for social amplification. Replace the medium when integrating with other paid media platforms.
Awaiting share interaction.
fbq('trackCustom', 'SharePrint')
Printing is often overlooked in analytics implementations. This example logs the method so you can reconcile offline dissemination in downstream tools.
No print intents logged.
fbq('trackCustom', 'ScrollDepth')
The sentinel toggles when 90% depth is reached, mirroring an Intersection Observer trigger used in production to gauge deep content engagement.
Sentinel armed — scroll to trigger.
fbq('trackCustom', 'SystemAnomaly')
Mission-critical experiences should bubble anomalies to analytics stacks. Trigger the sample to simulate logging a non-fatal issue.
No anomalies detected.
Telemetry queue latency has exceeded the acceptable range. Acknowledge the alert or dismiss it to keep mission control in sync with your instrumentation.
Deploy the base pixel early in the document head. Replace META-PIXEL-ID with your pixel
        ID and add advanced matching parameters as needed.
<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', 'META-PIXEL-ID');
  fbq('track', 'PageView');
</script>