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
BigCommerce stores custom customer attributes — company type, purchase frequency, preferred categories — via customer attributes. You pull these, group customers into segments by shared attribute values, and create Mavera personas from each real-world segment so generated content reflects actual buyer profiles. Flow: BigCommerceGET /v3/customers?include=attributes → Group by attribute values → Mavera POST /api/v1/personas per segment
Architecture
Code
Example Output
Error Handling
Custom attributes not returned
Custom attributes not returned
The
include=attributes query param is required — without it the attributes array is omitted. Verify your API account has store_v2_customers_read_only scope.Segment too small for useful personas
Segment too small for useful personas
Segments with fewer than 3 members produce generic personas. The code skips these. Combine low-count segments into an “Other” bucket or use a broader grouping attribute.