Skip to main content

Meta Conversion API

Source code Package

The Meta Conversion API (CAPI) destination is used to send server-side events from walkerOS to the Facebook Conversion API. It handles the data transformation and ensures that your events are correctly formatted for the Meta Conversion API.

Dependencies

Before using the Meta destination, ensure you have:

Installation

To get started, install the package via npm:

npm install @elbwalker/destination-node-meta

Configuration

Example

Configuration
Result

The parameters event_name, event_id, event_time, action_source, and user_data (and event_source_url for website events) are set automatically.

Custom

PropertyTypeDescription
accessToken*stringAds account ID used for every conversion
pixelId*stringAds account ID used for every conversion
action_sourcestringThe source of the event (e.g., website, app)
doNotHashstring[]List of properties to not hash
test_event_codestringTest event code
urlstringThe URL of the page where the event occurred
user_dataobjectCustomer Information Parameters

Mapping

The complete list of all parameters can be found in the Server Event Parameters documentation. Some events require specific parameters.

User Data

At least one user_data parameter is required. These are crucial for matching events to the correct user. It can be set on custom.user_data level, with the data.map.user_data config, or on the event level with mapping.entity.action.user_data. All values will be merged together.

The user_data.fbclid parameter is automatically formatted the fbc value. It is usually available with session start events in data.fbclid.

Destination Config
Result

The values em, ph, fn, ln, db, ge, ct, st, zp, country, and external_id are automatically hashed. The doNotHash property can be used to exclude specific parameters from being hashed.

Purchase

Event
Custom Config
Result
info

If you need professional support with your walkerOS implementation, check out our services.