The current field mapping under Meta integration is incomplete and limiting.

Right now, when configuring field mapping from Meta Lead Forms, the system only allows mapping into Contact fields.

Lead (Opportunity) fields and Custom Object fields are not available in the mapping interface.

However, this functionality already exists when creating forms directly inside HighLevel Ad Manager, where mapping is more flexible.

This creates an inconsistency in the platform.

Problem

Only Contact fields are available in Meta field mapping

Cannot map data into Opportunities (Leads)

Cannot map data into Custom Objects (e.g., Vehicle, Service Orders)

Impact

Data is forced into incorrect fields

CRM structure breaks

Automations depending on Opportunities and Custom Objects fail

Requires manual fixes or external workarounds

Expected behavior

Field mapping in Meta integration should allow selecting:

Contact fields

Opportunity (Lead) fields

Custom Object fields

The behavior should match what is already possible inside HighLevel Ad Manager.

This is not a new feature.

This is a missing capability that already exists elsewhere in the platform and should be available in Meta field mapping.