The Facebook Offline Events integration forwards in-store transaction data from Omneo to a Meta Conversions API offline event dataset. This lets you attribute offline purchases to your Meta ad campaigns.Documentation Index
Fetch the complete documentation index at: https://docs.omneo.io/llms.txt
Use this file to discover all available pages before exploring further.
How it works
When atransaction.created event fires in Omneo, the offline event extension receives the webhook and forwards the purchase data to Meta’s Conversions API. Meta matches the transaction against its user data and attributes the purchase to the relevant ad campaigns.
Prerequisites
You need:- A Meta Business account
- A Meta Events Manager dataset configured for offline purchases
- A Conversions API token (generated from your dataset settings)
- Your Omneo tenant credentials (domain, token, shared secret)
Step 1: Create an offline event dataset in Meta
- Open Meta Events Manager
- Click Connect Data Sources → Offline → Get started
- Name your dataset (e.g., “Omneo Offline Purchases”)
- Click Set Up Conversions API and select Purchase as the event type
- Follow the setup wizard and click Open Implementation Guide on the final screen
- Generate a Conversions API token and copy it
- Go to your dataset’s Settings tab and copy the Dataset ID
Step 2: Provide credentials to Omneo
Send the following to your Omneo implementation team to enable the plugin:- Conversions API token (from step 6 above)
- Dataset ID (from step 7 above)
- Mapping of your Omneo location types to Meta offline event source types (e.g.,
{"store": "physical_store"})
Step 3: Omneo configuration
Your Omneo implementation team will:- Configure the
fb-offline-eventplugin settings with your credentials - Create a
transaction.createdwebhook pointing to the offline event extension
Data sent to Meta
For each transaction, the integration sends:| Field | Source |
|---|---|
| Event type | Purchase (fixed) |
| Value | Transaction total |
| Currency | Profile currency |
| Event time | transacted_at |
| Email (hashed) | Profile email |
| Phone (hashed) | Profile mobile_phone |
| Location | Transaction location_id mapped to source type |
Content needed: event matching rate optimisation, PII handling details, and supported Meta SDK versions.