Before you begin
- Confirm the LinkedIn app or partner bridge has Lead Sync API access.
- Confirm the authenticated member has the right ad account, organization, and lead access permissions.
- Create the Lead Gen Form and include the privacy-policy URL and consent text required for your region.
- Decide whether the bridge will use lead notification subscriptions or polling to fetch new form responses.
LinkedIn setup
- Request or confirm Lead Sync API access for the app.
- Create or select the Sponsored Account and Lead Gen Form.
- Create a lead notification subscription or configure your approved connector.
- Resolve each lead notification to full lead form response fields.
- POST the normalized response to `https://instachime.com/api/webhooks/capture` with the shared secret header.
Payload example
{
"source": "linkedin_lead_gen_forms",
"linkedin_response_urn": "urn:li:leadGenFormResponse:abc123",
"lead_gen_form": "urn:li:leadGenForm:123",
"full_name": "Casey Nguyen",
"email": "casey@example.com",
"company": "Acme Manufacturing",
"job_title": "Operations Director",
"message": "Requested a LinkedIn demo follow-up"
}Verify
- Create a controlled LinkedIn form submission or connector test event.
- Confirm the bridge retrieves the full response, not only the notification URN.
- Confirm the InstaChime lead includes the LinkedIn response URN, form URN, contact fields, and company fields.
- Confirm alert delivery and CRM webhook delivery.
- Confirm duplicate handling using the same LinkedIn response URN.
Exact LinkedIn setup path
- Create or select the LinkedIn Developer app used for the integration.
- Apply for or confirm access to the LinkedIn Lead Sync API product.
- Confirm the authenticated member has access to the Sponsored Account, Organization, and Lead Gen Form.
- Create the Lead Gen Form in Campaign Manager and attach it to the campaign.
- Create a lead notification subscription or configure the approved connector to detect new form responses.
- When a notification arrives, retrieve the full lead form response from LinkedIn.
- POST the normalized response to `https://instachime.com/api/webhooks/capture` with `x-instachime-secret`.
LinkedIn permissions and ownership
- Confirm API access is for Lead Sync specifically; general Advertising API access is not enough.
- Use an integration user or app owner who will remain with the business.
- Record which LinkedIn organization and ad account are connected.
- Plan token refresh and alerting so the bridge does not silently stop.
- Keep response URNs and form URNs in raw fields for audit and support.
LinkedIn mapping checklist
- Member name -> `full_name` or split name fields.
- Email -> `email`.
- Phone -> `phone`.
- Company, job title, industry, seniority, and country -> raw fields and B2B routing context.
- Campaign and form URNs -> source identifiers.
- Custom question answers -> `message` and raw fields.
LinkedIn troubleshooting
- If notifications do not arrive, check Lead Sync access, subscription status, organization access, and ad account ownership.
- If only URNs arrive, the bridge still needs to retrieve full responses before posting to InstaChime.
- If responses are missing custom questions, confirm the API call requests the fields your bridge needs.
- If the integration stops after a user leaves, move ownership to a durable integration account.
- If duplicates appear, dedupe on the LinkedIn lead response URN.
Official references
These vendor-owned pages explain the controls and requirements referenced in this guide.
- LinkedIn Lead Sync APIOfficial documentation used to verify this setup path and its current vendor requirements.
- LinkedIn Lead Sync overviewOfficial documentation used to verify this setup path and its current vendor requirements.
- LinkedIn Lead Sync current versionOfficial documentation used to verify this setup path and its current vendor requirements.