LinkedIn Ads (Conversions API)
The qualified lead goes back to the campaign that produced it.
LinkedIn campaigns optimize toward form fills. This connection moves the target: the lead that later qualifies, books, or buys travels back through the LinkedIn Conversions API with its original li_fat_id attached.
Pages marked Planned are complete specifications written before the connector ships. They validate demand. Connectors with real delivery logs are marked Production or Beta.
Form fills are not qualified leads
LinkedIn counts the download. The decision happens weeks later when sales qualify the lead or close it. Without feedback, bidding keeps paying for volume instead of quality.
Lifecycle outcomes delivered with the original click id
Apointoo preserves li_fat_id from the first touch, joins it to CRM outcomes, and reports each conversion with a stable event id. Qualified-lead optimization becomes possible because the platform finally sees which fills turned into revenue.
What it sends to Google Ads
How the data flows
- Ad click carries li_fat_id
- Apointoo Capture stores the identifier
- CRM confirms the qualified lead or sale
- Apointoo sends the conversion
- Stable event ids prevent double counting
How the connection works
Capture preserves li_fat_id from the LinkedIn landing page.
Your CRM reports qualification and closed revenue.
Apointoo matches each outcome to its original click id.
Conversions post with stable event ids so nothing double counts.
Attribution identifiers
Event mapping
| From | Apointoo |
|---|---|
| Lead captured from LinkedIn traffic | lead_captured conversion |
| Sales-qualified stage | qualified_lead conversion |
| Closed revenue | sale_paid conversion (value) |
Frequently asked questions
The qualified lead goes back to the campaign that produced it.