Meta Offline Conversions is a method that lets you see how conversions made in your store — whether in-person, by phone, or via reservation — are influenced by the campaigns you run on Meta.
You can also compare people who completed conversions in your store with people who viewed your Meta campaigns, allowing you to see the real impact of your ads.
This way, you can:
- Analyze the online behavior of people who completed offline conversions.
- Review the offline returns of your ads.
- Create lookalike audiences to show Meta ads to people similar to your offline customers.
Before You Send Data to Meta
Before sending your Offline Conversions to Meta, there are some fields in your data you need to pay attention to.
- When sending offline conversion data, the
action_sourceparameter must be sent with the valuephysical_store. - The event parameters that Meta specifies as mandatory must be followed.
- Customer information must be sent in accordance with the parameters Meta requires.
Event parameters
| Parameter | Description |
|---|---|
event_time | Type: integer. UNIX timestamp of the conversion event. Example: 1456870055 |
event_name | Type: string. Type of event. Examples: ViewContent, Search, AddToCart, AddToWishlist, InitiateCheckout, AddPaymentInfo, Purchase, Lead, Other |
store_data | Type: JSON object. Store location data related to the conversion event. Example: "store_data": {"store_page_id": 8576093908, "brand_page_id": 10236898932, "store_code": "64CharacterAlphaNumericString"} |
currency | Type: string. Three-letter ISO currency code for this conversion event. Required for Purchase events. Example: USD |
value | Type: double. Value of the conversion event. Required for Purchase events. Example: 16.00 |
content_type | Type: string. A valid Advantage+ catalog ad content_type value. Example: product |
contents | Type: JSON array. Optional (required if integrating your ads with a catalog). Required fields: id, quantity. Recommended: price, brand, category. Example (required): [{"id": "A", "quantity": 1}, {"id": "B", "quantity": 2}]. Example (recommended): [{"id": "A", "quantity": 1, "brand": "Brand_A", "price": 10.0}] |
custom_data | Type: JSON object. Additional information about this conversion event. Example: {category: 'ICECREAM'} |
order_id | Type: string. A unique identifier for each transaction or order in an offline event set. For retail, this could be a receipt or invoice number. Examples: ATN10001, 123456 |
item_number | Type: string. A unique identifier used to distinguish events within the same order or transaction. Examples: 1, a |
Sending Offline Conversion Data to Meta via Hardal
You can send offline data to Meta in just a few steps from the capig.usehardal.com panel forwarded to you by Hardal.
First, you need to create a Bucket in BigQuery. You will also have a JSON file here.
Then, you need to upload your offline dataset to the Bucket file you created.
After completing the dataset creation steps in the BigQuery panel, go to the capig.usehardal.com domain and define your GCP Bucket under the Automatic File Uploads section. You can then complete the setup by uploading your JSON file.
After your data has been sent, you can open the Meta Ads interface, choose Offline conversions, and review your Offline Conversion metrics there.