How Meta lead data is handled

See what Liteo receives from Meta, why it is stored, and what changes when you disconnect.

Reviewed September 8, 2026

Browse all guides
On this page

When a selected Instant Form receives a lead, Meta sends Liteo a delivery event. Liteo verifies that the event came from Meta, records its provider identifier, then requests the complete lead data from Meta using the connected Page access.

What becomes a contact

Mapped answers become fields on a Liteo lead contact. The selected workspace member becomes its owner.

You decide whether Page, form, campaign, ad-set, and ad details are copied into visible custom fields. Liteo keeps the provider identifiers required for delivery and duplicate protection internally even when you leave those visible fields off.

How repeated events are handled

Liteo claims each Meta lead identifier inside the workspace before processing. A repeated webhook or historical import can update the same processing record, but it cannot create another contact for that provider lead.

What disconnecting changes

Disconnecting removes the active Meta connection and stops future lead delivery. Contacts already created in Liteo remain customer records until you delete them or make a data request under the normal Liteo process.

Delivery history remains after disconnecting. For removal requests and contact details, read Liteo’s data deletion instructions.

Still stuck?

Tell us what you expected and what happened. We’ll help you find the cause.

Email hello@liteo.io