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
Your Company Page has 15,000 followers, but your personas are based on assumptions from a strategy deck written two years ago. This job pulls real follower demographics — industry verticals, job functions, and seniority levels — from LinkedIn’s organizational statistics API. It compares those distributions against your existing Mavera personas, then updates (or creates) Custom Personas with actual audience data. The result: personas that reflect who actually follows you, not who you wish followed you.Architecture
Code
Example Output
Error Handling
r_organization_followers scope required
r_organization_followers scope required
Follower statistics need the
r_organization_followers scope, which requires the Community Management API product approval. Without it, the endpoint returns 403.Organization URN format
Organization URN format
The organization URN must be
urn:li:organization:{numericId}. Find your numeric ID on the Company Page admin URL or via GET /organizationAcls.Localized field names
Localized field names
Industry and function names are returned in a
localized object. The code extracts en_US first, falling back to the raw value. Adjust for other locales.Low follower counts
Low follower counts
Pages with under 300 followers produce unreliable demographic distributions. Wait for a larger base before running persona refinement.