Documentation Index
Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
Use this file to discover all available pages before exploring further.
Scenario
LinkedIn Lead Gen Forms capture high-quality B2B leads with job title, company size, and industry — but this data sits in Campaign Manager unused. This job pulls form responses, aggregates them by title cluster, company size tier, and industry vertical, then feeds each segment into Mavera’s persona discovery engine. The result is a set of Custom Personas grounded in who actually fills out your forms, not who you think your audience is.Architecture
Code
Example Output
Error Handling
r_ads_leadgen_automation scope required
r_ads_leadgen_automation scope required
Lead gen form responses need the
r_ads_leadgen_automation scope, which requires LinkedIn partner approval. Without it, the endpoint returns 403.Field name variations
Field name variations
LinkedIn lead gen form field names are defined per form. Common names:
jobTitle, companySize, industry, email. Inspect your form configuration if fields return empty.Deduplication
Deduplication
Leads can submit the same form multiple times. Deduplicate by email before aggregation for accurate persona counts.