A dynamic segment answers from its rules every time it is read, so a customer who no longer matches — their tag changed, their score moved — drops out. That is what dynamic means. Use a static segment when the membership must stay put.
The new one. A Send Email node points at a template by id, not at a copy, so the next send picks up your edit. To keep an in-flight campaign sending the old wording, copy the template to a new name and edit the copy.
Reply matching uses the email In-Reply-To and Message-ID headers, and some clients strip them. The reply still arrives in the inbox — it just is not tied back to the campaign. Using a reply-to address specific to the campaign makes the match more reliable.
Corporate mail scanners and provider prefetchers fetch the tracking pixel before a person reads anything. EDGR drops a hit that arrives within five seconds of the send, comes from a known scanner user agent, or carries no user agent at all, which removes most of that noise. Treat what remains as a trend. Clicks and replies are the reliable signals.
LinkedIn invalidates an authorization when it sees something it does not like, and the credential flips to revoked. Reconnect it from Integrations — the campaigns that were waiting on it carry on by themselves once it is active again.If it keeps happening, check the send volume. LinkedIn throttles accounts sending much beyond 50 to 100 DMs a day.
For one customer, click Auto-reply off in the conversation header.For the whole workspace, clear the chat slot under /settings, or revoke the AI credential under /settings/ai. Revoking is the immediate stop: the agent cannot call a model at all.If the replies are close but wrong, the cause is usually the knowledge base rather than the model. Check what is indexed against the product.
Two campaigns with overlapping audiences both send. To prevent it, add a Path node at the start of campaign B that checks for a tag campaign A applies, or have campaign A add everyone it touches to a segment that campaign B excludes.
It runs in the background — the modal says the import is queued and you can close it and keep working. Progress shows up in the customer table as rows land. Files are capped at 15 MB.
Usually that is correct. A Wait node holds a customer for however long you configured, and a messaging node waiting for a reply holds them until its timeout.When it is not correct, open History in the builder and drill into the run to see which node it stopped on. A dead credential pauses the node rather than failing the run; fix the credential and it continues.
No. Deleting would break the deals, activity and segment history attached to them. Archive them instead, which hides them from the table, or suppress their contacts to stop all outreach.
The server enforces the new role on the next request. The menu they see may need a page reload to catch up.
No.
Anything else: support@edgr.ecvhub.net.