Cartful + Meta (Pixel / CAPI)

Does Cartful integrate with Meta?

Yes. Cartful integrates with Meta using Studio’s plugin framework, which gives teams full control over which Pixel or CAPI events are fired, what parameters are included, and how attribution is handled. Clients actively use this integration path in production.

Why Studio’s plugin framework

Meta’s advertising ecosystem evolves constantly — event requirements, attribution models, and consent rules change frequently. A fixed native integration would lock teams into a mapping that quickly falls behind.

Studio’s plugin framework is the intended approach for Meta. It uses the same trigger system and event model as Cartful’s native analytics plugins (GA4, GTM, Adobe Analytics), but gives you full control over the fbq() calls, event names, parameters, and advanced matching. The result is an integration that matches your Meta configuration exactly and adapts when Meta’s requirements change.

How the integration works

Cartful’s Studio platform includes two plugin types that send data to Meta:

Custom JavaScript Integration (client-side Pixel)

Runs in the browser. You implement Meta Pixel calls (fbq('track', ...) or fbq('trackCustom', ...)) within the plugin and configure which Studio events trigger it. This path has full access to the complete set of quiz events.

Available trigger events: quiz start, quiz complete, start over, step enter, step leave, step skip, email submit, email skip, product view, add to cart, answer change, recommendations loaded, and per recommendation loaded.

Custom API Integration (server-side CAPI)

Sends events to Meta’s Conversions API from the server. This path only fires when the shopper completes the email modal, so it has a more limited event scope than the client-side Pixel approach.

What you control

Everything. Cartful does not prescribe which Meta events to fire, what parameters to include, or how to handle attribution. You implement the mapping within your plugin:

• Event names: standard Meta events (Lead, AddToCart, ViewContent) or custom events
• Parameters: content_ids, value, currency, content_type, or any custom parameters
• Advanced matching: hashed email or other user data for attribution, if needed
• Consent gating: Meta-specific consent logic, handled separately from Cartful’s consent model

Common event mappings

These are suggestions, not defaults — you choose what makes sense for your campaigns:

Studio event	Possible Meta event	Why
quiz:complete	Lead or custom event	Signal quiz completion as a conversion for campaign optimization
product:addToCart	AddToCart	Standard ecommerce event for retargeting and ROAS measurement
product:view	ViewContent	Track which recommended products shoppers engage with
recommendations:loaded	Custom event	Measure how often recommendations are delivered

How it works (setup)

1. Create a Custom JavaScript Integration in Studio.
2. Implement Meta Pixel calls within the plugin — fbq('track', ...) for standard events, fbq('trackCustom', ...) for custom events.
3. Configure triggers — select which Studio events fire the plugin.
4. For server-side CAPI (optional): create a Custom API Integration that sends to Meta’s Conversions API. This only fires on email modal completion.
5. Test: run a quiz session and confirm events appear in Meta Events Manager.

If the Meta Pixel is already loaded on the page outside of Studio, you can call fbq() directly from within your Custom JavaScript Integration — the trigger just needs to be defined inside Studio.

Consent considerations

Cartful’s browser scripts queue quiz events until consent is resolved. However, Meta Pixel consent gating is separate and must be handled by your consent management platform. Make sure both layers are aligned so Pixel events are not fired before the shopper has consented.

Retake behavior

Each trigger event fires independently based on its configuration. When a shopper retakes a quiz, the relevant events fire again naturally. There is no special retake handling or deduplication needed.

Good to know

• Plugin-based. The integration is built using Studio’s Custom JavaScript Integration or Custom API Integration rather than a fixed native connector. This is by design — it gives you full control over your Meta event configuration.
• Server-side scope. The Custom API Integration only fires on email modal completion. For full event coverage, use the client-side Pixel approach.
• Meta SDK familiarity helps. Setup is faster if your team is already comfortable with Meta’s Pixel SDK, event types, and (for CAPI) the Conversions API.
• You own the mapping. Cartful does not auto-send a default set of Meta events. You configure exactly what fires, which means you get exactly the data your campaigns need.

See: Integrations hub · Product