Wie richtet man die Facebook-Conversion-API (CAPI) und Google-Offline-Conversions in GoHighLevel ein?

Set up server-side Meta CAPI and Google Offline Conversion pipeline attribution in our GoHighLevel sub-account:
1. Verify that our funnel forms and Lead Ad integrations are capturing gclid and fbclid attribution parameters onto contact records.
2. Create a Pipeline Attribution workflow triggered when an Opportunity moves to "Appointment Booked" or "Job Won".
3. Configure the native Facebook Conversion API step (passing email, phone, fbclid, and deal value) and Google Offline Conversion step so ad spend optimizes for qualified buyers instead of raw form fills.

# 1. MCP Tool Call (ghl-crm-mcp)
{
  "tool": "workflows_create_from_recipe",
  "arguments": {
    "location_id": "<YOUR_LOCATION_ID>",
    "recipe": "pipeline_capi_offline_conversions",
    "trigger_stages": ["Appointment Booked", "Job Won"]
  }
}

# 2. Or run via ghl-crm Rust CLI
ghl-crm workflows apply-recipe --location-id <YOUR_LOCATION_ID> --recipe capi-offline-sync

Official GHL MCP vs. ghl-tools: HighLevel’s official hosted MCP (services.leadconnectorhq.com/mcp) covers public v2 CRM records (contacts, opportunities, appointments, conversations). ghl-tools MCP complements it with workflow graph inspection & recipes, funnel/form builders, DNS/BIMI checks, and ghl-crm doctor audits.