Use Custom Field Tokens and Report Export Columns

Use stable {custom.field_key} email tokens in an exact subscription context and understand how QCMM appends Custom Field columns to applicable CSV report exports.

Email Tokens Use Stable Field Keys

A Custom Field’s machine ID becomes its token key, such as {custom.tree_variety}. Once a field has subscription history, its Field ID is locked so historical token meaning cannot drift.

Exact Subscription Context Is Required

When rendering an email, QCMM resolves Custom Field tokens from the exact subscription or booking context. If no valid subscription context exists, or the field is not part of that subscription, the token resolves blank instead of guessing from another purchase owned by the same user. Customer-facing email also respects the saved customer-visible boundary.

CSV Report Columns

When Custom Fields are available for reporting, QCMM adds columns using the stable custom.field_key form and maps applicable billing/payment/report rows back to their subscription before loading values. Rows without a matching subscription value remain blank rather than borrowing data from another record.

Operational Guidance

Choose durable field keys before production use, keep customer visibility intentional, and test templates and exports with subscriptions that contain distinct values so context mistakes are easy to detect.

Community Discussion

Want to compare QCMM workflows or share practical tips? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.