Sending an email or triggering an activity based on a subscriber’s first login is a powerful way to engage users at a key moment in their journey.

For example, you may choose to send a welcome or onboarding email when a subscriber logs into your website or app for the first time.

Understanding how “First Logged In” is captured

Website or app behaviour can be stored in different ways depending on how tracking has been implemented. Before creating a trigger, you must confirm how the first login event is captured in your data.

Common implementations include:

1. Custom tracked event - A login event may be sent as a tracked event, for example:

    tracked view event = "first_logged_in"
   

2. Login success page tracking - If login redirects users to a specific page, this may be tracked as:

    tracked view page = "/account/login/success"
   

3. Subscriber custom field - The first login date may be stored as a custom field on the subscriber profile, for example:

    cf:first_logged_in
   

The exact field name or event must be confirmed with your relevant team or whoever configured the website/app tracking.

Example event data

Below is a generic example of how a first login event might appear:

{
  "uri": {
    "event": "first_logged_in",
    "page": "/account/login/success",
    "pageUri": "https://www.example.com/account/login/success"
  }
}

Or as a subscriber custom field:

first_logged_in: 2026-06-02T09:30:00

Using this in a trigger

Once you’ve confirmed how the first login is captured, you can configure an event-based trigger and apply the appropriate target expression.

Example target expressions

If using a tracked event:

tracked view event = "first_logged_in" last 24 hours and not sent activity Y

If using a login success page:

tracked view page = "/account/login/success" last 24 hours and not sent activity Y

If using a custom field:

cf:first_logged_in is not null and not sent activity Y

Replace Y with your follow-up activity ID.

If your trigger runs repeatedly, ensure you exclude subscribers who have already received the activity to avoid duplicate sends.

Key considerations

• “First logged in” is not a standard field or event and depends on your implementation
• Always confirm whether it is captured as:
  • A tracked event
  • A tracked page
  • A subscriber custom field
• Ensure tracking is correctly implemented before relying on triggers
• Test using a known subscriber profile where possible

If you have additional questions or require further assistance regarding First Logged In, do not hesitate to reach out to Taguchi Support

---