Skip to main content

​
Overview

Meta Conversions API lets Newie purchase and subscription activity reach Meta from the server side. It helps ad reporting use real Newie payment outcomes instead of relying only on browser tracking.

​
What You’ll Need

  • Newie connected to Zapier
  • Zapier account with access to Newie and Facebook Conversions
  • Facebook Business Manager account with the right permissions for the ad account, page, and pixel or dataset
  • Zapier added as a partner in Meta if the event is being recorded against a Meta Pixel
  • A clear event plan: which Newie trigger should count as Purchase, Lead, or another event
  • A deduplication plan if the Meta Pixel already sends the same event from the website

​
Common Zaps

Payment Paid → Facebook Conversions: Send Purchase Event Send a Purchase event after a Newie payment is complete for a subscription, instalment plan, or one-off purchase. Map the payment amount, currency, customer email, customer name, and a stable Newie payment or purchase ID if it is available. For BECS Direct Debit, this fires after bank confirmation, not at initial payment submission. Subscription Started → Facebook Conversions: Send Purchase Event Send the billing start as the conversion if your Meta campaign is optimized around new paid subscribers and should count the subscription start, not the earlier purchase event or every renewal. One-Off Purchase Complete → Facebook Conversions: Send Purchase Event Send a purchase conversion when a customer buys a one-off purchase. Use Payment Paid when the workflow needs confirmed payment across all service types. Subscription Created → Facebook Conversions: Send Lead Event or Send Other Event Send a lead or custom lifecycle event when the customer first purchases a subscription, especially if billing starts on a future date. Choose this only when the Meta account has a clear event strategy for leads or non-purchase lifecycle events.

​
Setup at a Glance

  1. If you have not connected Newie yet, follow Connecting Newie to Zapier first.
  2. In Zapier, create a new Zap and choose Newie as the trigger app.
  3. Pick the Newie trigger that matches the conversion: Subscription Created for the initial subscription purchase, Subscription Started for when billing starts, Payment Paid for confirmed revenue, or One-Off Purchase Complete for one-off purchases.
  4. Add Facebook Conversions as the action app and authorize the correct Meta business account.
  5. Choose Send Purchase Event for revenue events, or Send Lead Event / Send Other Event for a non-purchase lifecycle event.
  6. Map the Newie fields into the Facebook Conversions action, including customer identifiers, event time, value, currency, and a stable event ID when one is present.
  7. Test the Zap, then check Meta Events Manager and Zapier task history before turning it on.

​
Notes

  • Facebook Conversions is an action app in Zapier. Newie is the trigger app.
  • Do not send both Subscription Started and Payment Paid as the same Purchase event unless your event IDs and reporting plan prevent double counting.
  • If the Meta Pixel also sends the same event, the browser event and Conversions API event need matching event names and matching event IDs for Meta to deduplicate them.
  • For purchase reporting, map both value and currency. A Purchase event without those fields may be less useful for revenue reporting and ad optimization.
  • Send only customer data you are allowed to use for advertising measurement. Do not map sensitive notes, private messages, or unnecessary internal fields into Meta.
  • Zapier fields and Meta permissions can vary by account, pixel, dataset, and business access. Test inside the connected Zapier and Meta accounts before relying on the Zap in production.
Last updated: 2026-06-26