Meta Ads Meta Pixel and Conversions API Interview Questions
Meta Pixel interview questions: 119 questions with model answers on events, custom conversions, the Conversions API, deduplication and event match quality, from Basic to Advanced.
- Model answers
- Basic to Advanced
- Search and filter
Pixel, events, custom conversions, CAPI, deduplication and event match quality. Questions are grouped from Basic to Advanced, each with a model answer. Use the filters or search to find what you need, then take the free Meta Ads test to check your score. For official definitions and policies, see the Meta Business Help Center.
What these Meta Pixel interview questions cover
These Meta Pixel interview questions focus on tracking and measurement. They cover standard and custom events, custom conversions, the Conversions API, event deduplication, event match quality and aggregated event measurement. Each question comes with a model answer written by a working Meta ads specialist, so you can compare your own answer and see the points an interviewer or client expects to hear.
Interviewers use questions like these to check whether you can build reliable tracking, because every optimisation decision depends on clean data. Start with the Basic questions, then move to Intermediate and Advanced. Click any question to open its answer, use the level filters to focus, or search for a keyword. When you are ready, take the free Meta Ads test to score yourself and find your weak topics.
All questions, from Basic to Advanced
Basic questions
What is an "event" in Meta tracking?
- An action a person takes on your website/app that is sent to Meta: e.g. PageView, ViewContent, AddToCart, InitiateCheckout, AddPaymentInfo, Purchase, Lead, CompleteRegistration, Contact, Schedule, Search, Subscribe.
- Events are used for reporting, optimization and audience building.
What are standard events?
- Predefined event names recognized by Meta (Purchase, Lead, AddToCart, etc.).
- They can be used directly for optimization and reporting with full support.
- Parameters (value, currency, content_ids, content_type) add details.
What is a custom event?
- An event with a name you define (e.g. "WhatsAppClick", "BrochureDownload", "QualifiedLead") when no standard event fits.
- Sent via fbq('trackCustom', 'EventName', {params}) or via CAPI.
- To optimize toward it, you usually create a custom conversion from it.
What is a custom conversion and how is it different from a custom event?
- Custom conversion = a rule in Events Manager that defines a conversion based on URL rules (e.g. URL contains /thank-you) or event + parameter rules (e.g. Purchase where value > 500).
- No extra code needed for URL-based ones.
- Custom event = new event fired by code; custom conversion = a filter/rule on existing events/URLs.
- Ad account limit of custom conversions (100); they can be used for optimization and reporting.
Give an example of when to use a custom conversion.
- Track leads only from a specific landing page: rule "Lead event where URL contains /off-plan-dubai".
- Track only high-value purchases: Purchase where value > AED 1,000.
- Track a "thank-you page" when you can't add event code: URL contains /thank-you.
What are event parameters and why do they matter?
- Extra info sent with events: value, currency, content_ids, content_name, content_type, num_items, predicted_ltv, etc.
- Needed for ROAS reporting, value optimization, catalog/dynamic ads (content_ids must match catalog IDs).
What is the Meta pixel "funnel" for e-commerce?
- PageView → ViewContent (product page) → AddToCart → InitiateCheckout → AddPaymentInfo → Purchase.
- Each step shows where people drop off; ratio between steps identifies problems (e.g. high ATC but low IC = shipping/price shock at cart).
What is the funnel for a lead-gen website?
- PageView → ViewContent (service page) → Contact/Lead (form submit, WhatsApp click) → CompleteRegistration/Schedule → (offline) QualifiedLead → Converted/Customer via CAPI.
What is the Conversions API (CAPI) and why is it needed after iOS 14.5?
- Server-side events sent directly from your server/CRM/platform to Meta.
- iOS 14.5 ATT, browser tracking prevention (Safari ITP), ad blockers and cookie restrictions reduce pixel accuracy.
- CAPI recovers lost events, improves attribution and optimization, and can send offline/CRM events.
What are the ways to set up CAPI?
- Partner integrations: Shopify, WooCommerce, WordPress, Wix, Squarespace, HubSpot, etc. (often one click).
- Conversions API Gateway (Meta-hosted in your cloud), or Signals Gateway.
- Server-side Google Tag Manager (sGTM) with Meta CAPI tag.
- Direct integration by developers using the Marketing API.
- CRM integrations for lead/offline events (e.g. Conversion Leads integration, Zapier/Make).
How do you track WhatsApp button clicks on a website?
- Add a click-triggered event (e.g. standard "Contact" or custom "WhatsAppClick") via code or GTM on the WhatsApp link/button.
- Create a custom conversion if needed and optimize for it.
- Better: track the actual conversation and sales in CRM and send back via CAPI.
What is the Meta Pixel Helper?
- A Chrome extension that shows which pixel events fire on a page, their parameters and errors.
- Quick way to debug browser-side tracking.
What is a product catalog and how is it connected to the pixel?
- A file/feed in Commerce Manager containing products (ID, title, description, price, image, link, availability).
- Connected to the pixel/dataset so events can be matched to products for Advantage+ catalog ads and Shops.
- Updated via data feed, partner platform, or manually.
What does "Lead" standard event mean and when should it fire?
- When someone submits a form/inquiry and becomes a lead.
- Fire it on successful submission (thank-you page or success callback), not on button click alone (prevents false leads).
What is "Contact" event vs "Lead" event?
- Contact: person contacted the business (call, WhatsApp, email click, chat).
- Lead: person submitted information expecting follow-up.
- Use both to understand the funnel; optimize for the one closer to sales with enough volume.
How do you track video viewers for retargeting without a pixel?
- Create a video engagement custom audience (3-sec, ThruPlay, 25/50/75/95% viewers).
- No pixel needed; works from ad and organic video views.
What is "Automatic Advanced Matching"?
- Pixel setting that automatically captures hashed customer info (email, phone) from website forms to improve match rate.
- Turn it on in Events Manager pixel settings.
Intermediate questions
How do you calculate funnel conversion rates and what do they tell you?
- LPV→ViewContent, VC→ATC rate (typical e-com 5–15%), ATC→IC (30–60%), IC→Purchase (40–70%), overall site CVR (1–3% e-com).
- Low LPV/click: page speed/tracking issue. Low ATC: product/price/offer/page issue. Low IC→Purchase: checkout friction, payment, shipping costs.
- Benchmarks vary by industry – compare with your own history.
What is event deduplication and how does it work?
- When the same event is sent by both Pixel and CAPI, Meta must count it once.
- Send the same event_name and a matching event_id (pixel: eventID; CAPI: event_id) for both.
- Meta keeps the first received and discards duplicates within 48 hours.
- Check Events Manager → deduplication status / overview.
What happens if deduplication is not set up properly?
- Conversions double-count → inflated results and ROAS in Ads Manager.
- Algorithm optimizes on wrong data; reporting becomes untrustworthy.
- Fix: add matching event_id; or fbp/external_id as secondary keys.
What is Event Match Quality (EMQ)?
- A score (0–10) showing how well the customer information sent with server events can be matched to Meta accounts.
- Higher EMQ = better attribution and optimization.
- Improve by sending hashed email, phone, first/last name, city, country, external_id, client IP, user agent, fbp and fbc (click ID).
- Aim for 6+ (good) and 8+ (great) for key events like Purchase/Lead.
What are fbp and fbc parameters?
- fbp = the _fbp browser cookie identifying the browser (first-party cookie set by pixel).
- fbc = the _fbc cookie storing the fbclid click ID from Meta ad clicks.
- Sending them with CAPI events improves matching and attribution to the ad click.
What is Aggregated Event Measurement (AEM)?
- Meta's protocol to measure web and app events from iOS 14.5+ users in a privacy-safe way.
- Originally required verifying the domain and prioritizing up to 8 events per domain; Meta later removed the manual 8-event configuration and now handles event prioritization automatically.
- Data from opted-out iOS users is aggregated/modeled and reported with delays.
How do you test whether Pixel and CAPI events are firing correctly?
- Meta Pixel Helper (Chrome extension) for browser events.
- Events Manager → Test Events tool with a test code for server events.
- Check Diagnostics tab for errors (missing parameters, duplicate events, invalid values).
- Complete a real test lead/purchase and verify it appears with correct value/currency.
What is offline conversion tracking and how is it done now?
- Sending conversions that happen outside the website (in-store sales, phone sales, signed contracts) to Meta.
- Done via CAPI to the same dataset (Offline Conversions API was merged into CAPI) or CSV uploads.
- Lets you measure real revenue from ads and optimize toward it.
What are the limitations of pixel-only tracking?
- Ad blockers, browser privacy features and cookie expiry block events.
- iOS opted-out users are not trackable in the same way.
- Page load failures prevent the pixel from firing.
- Result: under-reported conversions (often 10–30%+), weaker optimization.
What is the difference between "view-through" and "click-through" conversions?
- Click-through: user clicked the ad and converted within the click window (e.g. 7 days).
- View-through: user saw the ad (didn't click) and converted within the view window (1 day).
- View-through can be valuable for awareness/video but can over-credit retargeting; compare with click-only views.
What is "1-day engaged-view" attribution?
- Counts conversions within 1 day after someone watched a video ad for at least ~10 seconds (or 97% of shorter video) without clicking.
- Introduced to credit video ads better (especially Reels); reported separately from view-through.
What does "Compare attribution settings" in Ads Manager do?
- Adds columns showing results under different windows (1-day click, 7-day click, 1-day view, engaged view).
- Helps understand how much reported result depends on view-through and long windows.
How do Google Tag Manager and Meta Pixel work together?
- Install the base pixel via GTM (custom HTML or community template) and fire events on triggers (clicks, form submits, page views of thank-you pages, data layer events).
- Server-side GTM can also send CAPI events.
- Be careful not to double-install the pixel (hardcoded + GTM).
What is "content_ids" and why does it matter for catalog ads?
- The product ID(s) sent with ViewContent, AddToCart and Purchase events.
- Must match the IDs in the Meta catalog so dynamic ads can show the right products.
- Mismatch = low catalog match rate and poor retargeting.
What are "Diagnostics" in Events Manager and give examples of issues?
- Alerts about tracking problems: duplicate events, missing value/currency, event_id missing for dedupe, low EMQ, server events delayed, domain mismatch, invalid parameters.
- Fix them regularly; they directly impact optimization.
What is the impact of server event delay?
- Meta expects events in near real time; late events (hours/days) reduce attribution accuracy and optimization signals.
- Send events as soon as they happen; batch uploads only for offline data within allowed timeframes (up to 7 days for web events, longer for offline).
What is "external_id" in CAPI?
- Your own unique user ID (e.g. CRM ID), hashed recommended; used consistently across pixel and CAPI to improve matching and dedupe.
What is the "lead_id" and how is it used?
- Unique ID for each instant form lead.
- When sending CRM stage updates back to Meta (Conversion leads), include the lead_id so Meta can link the outcome to the original lead.
What is "Conversion API for business messaging"?
- A way to send events that happen in WhatsApp/Messenger chats (e.g. lead qualified, order placed) back to Meta for measurement and optimization of click-to-message ads.
- Lets you optimize CTWA campaigns toward purchases/leads instead of only conversations.
Why might Events Manager show "No recent activity"?
- Pixel removed from site/theme update, wrong pixel ID, consent banner blocking pixel, site not getting traffic, CAPI token expired.
- Check Pixel Helper, test events, CMS integration settings.
What is the role of "value" in a Lead event?
- You can assign an estimated value to leads (e.g. average deal value × close rate) for value-based reporting and optimization.
- Better: send actual value later via CAPI when the deal closes.
What is "Data Sources" mismatch and what is the "Traffic permissions" setting?
- Traffic permissions (allowlist/blocklist) let you control which domains can send events to your pixel, preventing others from polluting your data.
- Add only your domains to the allow list.
What is the "Events Manager overview" breakdown by Browser vs Server and what does it tell you?
- Shows how many events came from pixel (browser) vs CAPI (server) and how many were deduplicated.
- A healthy setup shows both sources with good overlap/deduplication; a big gap shows tracking loss on one side.
What is the difference between "Purchase" and "Purchases conversion value" columns?
- Purchases = number of purchase events attributed.
- Purchase conversion value = total revenue attributed (used for ROAS).
- Check both: a high ROAS can come from a few large orders.
What is a "Lift study"?
- A randomized controlled experiment: a test group sees ads, a holdout group doesn't; the difference measures incremental conversions/brand lift.
- Gold standard for measuring true impact; requires enough budget and volume.
What happens to tracking for in-app browser purchases on Instagram/Facebook?
- Clicks open in Meta's in-app browser; pixel tracks there; if user later buys in Safari/Chrome, cross-browser journeys can be missed by pixel.
- CAPI with email/phone matching helps connect these.
Why should you track micro-conversions (scroll depth, time on page, video view on landing page)?
- They show engagement quality when final conversions are few.
- Useful for diagnosing landing pages and building warm audiences (e.g. people who spent 60+ seconds).
- Don't optimize campaigns on them unless needed; they are proxies.
Advanced questions
A real estate company gets 300 leads/month but sales says 90% are junk. How would you use tracking to fix quality?
- Set up CRM stages (New, Contacted, Qualified, Site visit, Booked) and send them back to Meta via CAPI (Conversion Leads integration).
- Switch optimization to Conversion leads (or a custom conversion on "Qualified") when volume allows.
- Use Higher-intent instant form, qualifying questions (budget, timeline, nationality/residency), and phone verification.
- Build lookalikes/suggestions from qualified leads; exclude junk sources.
Your Purchase event shows in Events Manager but ROAS is zero in Ads Manager. What is wrong?
- Purchase event is missing "value" or "currency" parameter, or value is sent as text/0.
- Wrong currency code or value in different format (e.g. "1,250.00 AED").
- Fix the parameters in pixel/CAPI and test with Test Events.
Events Manager shows "Purchase" events doubled compared to Shopify orders. Diagnose.
- Deduplication missing (pixel + CAPI without matching event_id).
- Pixel installed twice (theme code + app), or thank-you page refreshes firing again.
- Third-party apps sending extra events.
- Fix: remove duplicate installations, use event_id dedupe, fire purchase only once per order ID.
What tracking would you set up for a hotel booking website?
- Standard events: Search (date/destination), ViewContent (room page), InitiateCheckout, AddPaymentInfo, Purchase with value/currency/check-in dates.
- Travel-specific parameters (checkin_date, checkout_date, num_adults, content_ids for hotels) for dynamic ads for travel.
- CAPI via booking engine, cross-domain tracking if booking engine is on another domain.
The booking engine is on a third-party domain where you can't install the pixel. What do you do?
- Ask the booking engine for Meta pixel/CAPI integration (many support it).
- Track the click to the booking engine as a custom event ("InitiateBooking") on your site.
- Send confirmed bookings back via CAPI/offline upload from the PMS/CRM.
- Use UTMs to attribute in analytics.
How would you track a lead that becomes a customer 30 days later?
- Store fbc/fbp, click ID, email/phone at lead submission in the CRM.
- When the deal closes, send a CAPI event (e.g. Purchase or custom "Converted") with the same identifiers, value and event time.
- Meta attributes to the original ad interaction (for conversion leads integration, lead_id from instant forms is used).
How do you set up tracking for a business setup consultancy that gets leads by calls, WhatsApp and website forms?
- Website: Lead event on form submit, Contact on WhatsApp/call clicks; CAPI with hashed contact details.
- Meta calls ads: track call duration via call ads reporting; WhatsApp: CTWA conversions and CAPI for business messaging events (LeadSubmitted, Purchase).
- CRM: single source of truth; send Qualified/Converted stages back to Meta; UTMs for source tracking.
How does a cookie consent banner (GDPR-like) affect Meta tracking and what can you do?
- If users decline, pixel shouldn't fire marketing cookies → fewer tracked events.
- Implement consent mode correctly, send CAPI events only where legally allowed, rely on modeled conversions.
- Measure with blended metrics; in UAE PDPL applies – follow legal advice.
What is "predicted LTV" and how could it help?
- Sending predicted lifetime value as the value of a purchase/subscription event so the algorithm optimizes for valuable customers rather than first order value.
- Useful for subscriptions, apps, high repeat-purchase businesses.
After a website migration, conversions dropped 60% overnight in Ads Manager but sales are normal. What happened?
- Pixel/CAPI not installed on the new site or events misnamed, purchase event not firing on new thank-you URL, custom conversion URL rules no longer match.
- Check Events Manager activity, Pixel Helper, Test Events; fix URL rules; until fixed, algorithm loses signal so performance will genuinely degrade.
How do you prove to a client that Meta ads drive incremental sales, not just taking credit?
- Run a Conversion Lift study (Meta's randomized holdout test) or geo-holdout test.
- Compare blended metrics (MER, new customers) when spend changes.
- Use MMM (marketing mix modeling, e.g. Meta Robyn) for bigger budgets.
What is Meta's "incremental attribution" setting?
- A newer attribution option (rolled out 2025) that optimizes and reports only conversions Meta estimates were incremental (would not have happened without the ad), based on lift-style modeling.
- Results may look lower but closer to true business impact; useful for mature advertisers.
Write the basic Meta Pixel code flow for a Purchase event and explain each part.
- Base code loads fbevents.js and calls fbq('init', 'PIXEL_ID') then fbq('track', 'PageView') on every page.
- Purchase on the order confirmation page: fbq('track', 'Purchase', {value: 450.00, currency: 'AED', content_ids: ['SKU123'], content_type: 'product'}, {eventID: 'order_10045'}).
- value must be a number, currency a 3-letter ISO code; content_ids must match catalog IDs.
- The 4th argument {eventID} is used to deduplicate against the same event sent through CAPI.
- A <noscript> image tag is a fallback for browsers without JavaScript.
Expert insight: Fire Purchase only once per order – guard with a flag keyed on order_id so a refresh of the thank-you page doesn't re-fire. Pass value as a number (450.00), never a string with currency symbols. Follow-up: "Where does eventID come from?" → the order ID from the data layer, so CAPI can use the same value.
What is the Conversions API endpoint and what are the required fields of a server event?
- POST to https://graph.facebook.com/{API_VERSION}/{PIXEL_or_DATASET_ID}/events with an access token.
- Body has a "data" array of events (up to 1,000 events per request).
- Required: event_name, event_time (Unix timestamp in seconds), action_source, user_data (at least one matching key); for website events also event_source_url and client_user_agent.
- Recommended: event_id (dedupe), custom_data (value, currency, content_ids, order_id).
Expert insight: Meta returns {"events_received": N, "fbtrace_id": ...}; a 200 response doesn't mean data is good – still check Diagnostics and EMQ. Batch server events but send them within minutes; keep the Graph API version current because old versions are deprecated on a schedule.
What are the valid values for action_source in CAPI and why does it matter?
- website, app, email, phone_call, chat, physical_store, system_generated, business_messaging, other.
- Tells Meta where the conversion happened; it affects validation rules (e.g. website events need event_source_url and user agent) and how the event is used in attribution.
- Using the wrong value (e.g. "website" for a CRM-closed deal) can cause events to be rejected or misattributed.
Expert insight: For a website lead later converted offline, send the follow-up stage with action_source = system_generated (CRM) or phone_call, not website – website events require event_source_url and client_user_agent and will fail validation otherwise.
Which user_data fields must be hashed and which must NOT be hashed?
- Hash with SHA-256 after normalizing: em (email), ph (phone), fn, ln, db (date of birth), ge (gender), ct (city), st (state), zp (zip), country, external_id (recommended).
- Do NOT hash: client_ip_address, client_user_agent, fbc, fbp, lead_id, subscription_id, fb_login_id.
- Hashing un-hashable fields (e.g. fbc) makes them useless for matching.
Expert insight: Most server SDKs hash automatically when you use their setters (e.g. setEmail) – double-hashing (hashing an already-hashed value) silently destroys matching. Follow-up: "Is hashing encryption?" → No, SHA-256 is one-way; Meta matches hashes to its own hashed data.
How should you normalize data before hashing for CAPI?
- Email: trim spaces, lowercase.
- Phone: digits only including country code, no "+", no leading zeros after the country code (e.g. 971501234567).
- Names: lowercase, remove punctuation; city lowercase without spaces; state/zip lowercase without spaces.
- Country: 2-letter ISO code, lowercase (ae, in, sa); date of birth YYYYMMDD; gender f or m.
- Wrong normalization = hash mismatch = low Event Match Quality.
Expert insight: Common UAE mistake – phones stored as 050xxxxxxx; you must convert to 97150xxxxxxx before hashing. Test by hashing a known sample and comparing with Meta's Payload Helper output.
What is the format of the fbc and fbp values and how do you capture fbc server-side?
- fbp: fb.1.{creationTime in ms}.{random number} – set by the pixel in the _fbp cookie.
- fbc: fb.1.{creationTime in ms}.{fbclid} – from the _fbc cookie, or built from the fbclid URL parameter on landing.
- Server-side: read the cookies from the request, or capture fbclid from the landing URL, store it in session/CRM and include it in later events (even days later for leads).
Expert insight: When fbclid exists but no _fbc cookie (e.g. ITP or the pixel blocked), build fbc yourself: fb.1.<current ms timestamp>.<fbclid>. Don't modify fbclid's case – it is case-sensitive.
What is the time limit for sending events through CAPI?
- Website/app events: event_time can be up to 7 days in the past; events older are rejected.
- Physical store/offline events can be sent up to 62 days after the conversion.
- Best practice: send website events in real time (within minutes) for optimization.
Expert insight: If your CRM batches nightly, web-sourced leads are still fine (within 7 days) but optimization signals arrive late; real-time CAPI for the main event + nightly batch for deeper stages is the common hybrid.
How does deduplication work when event_id is not available?
- Meta can also deduplicate using fbp and/or external_id together with event_name, if both browser and server events carry the same values.
- This is less reliable; event_id + event_name is the recommended method.
- Deduplication only works within a 48-hour window and only between browser and server events (not server vs server).
Expert insight: Without event_id, Meta can fall back to external_id or fbp matching, but this only works when both sources carry identical values – most production setups break here. Always generate event_id client-side and forward it.
You send Purchase from both the pixel and CAPI, but the event_id is the order ID on the server and a random number on the browser. What happens and how do you fix it?
- They won't deduplicate → double counting of purchases and inflated ROAS.
- Use the same identifier on both sides, e.g. the order ID passed to the data layer and used as eventID in fbq and event_id in CAPI.
Expert insight: To verify, open Events Manager → event → "Deduplication" panel; a healthy Purchase shows most events received from both browser and server and "deduplicated". Follow-up: "What if the server sends first?" → Meta keeps the first one received and drops the duplicate either way.
What is the "test_event_code" and how is it used?
- A code from Events Manager → Test Events added to the CAPI payload so events appear in the test tool in real time.
- Used to validate payloads before going live; remove it in production (test events are not used for optimization/reporting).
What is the Conversions API Gateway and how is it different from a direct integration?
- A Meta-provided, self-hosted (in your AWS/GCP etc.) server that automatically mirrors pixel events to server events with no coding.
- Quick to set up and handles deduplication, but it only captures what the pixel sees (cannot add CRM/offline data).
- Direct/server integrations can send any event (CRM stages, refunds, offline sales) and richer customer data.
Expert insight: Gateway is a good quick win for SMEs without developers, but agencies usually move to direct/sGTM once they need CRM stages, refunds or offline revenue. Signals Gateway extends the idea to multiple destinations.
What is server-side Google Tag Manager (sGTM) and how is it used with Meta CAPI?
- A GTM container running on your own server (e.g. Google Cloud Run / Stape) that receives events from the website and forwards them to vendors.
- A Meta CAPI tag in sGTM sends events with user data, fbc/fbp, event_id.
- Benefits: first-party domain, more control over data, fewer client scripts; requires hosting cost and setup.
Expert insight: sGTM can set first-party cookies from your own subdomain (e.g. data.yoursite.com), extending cookie life vs ITP limits on JS-set cookies; costs are hosting (Cloud Run/Stape) and setup time.
How do you pass the same event_id from the website to both Pixel and sGTM CAPI?
- Generate a unique ID in the web container (variable/template), push it with the event in the data layer.
- Use it as eventID in the Meta pixel tag and send it to the server container in the GA4/HTTP request, where the CAPI tag uses it as event_id.
What is the data layer and why is it important for tracking?
- A JavaScript object (window.dataLayer) where the website pushes structured information (event name, order ID, value, items, user info).
- Tags read from it reliably instead of scraping the page; essential for accurate value, content_ids and dedupe IDs.
What custom_data parameters are important for e-commerce events?
- value, currency, content_ids, contents (id, quantity, item_price), content_type (product or product_group), content_name, content_category, num_items, order_id.
- order_id helps avoid duplicate purchases; contents with quantity and price improves catalog matching and value accuracy.
Expert insight: Sending contents=[{id, quantity, item_price}] lets Meta compute value per product and improves catalog matching vs content_ids alone. Always include order_id to protect against duplicate purchases from the same order.
What is the difference between content_type "product" and "product_group"?
- product: content_ids refer to individual variant IDs (e.g. a size/color SKU).
- product_group: content_ids refer to item_group_id (the parent product).
- Must match how IDs are defined in the catalog or dynamic ads won't match.
What are the main Events Manager diagnostics errors you should know?
- Missing/duplicate event_id, server events without user agent, invalid currency or value, events sent with future/old timestamps, low match keys, mismatched IP address formats, unverified domain, pixel firing on unauthorized domains, ad-blocked traffic share.
Expert insight: Prioritize diagnostics by business impact: Purchase/Lead value errors and dedupe issues first, then match-key coverage, then minor parameter warnings.
How do you send a refund or cancelled order back to Meta?
- There is no standard "Refund" event; teams send a custom event (e.g. "Refund") for reporting, or adjust value in internal reporting.
- Important: don't send negative purchase values; measure net ROAS in your backend and in MER.
How would you track a single-page application (React/Next.js) correctly?
- Fire PageView on route changes (history changes), not only on first load.
- Fire events on state changes (add to cart, form submit success) from the app code or data layer.
- Avoid duplicates from React re-renders (strict mode double effects) by guarding the event fire.
Expert insight: In Next.js, listen to router events (routeChangeComplete / App Router usePathname effect) for PageView; guard against React StrictMode double effects in development.
How do you track a form submission correctly to avoid false leads?
- Fire on the success callback (after server validates) or on a thank-you page/URL – not on button click.
- Include event_id and send the same lead via CAPI with hashed email/phone from the form.
- Exclude test submissions and spam (honeypot, CAPTCHA).
Expert insight: For AJAX forms, fire the event in the success callback after the server returns 200 – also send the lead to CAPI from the server using the same event_id generated in the browser.
What is cross-domain tracking and when is it needed?
- When the user journey moves across domains (site.com → booking-engine.com → checkout.shopify.com).
- Pixel is first-party per domain; the _fbp cookie differs on each domain, so journeys break.
- Solutions: install the same pixel on all domains, pass fbclid/fbc along via URL, and use CAPI with customer data (email/phone) to stitch the conversion.
Expert insight: Booking/checkout engines on other domains often drop UTMs and fbclid; ask the vendor to persist query parameters, or append them on the outbound link with a small script.
What is "Automatic events" / "automatic setup" in pixel settings and what are the risks?
- Meta can auto-detect button clicks and page metadata (and suggest events) without code.
- Risk: inaccurate or duplicate events; many experts disable automatic events for important conversions and use explicit code.
What is a Meta "dataset quality" API / Dataset Quality dashboard used for?
- Shows EMQ, event coverage (how many events have both browser and server), deduplication rate, data freshness and additional conversions reported by CAPI.
- Agencies and developers use it to monitor tracking health at scale.
What is "event coverage" in CAPI?
- The percentage of browser events that also have a matching server event (via deduplication keys).
- Meta recommends high coverage (e.g. 75%+) so that events lost on the browser are recovered on the server.
Expert insight: Meta suggests strong coverage on key events; low coverage means many browser events have no server twin – often because CAPI only sends some events or misses anonymous users.
What is "Additional conversions reported" in Events Manager?
- An estimate of how many more conversions Meta can attribute thanks to CAPI compared with the pixel alone – used to show CAPI's value.
How do you send events from WordPress/WooCommerce, Shopify and custom stacks?
- Shopify: Meta's Facebook & Instagram app with "Maximum" data sharing (pixel + CAPI with dedupe).
- WooCommerce/WordPress: official Meta for WooCommerce plugin or tools like PixelYourSite/Stape.
- Custom: developers call the CAPI endpoint from backend, or use sGTM/CAPI Gateway.
What is a "system user" and why use it for CAPI access tokens?
- A non-human user in the Business Portfolio used for API integrations.
- Its access tokens can be non-expiring and are not tied to an employee's personal account, so integrations don't break when staff change.
Expert insight: Create the system user with "Admin" or "Employee" role, assign only the dataset/ad account assets needed, and generate a token with ads_management/business_management scopes as required – store it in a secret manager, not in code.
Explain how the Marketing API differs from the Conversions API.
- Marketing API: create/manage campaigns, ad sets, ads, audiences, read insights programmatically (used by tools and agencies).
- Conversions API: only sends events (conversions) to datasets.
- Both use Graph API tokens and permissions, but serve different purposes.
How can you pull Meta ads data automatically into a dashboard (Looker Studio, Power BI)?
- Use the Marketing API Insights endpoint (/act_{ad_account_id}/insights) with fields, breakdowns, date ranges and attribution windows; or connectors like Supermetrics, Funnel, Windsor, Power Query.
- Align attribution settings and time zone with Ads Manager for consistent numbers.
Expert insight: Insights API has rate limits and async report jobs for large date ranges; request action_attribution_windows explicitly so numbers match Ads Manager.
What is a "custom conversion" limitation that technical marketers must know?
- Max 100 custom conversions per ad account; they can't be edited in their rules after creation (you may change name/category); deleting stops them; URL rules depend on page URLs staying stable.
- For complex logic use custom events or CAPI instead.
What is "value" in Lead events for value-based optimization and how do you choose it?
- Assign value = expected revenue per lead (average deal size × lead-to-sale rate), or different values for different lead tiers (e.g. AED 50 for basic, AED 300 for high-budget investors).
- Enables value reporting and value-based lookalikes; better to send real deal values later via CRM events.
Expert insight: Tiered lead values allow value optimization in lead gen – but they must correlate with real outcomes; review every quarter against CRM revenue and adjust.
What is the difference between client-side and server-side tracking regarding ad blockers and ITP?
- Client-side (pixel) runs in the browser: blocked by ad blockers, Safari ITP limits cookie lifetime (e.g. 7 days or less for script-set cookies), lost on page close.
- Server-side runs on your servers: not blocked, can set longer-lived first-party cookies (server-set), richer data.
Expert insight: Safari ITP caps JavaScript-set first-party cookies (often 7 days, and as short as 24 hours when link decoration is detected); this shortens _fbp/_fbc life, hurting attribution for longer journeys – server-set cookies and CAPI with customer info mitigate it.
What are Limited Data Use (LDU) / data processing options in CAPI?
- A flag (data_processing_options ["LDU"]) to restrict Meta's use of data for users in certain US states for privacy compliance.
- Not usually needed for UAE campaigns, but it's part of the technical parameter set and shows privacy awareness.
How do you verify that your server events are matched to the correct ad click?
- Include fbc (click ID) and fbp, plus hashed email/phone and IP/user agent.
- Check Events Manager event details: "Parameters" and "Customer information parameters", and EMQ breakdown by parameter.
Expert insight: Event details in Events Manager show which customer information parameters were received and their match contribution; EMQ breakdown helps you see if fbc is missing (often the biggest lever for click attribution).
What does "events received with low-quality IP address" mean?
- Server is sending its own server IP or a proxy/CDN IP instead of the user's IP (client_ip_address).
- Fix by forwarding the real visitor IP (X-Forwarded-For) and user agent from the original request.
How should you handle consent (GDPR/UAE PDPL) technically with the pixel?
- Delay pixel initialization until consent: fbq('consent','revoke') before init, and fbq('consent','grant') after user accepts.
- Only send CAPI events for users who consented where required by law.
Expert insight: For CAPI, mirror the same consent state server-side (don't send events of users who refused, where law requires). Document this in your privacy policy.
What is the difference between "fbq('track')" and "fbq('trackSingle')"?
- track sends the event to all initialized pixels on the page.
- trackSingle sends it only to a specific pixel ID – useful when multiple pixels (brand + agency) are installed and you need to avoid double counting.
Why should you avoid having multiple pixels on one website?
- Confusing data, duplicate event firing, page speed issues, events going to wrong ad accounts.
- Use one dataset per business and share it with ad accounts via Business Portfolio.
How do you share a pixel/dataset with multiple ad accounts or an agency?
- Business settings → Data sources → Datasets → assign ad accounts and partners.
- The agency doesn't need its own pixel; using one dataset keeps learning unified.
Explain Aggregated Event Measurement's impact on reporting delays.
- Events from opted-out iOS users may be reported with delays (up to ~72 hours) and modeled; real-time reporting is incomplete.
- That's why last-24-hour data looks worse and recovers later.
What is SKAdNetwork / AdAttributionKit and how does it relate to Meta app campaigns?
- Apple's privacy-preserving attribution frameworks for iOS app installs; provide delayed, aggregated postbacks without user-level data.
- Meta app campaigns on iOS rely on SKAN/AEM for apps and modeled reporting; MMPs help configure conversion values.
What is an MMP and why is it needed for app advertisers?
- Mobile Measurement Partner (AppsFlyer, Adjust, Branch, Singular) that attributes installs and in-app events across ad networks, deduplicates, and forwards events to Meta.
- Gives one source of truth across Meta, Google, TikTok etc.
How do you track phone calls generated by Meta ads?
- Meta "Calls" campaigns report calls started from ads; for real outcomes use call tracking numbers (dynamic number insertion) on the landing page, and send qualified calls back via CAPI with action_source = phone_call.
What is "event_source_url" and why can it break custom conversions?
- The URL where the event happened; custom conversions with URL rules rely on it.
- If CAPI events have missing/wrong URLs (e.g. server URL), URL-based custom conversions won't count them.
How do you set up a custom conversion for "qualified lead" coming from the CRM?
- Send a custom event (e.g. QualifiedLead) or a standard Lead event with a parameter (lead_status: qualified) via CAPI.
- Create a custom conversion: event = QualifiedLead (or Lead where lead_status = qualified), category Lead.
- Use it for reporting and, when volume allows, for optimization.
What is an "Offline event set" and what replaced it?
- Previously a separate container for offline conversions uploaded via Offline Conversions API.
- Replaced by datasets: offline events are now sent through CAPI with action_source physical_store/system_generated into the same dataset.
What would you check when EMQ for Lead events is 3.5 but Purchase is 8.2?
- Lead events are probably sent from the browser only or without customer parameters (email/phone) – forms often don't pass data to the event.
- Fix by sending lead events via CAPI with hashed email/phone, fbc/fbp, IP, user agent from the form submission.
Expert insight: Lead events often come from form plugins that fire only browser events without hashed data. Fix by sending the lead from the server with em/ph from the form submission + fbc/fbp cookies + IP/user agent; EMQ for Lead usually jumps to 6–8.
Explain "parameter builder" / client libraries Meta provides for CAPI.
- Meta offers SDKs (PHP, Node.js, Python, Java, Ruby) and a Parameter Builder library to correctly normalize, hash and format parameters like fbc/fbp – reduces implementation errors.
What is "domain-level event configuration" and is it still needed?
- After iOS 14.5, advertisers had to configure up to 8 prioritized events per domain in Events Manager.
- Meta has since removed this requirement and manages prioritization automatically; domain verification is still recommended for ownership and link control.
What technical checks would you do before launching a campaign for a new website?
- Pixel base code on all pages, key events firing once, values/currency correct, CAPI live with dedupe and EMQ ≥ 6, domain verified, traffic permissions allowlist, UTMs working in GA4, thank-you page not indexable/reloading duplicates, page speed acceptable.
Expert insight: Add a "launch checklist" document: test purchase/lead on mobile and desktop, every payment method, every form; confirm in Test Events with test_event_code, then remove it before launch.
A Lead event fires twice when the user submits the form. What are possible technical causes?
- Event fired on click and again on the thank-you page; GTM trigger configured twice; both hardcoded pixel and GTM tag; form plugin firing its own pixel event; React double render.
- Fix: one trigger source, test in Pixel Helper and GTM preview.
Expert insight: Use GTM Preview + Pixel Helper simultaneously: if two Lead fires appear with different event IDs, you have two triggers; if same ID, it's a duplicate send from one trigger.
What is "Meta Pixel for WhatsApp" — can you track WhatsApp conversations on the pixel?
- Not directly: once the user opens WhatsApp, the website pixel can't see the conversation.
- Track the click on the site (Contact event), and track chat outcomes using CAPI for business messaging (action_source business_messaging) from the WhatsApp Business Platform/CRM.
What does "Events Manager → Data sources → Settings → Traffic permissions" protect against?
- Other websites firing events into your pixel (by copying the code), which pollutes data and optimization.
- Allowlist your domains; events from others are blocked.
Explain UTM vs URL parameters in Meta ads (the "URL parameters" field).
- The "URL parameters" field appends parameters to the destination URL automatically (e.g. utm_source=meta&utm_medium=paid&utm_campaign={{campaign.name}}&utm_content={{ad.name}}).
- Keeps landing URLs clean in the ad and enables GA4/CRM attribution; dynamic values are replaced at click time.
What dynamic URL parameters are available in Meta ads?
- {{campaign.id}}, {{campaign.name}}, {{adset.id}}, {{adset.name}}, {{ad.id}}, {{ad.name}}, {{placement}}, {{site_source_name}} (fb, ig, an, msg).
- Use IDs for joining data reliably (names can change).
How do you get UTM/source data into instant form leads (which don't open a website)?
- Instant forms don't use UTMs; use hidden fields in the form (custom fields with fixed values per form) or capture ad_id, adset_id, campaign_id, form_id that come with the lead via API/CRM integrations.
Expert insight: The CRM integration (Zapier/HubSpot/Salesforce) receives ad_id, adset_id, campaign_id, form_id for each lead – map them into CRM fields so you can report cost per qualified lead by ad later.
What is the Leads webhook and how do CRM integrations retrieve instant form leads?
- Apps subscribe the Page to the "leadgen" webhook; when a lead is submitted, Meta sends the leadgen_id; the app calls the Graph API to retrieve the fields.
- Requires Page permissions (leads_retrieval) and Leads Access Manager to allow the CRM.
Expert insight: Webhook payload only contains leadgen_id, page_id, form_id, ad_id; your app must call GET /{leadgen_id} with a token that has leads_retrieval permission to get field data.
Why do CRM integrations stop receiving leads after an admin leaves the company?
- The integration was authorized with that person's user token; when their access is removed, the token loses permissions.
- Use a system user or re-authorize with an active admin; check Leads Access Manager.
How long does Meta store instant form leads and where can you download them?
- Up to 90 days in Meta Business Suite → Leads Center / Instant Forms library (CSV download).
- After that, leads must be in your CRM – integrate early.
What is "item_group_id" in a catalog and why does it matter?
- Groups variants (sizes/colors) of the same product; used for content_type product_group, carousel deduplication and showing variants correctly in dynamic ads.
What are the required fields of a Meta product catalog feed?
- id, title, description, availability, condition, price, link, image_link, brand (or GTIN/MPN).
- Optional but useful: sale_price, item_group_id, additional_image_link, google_product_category, product_type, custom_label_0–4, inventory, color/size, video.
Which feed formats and update methods does Meta support for catalogs?
- CSV, TSV, XML (RSS/ATOM), Google Sheets; scheduled feed fetch (hourly/daily/weekly) from a URL, manual upload, partner platform sync (Shopify/Woo), or Catalog Batch API for real-time updates.
- Pixel/CAPI can also update availability via "automatic catalog updates" in some setups.
What causes "catalog items rejected" errors and how do you fix them?
- Missing required fields, invalid price/currency format, broken image links, images too small, policy violations (restricted products), duplicate IDs, unsupported characters.
- Use Commerce Manager → Issues to see the list and fix the feed.
Expert insight: Prioritize fixing items with spend potential (bestsellers) first; rejected items silently disappear from dynamic ads, so a 20% rejection rate can mean your best products never show.

More Meta ads question topics
Want an expert to run your Meta ads?
Book a free strategy call and get a clear plan for your campaigns.