Getting & Displaying Custom Registration Field Data — a customization topic from the APG vNext community covering themes, skins, and UI adjustments.
APG vNext Customization Overview
- Skins: Each forum can use a separate skin. Skins are stored in
App_Themes/as CSS + image sets. - Master Pages: The
.masterfiles control the overall page layout — header, footer, and navigation. - User Controls: Custom
.ascxcontrols can be added to the header, footer, or sidebar regions. - Theme-specific JS: JavaScript can be loaded per-theme via the skin's master page.
- CSS Override: Add a
custom.cssfile to your skin folder for targeted overrides without modifying core files.
See Template Customization Guide and Features Overview.
Custom Registration Field Data - API Access and Advanced Display
This follow-up thread covers accessing custom registration field data via the APG vNext REST API and implementing advanced display patterns like conditional field visibility and field-based member segmentation.
Accessing Custom Fields via REST API
GET /api/v1/members/{memberID}/profile
Authorization: Bearer {api-token}
Response:
{
"memberID": 123,
"username": "john.doe",
"customFields": [
{"fieldName": "Company", "fieldValue": "Acme Corp"},
{"fieldName": "JobTitle", "fieldValue": "Developer"}
]
}Conditional Field Visibility
Show certain custom fields only to specific member groups:
<!-- In member profile template -->
<%# if (Member.IsInGroup("Moderators") || CurrentUser.IsAdmin) { %>
<dt>Internal Notes</dt>
<dd><%# Member.GetCustomField("InternalNotes") %></dd>
<%# } %>Member Segmentation by Custom Field
-- Find all members who listed "Developer" as their job title:
SELECT m.UserName, m.Email
FROM apg_Members m
JOIN apg_MemberFieldValues v ON v.MemberID = m.MemberID
JOIN apg_RegistrationFields f ON f.FieldID = v.FieldID
WHERE f.FieldName = 'JobTitle'
AND v.FieldValue = 'Developer';
-- Use this list for targeted forum notifications or newsletter segmentsRelated Resources
Exporting Custom Registration Data for Analytics
Custom registration field data collected by APG vNext is stored in the member profile data tables and is accessible for export and analysis. Community managers use this data to understand the member demographic profile, segment members for targeted communications, and measure how the community's composition changes over time. Export custom field data for analysis using the APG vNext admin CSV export (Admin Panel → Members → Export → Include Custom Fields) or by querying the database directly. For ongoing analysis, set up a scheduled SQL Agent job to export a weekly snapshot of member custom field data to a CSV file or a business intelligence tool such as Power BI or Tableau. Ensure that data exported for analysis is handled according to your community's privacy policy and applicable data protection regulations — member custom field data may include personal information subject to GDPR or similar regulations.
Custom Field Reporting and Analytics
APG vNext custom registration field data can be included in the admin member reports to provide demographic breakdowns of the community. Enable custom field columns in the member report by navigating to Admin Panel → Reports → Members → Customise Columns and selecting the custom field checkboxes. The resulting report shows each member's custom field values alongside standard member data (join date, post count, last active date), allowing segmentation analysis — for example, comparing the post frequency of members who listed Beginner vs Expert skill level, or identifying which industry segments are most active in the community. Export the report to CSV for external analysis in Excel, Power BI, or any data analysis tool that supports CSV import.
Dynamic Custom Fields Based on Member Role
APG vNext supports dynamic custom field visibility based on member role — certain custom fields can be shown only to members in specific roles. For example, a Moderator Notes field can be visible and editable only by administrators and moderators, while remaining hidden from regular members and guests. Configure role-based field visibility in Admin Panel → Members → Custom Fields → [Field Name] → Role Visibility. Role-specific fields allow the member profile to serve as a lightweight CRM for community managers — recording notes about specific members, their communication history, or any special circumstances without exposing this information to the member themselves. This capability is particularly useful for communities that manage member relationships with a level of care similar to customer relationships, such as paid membership communities or professional networks.
Custom Fields for Member Onboarding
The registration form is the first interaction a new member has with the community after signing up, and the custom fields you collect at this stage set the tone for the relationship. Limit registration custom fields to information that is genuinely needed to personalise the member's experience — every additional required field reduces registration completion rates. Optional fields for enrichment (bio, social profiles, areas of expertise) can be collected through a post-registration profile completion prompt that invites members to complete their profile after their first login, rather than requiring it before they can access the community. APG vNext's profile completion prompt is configurable in Admin Panel → Members → Profile Completion and can be set to appear after the first login, after the first post, or at a configurable number of days after registration.
Looking for more help? Browse the support forum or check the Knowledge Base.