---
title: Member registration automation scenarios
related:
  - https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/automation-customization.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

## Member registration automation scenarios

Processes with a _Registration_ trigger run when the _Member registration_ [activity](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/set-up-activities.md#activity-type-overview) is logged for a contact. This activity is logged only when the member becomes active (enabled), for example after confirming the registration when using double opt-in via [email confirmation](https://docs.kentico.com/documentation/developers-and-admins/development/registration-and-authentication/forms-authentication.md#email-confirmation).

### Member to contact mapping

Automation processes always run for a [contact](https://docs.kentico.com/modules/contact-management/contact-management-page.md), not directly for the [member](https://docs.kentico.com/modules/contact-management/members.md) created during registration. The system maps the member to a contact based on the email address submitted during registration.

**Scenario**: A visitor registers after giving consent to be tracked as a contact

- If the registration email matches the current contact's email, the process is triggered for the current contact.
- If the current contact does not have a known email address, the contact's email is automatically updated to match the member registration email. The process is triggered for the current contact.
- If the current contact has a known email address that doesn't match the registration email, the process is triggered for:
  - Another contact, if one exists with a matching email address.
  - A new untracked contact, which is automatically created with the member email if a matching contact doesn't exist (based on [legitimate interest](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/set-up-activities.md#activity-logging-based-on-legitimate-interest)).

In the last case, the process runs for a different contact than the current contact. This means that any subsequent activities by the given visitor, such as page visits or clicks, are not logged for the contact in the automation process. Keep this in mind if the process uses [conditions](https://docs.kentico.com/modules/contact-management/analyze-and-customize-automation.md#rule-based-conditions) that evaluate such activities.

**Scenario**: A visitor registers without giving consent to be tracked, so the current contact is unknown

- If the registration email matches the email address of an existing contact, the process is triggered for this contact.
- If a matching contact doesn't exist, a new untracked contact with the registration email is automatically created (based on [legitimate interest](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/set-up-activities.md#activity-logging-based-on-legitimate-interest)). The process is triggered for this new contact.

In this scenario, the contact in the automation process is untracked, and not directly linked to the visitor. Subsequent activities by the visitor, such as page visits or clicks, are not logged at all. Keep this in mind if the process uses [conditions](https://docs.kentico.com/modules/contact-management/analyze-and-customize-automation.md#rule-based-conditions) that evaluate such activities.

### Contact is member conditions

The _Contact is member_ [condition](https://docs.kentico.com/modules/contact-management/analyze-and-customize-automation.md#rule-based-conditions) is only fulfilled for new members who have the [member registration activity](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/set-up-activities.md#activity-type-overview) logged. This activity cannot be logged retroactively. Pre-existing members who have no registration activity logged will not satisfy the condition.

If you have existing members who may have registered before the _Member registration_ activity became available, the condition will only work reliably in processes with the _Registration_ trigger.

Additionally, the condition requires members to exist and be active (enabled) at the time of the evaluation. If a member's account was deleted or disabled after the member registration activity was logged, the condition is evaluated as false.