How to Import Offline Conversions for Meta Ads Using CAPI

Overview: why import offline conversions with Meta CAPI

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.

Prerequisites and high-level workflow

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:

• Collect offline event details (e.g., order_id, purchase_time, value)
• Hash and map identity data (email, phone, name) according to Meta's requirements
• Format events to the CAPI JSON schema and include event_source and action_source
• Send events to the Conversions API and validate with Event Manager
• Monitor match rates and attributioned revenue in Ads Manager

Conversion tracking diagram (simplified)

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.

Key data elements for offline conversion import

Ensure each offline event includes at minimum:

• event_name (e.g., Purchase_offline)
• event_time (Unix timestamp in seconds)
• event_source and action_source (server or offline)
• user_data object with hashed identifiers (email, phone, client_ip_address when available)
• custom_data with currency and value for revenue accuracy (use $ for US examples)

Mapping offline fields to CAPI fields

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

Data hygiene and hashing

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.

Step-by-step: build, validate, and monitor your offline CAPI import

1) Build: ETL and event formatting

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.

2) Validate: Event Manager and test 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.

3) Monitor: match rates and revenue reconciliation

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 $.

Funnel placement: where offline conversions sit

Map offline conversions to your funnel stages to avoid double-counting and to optimize campaigns:

• TOF - Awareness metrics (impressions, view-throughs)
• MOF - Leads and offline-assisted conversions (store visits, calls logged)
• BOF - Offline Purchases and closed-won deals attributed via CAPI

Practical example: call center sales for a US retailer

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 pitfalls and fixes

• Low match rate: normalize and hash more identifiers (email, phone, name).
• Duplication: include event_id or order_id to prevent double attribution.
• Timezone errors: use UTC Unix timestamps to avoid mismatched event_time.
• Privacy oversharing: send minimal PII and maintain consent records for US customers.

Where teams usually get stuck

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.

Checklist before going live

• Hashing validated (SHA-256) and identifiers normalized
• event_time uses UTC Unix seconds
• currency set to USD for US reporting
• event_id or order_id included for deduplication
• Event Manager shows successful event receipts and acceptable match rates

Next steps and further reading

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.

Sources

• Meta Conversions API documentation - developers.facebook.com/docs/marketing-api/conversions-api/?utm_source=straider&utm_medium=referral&utm_campaign=prebo-digital
• US Federal Trade Commission - Consumer Privacy Guidance - ftc.gov/?utm_source=straider&utm_medium=referral&utm_campaign=prebo-digital
• General conversion tracking patterns - developer.twitter.com/en/docs/ads/conversion-tracking/overview?utm_source=straider&utm_medium=referral&utm_campaign=prebo-digital