Mariana Tek Meta CAPI Integration
Meta's pixel misses most of your Mariana Tek revenue. iOS restrictions block it. Ad blockers kill it. Checkout flows on a different domain break attribution entirely. ConversionLoop fixes this by sending Mariana Tek purchase and membership events to Meta CAPI server-side, where nothing can block them.
Key Takeaways
- ConversionLoop sends Mariana Tek purchase events to Meta CAPI server-side.
- Bypasses iOS 14 signal loss and browser ad blockers completely.
- Feeds Meta's algorithm real membership revenue to build stronger Lookalike Audiences.
- Works alongside Google Ads tracking. One ConversionLoop integration covers both.
Why the Meta pixel misses most Mariana Tek conversions
The Meta pixel fires from a browser. It depends on a JavaScript tag running on the page where the conversion happens. For boutique fitness studios using Mariana Tek, the actual purchase or membership signup happens inside Mariana Tek's hosted checkout flow, not on your website.
If your pixel is installed on your marketing site but Mariana Tek handles the transaction, the pixel never fires on the conversion event. You get a view or a click attributed, but Meta never learns that the person bought a membership. Over time, your Lookalike Audiences drift toward clickers, not buyers.
iOS 14 and later restrictions make this worse. Apple's App Tracking Transparency blocks identifier sharing by default, which breaks browser-based attribution even when the pixel is technically on the right page. Studies from Meta's own data show pixel-only setups miss 20 to 30 percent of conversions on average, and for mobile-heavy audiences common in boutique fitness, that number climbs higher.
How server-side CAPI fixes the attribution gap
Meta's Conversions API (CAPI) sends events directly from a server to Meta, bypassing the browser entirely. No JavaScript required. No dependency on the user's device, browser settings, or installed extensions. If Mariana Tek fires a webhook when someone buys a membership, ConversionLoop catches that webhook and forwards the event to Meta CAPI in under a second.
Meta matches the event to an ad account user using hashed email and phone. The match rate for server-side events is typically higher than browser pixel events because email addresses are stable identifiers, while browser cookies can be blocked or expire. A stronger match rate means more conversions attributed, and more conversions attributed means better algorithm training.
What events ConversionLoop sends to Meta
Three core Mariana Tek events map to Meta standard events out of the box.
Fires when a member books any class. High volume. Use to train Meta on early purchase intent.
Fires when a member activates a new membership. Highest revenue value. Primary optimization event.
Fires on class pack, retail, or one-time purchase. Passes revenue value so Meta can optimize for high-LTV buyers.
How to set it up
No code required. Setup takes under 15 minutes.
Select Mariana Tek as your source and Meta CAPI as your destination. ConversionLoop generates a unique webhook endpoint and ingest secret for your account.
Navigate to Integrations in your Mariana Tek admin panel and paste the ConversionLoop webhook URL. Mariana Tek sends a test ping immediately to confirm the connection.
Enter your Meta Pixel ID and a Meta system user token with ads_management permission. ConversionLoop uses these to authenticate CAPI requests on your behalf.
Choose which Mariana Tek webhook events map to which Meta standard events. Membership Created maps to Purchase. Class Booking maps to InitiateCheckout or a custom event, depending on your funnel.
ConversionLoop fires a test event through the full pipeline. Confirm it appears in Meta Events Manager under Test Events, then activate the integration.
How it works alongside Google Ads
Most Mariana Tek studios run both Meta and Google Ads. ConversionLoop handles both from a single integration. When Mariana Tek fires a webhook, ConversionLoop routes the event to Meta CAPI and uploads it to Google Ads offline conversions simultaneously.
You do not need two separate tools or two separate webhook registrations in Mariana Tek. One integration connects to multiple destinations. Both platforms receive the same purchase signal, both optimize toward real studio revenue, and your attribution is consistent across channels.
Read the Mariana Tek Google Ads setup guideCommon questions
No. CAPI complements the pixel. Run both for the best event match rate. CAPI fills the gaps left by iOS restrictions and ad blockers. The pixel still catches browser-side signals that CAPI does not have access to.
Yes. When a Mariana Tek webhook arrives, ConversionLoop routes it to both Meta CAPI and Google Ads offline conversions simultaneously. One integration covers both platforms.
ConversionLoop sends hashed PII (email and phone) for server-side matching, plus event metadata like event name, value, and currency. Raw personal data never leaves ConversionLoop in plain text.
Under 15 minutes. No developer required. No code changes to your Mariana Tek setup or your website.
Start sending Mariana Tek events to Meta today
Connect your first Mariana Tek to Meta CAPI integration in under 15 minutes. No developer, no code changes, no guesswork.
Start free trial