← ClayCONTENT HISTORY
WHAT CHANGED
Update to Clay
Snapshot Nov 18, 2026 · 06:19 UTC · version 2.38.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Clay and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user asks what happened to a lead in a Clay sequence (formerly campaign) — replied, out of office, bounced, unsubscribed, stopped getting emails, needs resuming — or works in the Campaign events table, including how replies and out-of-office count in reply rate, reply categories, rep routing, and automations or workflows built on sequence events.",
"included_files": [],
"name": "sequences-events",
"skill_md_contents": "---\nname: sequences-events\ndescription: Use when the user asks what happened to a lead in a Clay sequence (formerly campaign) — replied, out of office, bounced, unsubscribed, stopped getting emails, needs resuming — or works in the Campaign events table, including how replies and out-of-office count in reply rate, reply categories, rep routing, and automations or workflows built on sequence events.\n---\n\n# Sequence events\n\nBefore using this skill, read the `clay` entry skill if you haven’t already this session, and follow its access guidance.\n\nUse this to explain, filter, or build on sequence activity: the **Campaign events** table, a column, workflow, or\nautomation that reads it, or a question such as \"why did this lead stop getting emails?\". Answer from this skill, not\nfrom general email-sequencing knowledge: Clay configures its email provider in ways that differ from common defaults,\nespecially for out-of-office replies.\n\n## The Campaign events table\n\nEach workspace has one shared Campaign events table (named Campaign webhook events in older workspaces). Every\nsequence writes to it, and each sequence also gets a view named `<sequence name> events` that is filtered to that\nsequence. The table keeps only the most recent 10,000 events. Older rows move to the table's read-only archive,\nwhich the user opens with the View archive button at the bottom right of the table. The table and its per-sequence\nviews therefore show only recent events, and columns, exports, and automations on the table never see archived rows.\nFor an older sequence's full history, point the user to the archive or the sequence's Activity tab, and use `clay\nsequences analytics` for totals.\n\nEvents usually appear within a few minutes of happening. Replies from a mailbox the user connected themselves (rather\nthan one bought in Clay) can be delayed or missing while that mailbox is disconnected.\n\nEach row is one event. The raw payload is in the source column. Managed formula columns extract the common fields:\n\n| Column | Payload path | Notes |\n| ---------------------- | ------------------------------------------- | ---------------------------------------------------------------------- |\n| `Campaign ID` | `smartlead.campaign_id` | The email provider's campaign id, not the Clay sequence id |\n| `Event type` | `event_type` | One of the types below |\n| `Lead ID` | `smartlead.lead_id` | The email provider's lead id |\n| `Audience ID` | `lead.audience_entity_id` | Links to the Audiences contact; `Audience record` looks the contact up |\n| `Lead email address` | `lead.email`, else `recipient.email` | Always the enrolled lead |\n| `Last reply content` | `reply.html` | Only `EMAIL_REPLY` |\n| `Reply category` | `reply.category_name`, else `category.name` | `EMAIL_REPLY` and `LEAD_CATEGORY_UPDATED` |\n| `Sender email address` | `sender.email` | Direction depends on the event type; see `EMAIL_REPLY` |\n\nThe default view shows only `EMAIL_SENT`, `EMAIL_REPLY`, `EMAIL_OPEN`, `EMAIL_LINK_CLICK`, `EMAIL_BOUNCE`, and\n`CAMPAIGN_STATUS_CHANGED`. Unsubscribes and category updates are still in the table. Remove the view filter or use\na different view to see them.\n\n## Fields on every event\n\n- `event_type`\n- `event.description`\n- `event.occurred_at`: when the event happened at the provider (for example, the send, open, click, or reply time).\n Use this field for time, not the row's creation time. It can be missing.\n- `campaign.name`, `campaign.status`\n- `clay_campaign_id`: the Clay sequence id, when Clay could resolve it.\n- `smartlead.campaign_id`, `smartlead.lead_id`, `smartlead.lead_map_id`: the email provider's ids.\n\nEvery event type except `CAMPAIGN_STATUS_CHANGED` also has:\n\n- `lead.email`, `lead.name`, `lead.audience_entity_id`: the enrolled lead, using the address they were enrolled with.\n Use `lead.email` to identify the lead.\n- `sender.email`, `recipient.email`: the addresses as the email provider reported them.\n- `sent` (all of these except `LEAD_CATEGORY_UPDATED`): the sequence email the event relates to (`subject`, `html`,\n `text`, `sequence_number`, `stats_id`). `sequence_number` is the 1-based step in the sequence.\n\n## Event types\n\n### `EMAIL_SENT`\n\nA sequence step was sent to the lead. `sender.email` is your sending mailbox, and `recipient.email` is the lead. After\nthe final step is sent, the lead counts as completed.\n\n`sent.subject` and `sent.html` are the exact copy that went out. Copy edits on a live sequence apply only to leads\nenrolled after the edit, so use this event to check what a particular lead received.\n\n### `EMAIL_OPEN` and `EMAIL_LINK_CLICK`\n\nThe lead opened the email (`engagement.opened_at`) or clicked a link (`engagement.clicked_at`,\n`engagement.clicked_links`).\n\n- These events only fire when open or click tracking is on. Plain-text sequences always turn tracking off, so they\n never produce opens or clicks. If these events are missing, that does not mean nobody engaged.\n- Every repeat open or click is a separate event. Sequence analytics count each sent email at most once.\n- Opens are unreliable: mail clients and security scanners can trigger them automatically.\n- These events never change a lead's status or stop a sequence.\n\n### `EMAIL_REPLY`\n\nThe lead replied.\n\n- **`sender.email` is usually your sending mailbox, not the lead.** For about 98% of replies, the email provider\n reports the reply with the sender and recipient the same way round as the original send: `sender.email` is the\n rep's sending mailbox and `recipient.email` is the lead. In the remaining cases they are swapped. Use `lead.email`\n for the lead. To find the sending mailbox reliably, take whichever of the two addresses is not the lead.\n- The reply is in `reply.html` and `reply.text`, with a shorter `reply.preview_text`. `reply.cc_emails` lists anyone\n else on the reply.\n- `reply.category_id` and `reply.category_name` hold the AI-assigned lead category, if there is one. `category_name`\n is filled only for the standard categories (listed below). A reply that is not categorized yet may be categorized\n later, which produces a `LEAD_CATEGORY_UPDATED` event.\n- `links.reply_url` opens this reply in the Sequencer inbox. It is present only when the provider sent both lead ids.\n- A reply stops that lead's sequence and marks the lead as replied, unless the reply is out of office (see below). If\n the sequence setting to pause other leads at the same domain on reply is on, those leads pause too.\n- The table adds reply-only action columns:\n - `Get rep email` looks up the rep assigned to the mailbox in `sender.email` and returns `repEmail` and\n `repFullName`. It returns no data when no rep is assigned to that mailbox, or when `sender.email` is not one of\n the workspace's mailboxes (the swapped case above).\n - `Forward email` forwards the reply to that `repEmail`.\n - `Reply to lead email` sends the body written in the `Email reply: Body` column as a reply in the lead's thread.\n It does not run for replies categorized as Out Of Office, Wrong Person, Not Interested, or Do Not Contact.\n - `Add email to blocklist` blocks the lead's address. Unlike the other three, it can run on every event type.\n\n### Out of office (OOO)\n\nOOO is a reply category (`Out Of Office`, id 6), not a separate event type. An OOO auto-reply comes in as an\n`EMAIL_REPLY` with that category.\n\n- An OOO reply does **not** stop the sequence, mark the lead as replied, or count as a positive reply.\n- The sequence's Analytics page **does** count OOO replies in its Reply rate, which is all replies divided by emails\n sent. Replies count once per email answered, so two replies to one email count once. The Reply rate tooltip gives\n the count excluding OOO, and a separate Out of office card shows how many replies were OOO. Answer reply-rate\n questions from these definitions, not from general email-sequencing conventions.\n- Leads auto-resume. When the OOO message says when the person will be back and the sequence has at least one step\n left, the sequence is held and resumes on that date. If the return date is more than 30 days away, the sequence\n ends for that lead instead. Clay does not log an event for the hold, the resume, or the end; the next sign of\n activity is the next `EMAIL_SENT`. Do not tell the user to resume these leads by hand.\n- The out-of-office check happens only when the reply arrives. If the reply was uncategorized on arrival, the lead is\n already counted as replied, and categorizing it as OOO later does not change that.\n- The `Reply to lead email` action does not run on OOO replies.\n\n### `EMAIL_BOUNCE`\n\nThe email bounced. The bounce message is in `bounce.html` and `bounce.text`, with a shorter\n`bounce.reply_email_preview`.\n\n- `bounce.is_sender_originated_bounce` separates the two kinds of bounce. `false` means the lead's address bounced:\n the lead is marked bounced and gets no more emails. `true` means the receiving server rejected your sending side,\n often because static copy was flagged as spam. The lead's address may still be good, and the lead is not marked\n bounced. Suggest more copy variation (spintax, AI snippets, sender and lead variables) to reduce these.\n- `lead` can be missing on a bounce. Use `recipient.email` (the `Lead email address` column already falls back to\n it).\n- A high bounce rate on a sequence triggers an email alert to the sequence creator.\n\n### `LEAD_UNSUBSCRIBED`\n\nThe lead unsubscribed. They get no more emails, and the lead is marked unsubscribed.\n\nThis event comes from the unsubscribe link, which only HTML sequences with the link turned on include. A lead who\nreplies asking to stop produces an `EMAIL_REPLY` instead; use `Add email to blocklist` for those.\n\n- `smartlead.lead_id` is usually empty on this event, so match the lead by `lead.email`.\n- `sender` and `recipient` can be missing.\n- `unsubscribe.client_unsubscribed_at` maps each provider client id to the unsubscribe time.\n\n### `LEAD_CATEGORY_UPDATED`\n\nThe lead's category changed, either because the AI categorized a reply or because someone changed it by hand.\n\n- `category.id`, `category.name`, `category.sentiment` hold the new category. `category.old_id` and\n `category.old_name` hold the previous one (null if there was none).\n- `lead_category_update.current_sequence` is the step the lead was on. `reply_body_html` and `preview_text` hold\n the reply that was categorized.\n- Address direction follows the same rules as `EMAIL_REPLY`.\n- A category change does not stop or resume the sequence by itself.\n\n### `CAMPAIGN_STATUS_CHANGED`\n\nThe sequence's status changed: `status_change.previous_status` → `status_change.current_status`. The event has no\nlead fields. It is sequence-level, so filter it out when counting lead activity.\n\n### `MANUAL_STEP_REACHED`\n\nA manual (call, LinkedIn, or to-do) step is due: `manual_step.current_sequence`, `manual_step.scheduled_at`. This\ntype is reserved. Do not depend on it appearing. Completing a manual step can show up as an `EMAIL_SENT` with no\nmailbox and no step number, so do not count those as real sends.\n\n## Lead categories\n\n`Reply category` uses these standard categories:\n\n| Category | Sentiment | Notes |\n| -------------------------- | --------- | ------------------------------------------------- |\n| `Interested` | Positive | |\n| `Meeting Request` | Positive | |\n| `Information Request` | Positive | |\n| `Out Of Office` | Neutral | Does not stop the sequence; the lead auto-resumes |\n| `Wrong Person` | Neutral | `Reply to lead email` does not run |\n| `Uncategorizable by Ai` | Neutral | |\n| `Not Interested` | Negative | `Reply to lead email` does not run |\n| `Do Not Contact` | Negative | `Reply to lead email` does not run |\n| `Sender Originated Bounce` | Negative | The sending mailbox failed, not the lead |\n\nCustom categories also appear, by name, on `LEAD_CATEGORY_UPDATED`. On `EMAIL_REPLY`, a custom category has a\n`category_id` but no `category_name`.\n\n## Building on these events\n\n- Filter on `Event type` first. Columns that read type-specific fields are empty on other event types.\n- For \"who replied\", use `Lead email address`. Do not use `Sender email address`.\n- For \"which rep owns this reply\", use the `Get rep email` column. Do not use `Sender email address` on its own.\n- For \"real replies\", exclude the `Out Of Office` category, and treat an empty category as a real reply.\n- For \"did they bounce\", check `bounce.is_sender_originated_bounce` is `false` before treating the lead's address\n as bad.\n- The same event can occasionally arrive twice. When exact counts matter, de-duplicate on `event_type`, `lead.email`,\n `sent.stats_id`, and `event.occurred_at`. For sequence totals, prefer `clay sequences analytics`.\n"
}SHA-256 of public snapshot: df7b8d642f03e2d262dc84197555b5d506ff955190010bce0a69c2377f2bcc61