> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/strategies/meta-business/how-leads-are-captured-and-synchronized-with-meta.md).
# How Leads Are Captured and Synchronized with Meta
### Introduction
The integration between Meta (Facebook and Instagram Ads) and the Sprinthub CRM is essential to optimize the capture, storage, and tracking of leads generated by advertising campaigns. This process makes it possible to track everything from a user’s initial interaction with an ad to the final conversion, ensuring that events are properly recorded and analyzed.
### How Data Capture Works in Meta
When a user interacts with a sponsored ad on Facebook or Instagram, سواء by clicking the link or filling out a form within the platform, Meta automatically captures the following data:
* First name
* Last name
* Email
* Phone (if applicable)
* Other custom data defined in the campaign
This information is stored in **Meta Pixel** and in **Ads Manager**, allowing advertisers to have visibility into who interacted with the ad and make decisions based on those insights.
### Transfer of Data to the Sprinthub CRM
If the ad directs the user to a page linked to Sprinthub, the same data captured by Meta is stored within the CRM, automatically generating a new lead. This process triggers an event called **Lead Created**, which signals to the system that a new contact has been registered.
After the lead is created, the Sprinthub CRM sends a corresponding event back to **Meta Pixel**, containing the same lead information. This step is essential so that Meta can correlate the lead initially captured with future interactions and conversions.
### Purchase Event and Validation by Meta
If the lead makes a purchase or completes a relevant action within Sprinthub, a **purchase event** is sent to Meta Pixel. However, verifying that this event belongs to the same lead captured earlier is Meta’s responsibility. This means Meta’s system needs to process and identify that the lead who clicked the ad is the same one who made the purchase.
### Attribution Window and Meta Delay
For a conversion to be correctly attributed to an ad, Meta has a **28-day attribution window**. In other words, if the lead makes a purchase within this period, the event will be linked to the original ad.
However, it is important to consider that Meta has its own delay in displaying events in Ads Manager, which may cause some conversions to take longer to appear in reports.
###
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sprinthub.com/en/strategies/meta-business/how-leads-are-captured-and-synchronized-with-meta.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
