A block to handle Meta Conversions API events.

The Conversions API is designed to create a connection between an advertiser's marketing data (such as website events, app events, business messaging events and offline conversions) from an advertiser's server, website platform, mobile app, or CRM to Meta systems that optimize ad targeting, decrease cost per result and measure outcomes.

Rather than maintaining separate connection points for each data source, advertisers are able to leverage the Conversions API to send multiple event types and simplify their technology stack by establishing a connection between an advertiser's server and Meta's Conversions API endpoint.

The meta_conversion block compiles to this FLOIP block. The event_name config parameter is required and should be provided as a string expression (e.g., "Purchase" or "@(contact.event_type)"). The user_data parameter is required and should be a map, keyword list, or JSON string of key-value pairs where values are evaluated as expressions (e.g., %{email: "@email", phone: "@phone"} or "{"email":"@email","phone":"@phone"}"). The optional_fields parameter is optional and should be a map, keyword list, or JSON string of key-value pairs where values are evaluated as expressions (e.g., %{event_id: "123", event_source_url: "@url"} or "{"event_id":"123","event_source_url":"@url"}").