| numberOfMatches |
Integer (for example 3, 8) |
verified — Raises or lowers how many open introductions count against the member’s Available Introductions on the profile (overrides plan default when set). Recalculated when the member saves the preference. |
Compare with App Settings max-introduction limits. Tooltip reason codes on the profile still apply for other blockers — see no new suggestions. |
| whosFirst |
first, second, random, or premium chip values me / other |
verified — Member premium preference for who should act first on a suggestion; may show a chip on the partner profile when reveal who first is enabled. |
Staff Swap Direction on pending approval only warns for first on initiator or second on responder — not for me / other. See Whos First. |
| hidePartnerImage |
true / false (sometimes stored as string "true") |
verified — When true, the member app hides the partner’s photo on the public profile view for that user. |
On Shidduch request detail, the image-policy chip above the other person’s avatar may read as will be shared (staged reveal) because the viewer turned off partner photos — not because the photo owner blocked sharing. Does not remove photos from Admin score tables. |
| feelBrave |
Small integer (for example 2) |
verified — When your brand enables feel brave and sets a non-zero brave factor in Algorithm settings, the matcher lowers that member’s personal bio-score floor by feel brave × brave factor when deciding in-app suggestions (veteran rules still apply separately). |
Not shown as its own column on potential match scores — compare stored bio % with Algorithm minimums and this key when a member is “just below” the cutoff. Deleting the key restores the default floor on the next suggestion run. |
| walkthroughState |
JSON map of tutorial flags (for example {"homeTab": true}) |
verified — Member app stores which in-app coach marks / walkthroughs the user already saw; syncs across devices when they log in again. |
Rare on introduction tickets. Safe to leave alone unless support resets onboarding UX — clearing local app cache does not reset server flags. |
| language |
Language code (for example en, he) |
verified — Used when the system picks notification / comm language for that profile. |
Changing in Admin is rare; confirm brand locale policy before editing. |
| readReceipts |
true / false |
Stored when the member toggles read receipts in premium account settings. verified — Matched chat UI gates read-receipt display on subscription plan features, not this stored flag alone. |
If ticket says receipts missing but key is true, check plan tier and read receipts app feature — not only party settings. |
| sendMedia |
true / false |
Persisted from premium toggles. verified — Chat media upload in matched conversations is allowed when plan includes send media (customer-support chat always allows upload). |
Same plan-vs-stored caveat as read receipts. |
| deleteMessages |
true / false |
Persisted from premium toggles. verified — Delete-message actions in chat require plan feature delete messages. |
— |
| partnerExtendedData |
Often appears only when the member’s plan includes this benefit (checkmark row in My account) |
verified — Premium benefit tied to subscription tier. Your brand must also enable the extended data (partner) app feature before partner-side extended fields can appear in the member app at all. Which bio/preference rows unlock is configured per attribute on your brand (not a single global list). |
Admin may still see the key on the profile after a plan change. If a member cannot see partner extended fields, check plan tier, app features, and attribute visibility — not only this key. |
| yourExtendedData |
Plan benefit indicator (checkmark in My account when the plan qualifies) |
verified — Same pattern as partner extended data, for your own extended profile fields. Requires the extended data (me) app feature on the brand plus attributes configured for extended visibility. |
Members do not toggle this key like read receipts — it reflects plan eligibility. Staff rarely edit manually. |
| Brand-specific keys |
From the setting attribute group (see Brand setting attributes) |
May participate in pre-validation when rules reference the key. |
Attribute name becomes the stored key. Confirm meaning with your brand’s attribute catalog before writing values in Admin. |