Step-by-step technical guide to map, format, and send offline sales to Meta via the Conversions API for accurate attribution.
Image via 123RF
Fill out the form below and our team will get back to you within 24 hours
Here's what sets us apart from the competition
Find answers to common questions
Server-side tracking is recommended when you need more reliable event delivery, reduced loss from ad blockers or browser restrictions, and tighter control over data routing and PII. It is typically used alongside client-side tags to improve attribution accuracy and data governance.
Run tag and network debuggers, execute synthetic transactions through the full funnel, reconcile analytics events to backend order and revenue data, and set automated alerts for event drops or source discrepancies. Regular audits of event naming, parameter consistency, and ETL integrity help maintain long-term measurement quality.
We implement consent-aware tag firing, server-side proxies, and cookieless or modeled measurement techniques so key funnel signals are preserved without overriding user choices. All modeled data is labelled in reports to separate observed from inferred metrics.
A typical implementation maps enhanced eCommerce events to a consistent dataLayer, deploys GA4 via Google Tag Manager with optional server-side forwarding, and funnels raw events into BigQuery for attribution, reporting, and downstream ETL. This ensures events are structured for revenue-focused analysis rather than just traffic metrics.
We consolidate events through GA4, server-side tagging, and a central data pipeline (BigQuery/ETL) to reconcile platform conversions with backend revenue. Deterministic identifiers and consistent event schemas reduce discrepancies between platform-reported and first-party data.
In This Article
Prepare clean identifiers
Map to CAPI schema
Validate and monitor
Importing offline conversions into Meta Ads using the Conversions API (CAPI) closes the loop between digital ad exposure and real-world revenue. For US-based eCommerce and B2B teams, offline conversion import reduces reliance on browser signals, improves attribution accuracy, and helps align spend to profitability rather than vanity metrics. This guide explains how to prepare offline data, format events, and send them reliably to Meta's CAPI.
Before you begin, make sure you have: a Business Manager admin role, a Meta Pixel associated with your ad account, and a server or ETL pipeline capable of making HTTPS POST calls. You can import offline conversions via direct server calls to CAPI, partner integrations, or CSV uploads in Events Manager. The typical workflow is:
A clear diagram helps teams visualize how offline conversions reach Meta's systems:
User sees ad → clicks or views (Meta Pixel records if browser) → User converts offline (POS, call center, in-person) → Internal system captures sale and identity data → ETL/server formats and hashes data → Server sends event to Meta Conversions API → Meta matches hashed user identifiers and attributes conversion to ad touch.
Ensure each offline event includes at minimum:
| Offline column | CAPI field | Notes |
|---|---|---|
| Order ID | custom_data.order_id | Useful for de-duplication and reconciliation |
| Customer email | user_data.em | SHA-256 hashed lowercase trimmed value |
| Purchase timestamp | event_time | Unix seconds (UTC) |
| Total amount | custom_data.value + custom_data.currency | Use $ and correct rounding for US dollars |
Hash identifiers server-side with SHA-256. Normalize values first - lowercase, trim whitespace, remove special characters for phone numbers - before hashing. Good data hygiene improves match rates and the value of offline conversion imports.
Compliance note: In the United States, consider state privacy requirements such as CCPA when you collect, store, and share identifiable customer data. Maintain a consent record and minimize PII sent to third parties.
For technical services that include server-side tracking, mapping, and ETL pipelines, see our Services Overview and architecture best practices. For agency background and approach to attribution, visit About Prebo Digital.
Extract offline transactions from POS, CRM, or ERP. Transform records to the CAPI JSON schema and load via one of these methods: server-side HTTP POSTs to the /events endpoint, Bulk Upload CSV in Events Manager, or partner connectors where available. When sending events, include a unique event_id or order_id to allow Meta to de-duplicate with browser pixel events.
Use Meta's Test Events tool and the Event Manager diagnostics to check for schema errors and match rate. Aim for higher match rates by adding more hashed identifiers where available. Address common errors like invalid timestamps, missing currency, and incorrectly hashed emails.
Track two KPIs regularly in the US context: hashed match rate (percentage of events Meta links to known users) and attributed offline revenue versus internal records. Expect match rates to vary by channel and data quality; for example, phone-only purchases may lower hashed email match rates. Use the Ads Manager breakdowns to compare cost-per-offline-conversion against your CAC targets in $.
Map offline conversions to your funnel stages to avoid double-counting and to optimize campaigns:
A US retailer receives a $120 phone order after an ad click. The call center records the customer's phone and order ID. The ETL task runs hourly, hashing phone and email and posting an event with event_name: Purchase_offline, event_time, user_data, and custom_data.value: 120. With clean identifiers, Meta attributes the offline sale to the earlier ad touch for improved CAC visibility.
Common blockers include: inconsistent data pipelines, missing hashing libraries in the stack, and unclear mapping between offline SKUs and ad-level metadata. For systemized implementations that pair server-side tracking with GA4 and tag management, our technical approach combines clean attribution and automation-supported ETL. Learn more about Prebo Digital's technical-first frameworks on the homepage.
If your team needs an architecture review or integration plan for server-side Conversions API imports, consider a scoped growth audit or tracking review to evaluate your pipelines and attribution model. For direct assistance, you can request specifics through our contact page where we discuss technical engagements and long-term tracking strategies: Contact.
Here's what sets us apart
Don't just take our word for it
Keep reading
