Reference (partial) — Event names and parameters match the Admin picker. Rows marked Verified (app) or Verified (system) were traced in the member app or server code (June 2026). A few picker options have no active emitter yet—those stay marked TBD.

Where activity comes from

Tag rules count end-user activity recorded in analytics (aggregated by profile, event type, and optional parameters). When a rule runs, the system looks back over the Months you set on each condition and checks whether each person reached at least the Count you require.

Activity is not read from profile questionnaire answers directly—use Singles Advanced Search for that. Tags are written to External Info when someone qualifies.

See also: Tag Rules · How to build a tag rule

Parameters (Param 1 / Second parameter)

Many events accept optional filters so the rule only counts specific variants—for example a particular questionnaire, introduction status, or profile status. The condition row shows Param 1 and Second parameter when the event type supports them; hints on screen describe what to pick.

Some events (for example profile status updated) offer dropdowns tied to status lists in Admin. If you leave parameters empty, the rule counts all occurrences of that event type in the look-back window.

Common free-text parameter values (reaction names, login providers, photo change modes) are listed in the parameter value catalogs below.

Parameter value catalogs

Verified values the member app or system sends—use these when filtering Param 1 / Second parameter. Status pickers (introduction, profile, ticket) use your brand’s live status lists in Admin.

Introduction response (intro response)

When you pick intro response as the event, Param 1 often shows a status dropdown (your brand’s introduction lifecycle values) and free-text fields for reaction and location. Use reaction for approve vs decline rules; use status when the same tap should count only from one stage (for example only while the introduction is still in an early “raw” state).

ParameterValues (examples)Plain meaning
reaction approved, semiApproved, rejected, ignored approved — member accepted a ready introduction. semiApproved — member accepted while the introduction was still in an early “raw” state. rejected — member declined. ignored — reserved; confirm with product before using in rules.
status Picker in Admin (introduction statuses) Introduction lifecycle state at the moment the member tapped approve or decline—filter when you care about which stage they responded from. Leave empty to count responses from any stage.
location Free text from app Where in the app the member responded (when the app sends it). Often left blank in current builds—prefer reaction for approve vs decline rules.

Introduction status filter (intro response / intro status updated)

Status pickers use your brand’s introduction lifecycle list—the same values appear on introduction screens and on communication triggers such as Intro Update. Filter on status when the event should count only from one stage:

Status (typical Admin label)Plain meaningExample rule idea
RawNew introduction; neither side has fully approved yet.Intro response + reaction = semiApproved + status = Raw (early accept).
Initiator approvedFirst side accepted; waiting on the partner.Reminder tags for responders who have not opened the profile.
MatchedBoth sides approved; introduction chat is available.AND with chat started to find matches who never messaged.
MM available / MM taking on / MM connectedMatchmaker coordinator workflow (matchmaker brands only).Ops tags on intro status updated—not usually on member tap events.
Engaged / EndedMilestone reached or introduction closed.Lifecycle comms; pair with intro status updated, not intro response, unless you mean the tap that caused the change.
Responder declined / Initiator declinedOne side explicitly declined.Combine with reaction = rejected for decline campaigns.

Login & session

EventParameterValuesWhen to filter
Login attempt mode manual, auto manual — member started sign-in (phone, email, social). auto — app restored an existing session on open.
Login attempt provider Provider name (for example phone, Google, Apple) Count sign-ins for one method only.

Profile & Me

EventParameterValuesPlain meaning
Profile picture changed mode insert, update, removed, hide, unhide, reorder What the member did to their photos—add, replace, delete, hide from public view, unhide, or change order.
Profile snooze type snooze, delete, stay_mekudeshet (brand-specific) snooze — temporary pause. delete — account deletion flow. stay_mekudeshet — special stay-in-network branch when that brand feature is on.
Profile snooze reason Reason id (number as text) Which reason the member picked on the snooze or delete screen—ids match your brand’s reason list.
Profile opened r loraChat, suggestionsList, chatHead Entry point: Lora chat, suggestions list, or chat header.

Questionnaires & chat

EventParameterValuesPlain meaning
Batch content response skipped true, false true — member used skip instead of answering. Pair with contentId to count skips on one step.
Media sent mediaType photo, video Attachment type in introduction chat.

App vs system events

Tag rules read the same analytics warehouse whether the event came from the member app or from a system job (matching, questionnaires, support). The tables below say which side records each event so you know what member action (if any) you are counting.

  • Verified (app) — the member app logs this when the person does something visible (sign-in, opens a profile, answers a step, sends chat).
  • Verified (system) — a server process logs this (new profile, introduction sent, batch finished, ticket status change). The member may not tap anything at that exact moment.
  • Verified (app + system) — both sides can emit the same event name (for example batch started or batch content impression). Counts still aggregate correctly; use parameters to narrow to one questionnaire or content step.

Inactive in picker (July 2026): Me category opened and Native push impression still appear in Admin but are not emitted by the current member app—see Inactive picker options for what to use instead.

Login & session

Event (Admin)ParametersWhen it fires
Login attemptprovider, modeVerified (app): Logged when sign-in starts or finishes—phone, email, social provider, OTP, or automatic restore on app open. provider = method name (for example phone or Google); mode = manual sign-in vs auto-restore.
Logout—Verified (app): Logged when the member signs out from settings (not when the app is closed in the background).

Profile & Me

Event (Admin)ParametersWhen it fires
Profile picture changedmodeVerified (app): After the member adds, replaces, removes, hides, unhides, or reorders a profile photo. mode = insert, update, removed, hide, unhide, or reorder.
Me category openedcategoryIdInactive (July 2026): Listed in Admin but never logged in the current member app. Use Attribute opened when a member expands a field on the Me tab, or Category opened when they expand a bio section on someone else’s profile. Do not build new rules on Me category opened until product re-enables it.
Attribute openedattributeIdVerified (app): When the member expands or opens a profile field on the Me tab (before editing).
Attribute editedattributeIdVerified (app): When the member saves a new answer on Me, profile settings, or attribute editor screens. Filter by attributeId for one field.
Attribute visibility changedattributeIdVerified (app): When the member changes who can see a profile field (visibility policy).
Profile snoozetype, reasonVerified (app): When the member snoozes their profile or completes account deletion/snooze flows from settings.
Profile created—Verified (system): When a new end-user profile row is created at registration (not when the member merely opens the app).
Profile status updatedstatus (picker)Verified (system): When profile lifecycle status changes (Admin, automation, or approval). Filter by status to count reaches of one status.

Questionnaires & content

Event (Admin)ParametersWhen it fires
Batch content impressioncontentIdVerified (app + system): When a questionnaire step becomes visible—the member app logs each Lora message shown; the server also logs when the next step is delivered after pre-validation passes. Filter by contentId for one step.
Batch content responsecontentId, skippedVerified (app): When the member submits or skips an answer in a questionnaire or slide flow. skipped = true when they used skip instead of answering.
Question extended content requestcontentId, batchIdVerified (app): When the member taps “tell me more” / extended content on a question (bottom sheet opens).
Dynamic screen viewedinfoScreenId, typeVerified (app): When a dynamic info screen route opens or an in-app notification presents a dynamic screen.
Batch startedbatchNameVerified (app + system): When a questionnaire flow starts—the member app logs when Lora opens the batch; the server logs when the system assigns that questionnaire to the member. Filter by batchName for one questionnaire.
Questionnaire backquestionnaireIdVerified (app): When the member taps back inside a slide/wizard questionnaire (not Lora chat back navigation).
Info viewedinfoIdVerified (app): When the member taps an in-app info link or help widget.
Batch finishedbatchIdVerified (system): When the server marks a questionnaire assignment complete (all required steps done). Use batchId to count one questionnaire.
Page viewpageName, rVerified (app): On each navigation to a new screen (route push or replace). pageName = route name; r = previous screen name when available.

Introductions & matching

Event (Admin)ParametersWhen it fires
Intro responsestatus, reaction, locationVerified (app): When the member accepts, semi-approves, or declines an introduction. Use reaction to filter approve vs decline; status is the introduction state at tap time.
Profile openedrVerified (app): When the member opens another person’s profile from the suggestions list, Lora chat, or a chat header. r tells you which entry point was used when the app sends it.
Category openedcategoryIdVerified (app): When the member expands an attribute category on someone’s public profile (bio tab).
Image opened—Verified (app): When the member opens a profile photo full-screen (gallery or inline).
Who first clickedstatusVerified (app): When the member taps the “who goes first” control on a paired introduction profile.
Unmatch requested—Verified (app): When the member completes an unmatch request on an active introduction.
Intro sent—Verified (system): When the matching pipeline delivers a new introduction to the member (outbound suggestion published).
Request introduction—Verified (system): When the member asks the matcher for a new suggestion (server-side request logged).
Match service response—Verified (system): When the matching service returns scores for a suggestion run. Diagnostic—use sparingly in tag rules.
Intro status updatedstatus (picker)Verified (system): Logged on the profile whose own action or automation moved the introduction while they were the active party for that status (initiator-side statuses for the initiator, responder-side for the responder). Each transition is recorded once per member. Filter by status for one lifecycle state.
Intro status updated by partnerstatus (picker)Verified (system): Logged on the profile that did not drive the change — when the introduction enters a responder-track status, the initiator gets intro status updated by partner; when it enters an initiator-track status, the responder gets this event. Example: partner approves first → you see this event on the waiting member’s profile. Use for tags like “reacted to partner’s approval” without counting the member’s own taps. Same status picker as intro status updated.

Chat

Event (Admin)ParametersWhen it fires
Chat started—Verified (app): When the member sends the first message in an introduction chat thread (one event per conversation).
Media sentmediaTypeVerified (app): When the member sends a photo or video in chat. mediaType = photo or video.

Contact & support

Event (Admin)ParametersWhen it fires
Ticket createdcontactUsTypeVerified (app): When the member submits the contact-us / support form from the app. Filter by contactUsType for one reason code.
Customer support status updatedstatus (picker)Verified (system): When a support ticket status changes (member or Admin workflow).
Customer support message sent—Verified (system): When an Admin user posts a reply on a mobile-app support ticket (logged from Admin, not from the member typing).

Push & other

Event (Admin)ParametersWhen it fires
Native push impressionmessageId (when live)Inactive (July 2026): Impression logging is commented out in the member app. Use Native push click (member tapped) or Native push sent (system delivered from template) for campaign rules until product re-enables impressions.
Native push clickeventId, eventParamVerified (app): When the member taps a push notification. eventId / eventParam come from the push payload for deep links.
Native push senttemplateIdVerified (system): When the notifications service sends a push from a template. Filter by templateId for one campaign.

Worked examples: How to build a tag rule.

Inactive picker options

These events still appear in the Admin condition dropdown but do not produce analytics rows in the current member app (July 2026). Historical data from older builds may exist—confirm with your analytics team before relying on past counts.

Admin labelWhy it is inactiveUse instead
Me category opened The event name exists in Admin and in the app’s analytics enum, but no screen in the current member app calls it when a member opens a Me-tab section. Attribute opened — member expands one profile field on Me (filter by attributeId). For public-profile bio sections use Category opened (categoryId).
Native push impression Push “shown on device” logging is disabled in the current member app build. Native push click — member tapped the notification. Native push sent — server sent a push from a template (filter by templateId).

When product re-enables either event, update active rules only after you see fresh rows in analytics for a test profile.