Yes, through what the ConvertKit for WordPress plugin syncs locally and what the ConvertKit API exposes. SleekAI reads the matched subscriber's ID, email, tags, current sequences, and form signups, then injects the parts you select into the bot's system prompt. You decide which fields enter the context, so private notes and unrelated tags stay out while name, tag, and last broadcast flow through.

Two signals work in parallel. First, ConvertKit's tracking cookie sets a subscriber ID when a tracked link in a broadcast is clicked, identifying that visitor even if they never log in. Second, logged-in WordPress users whose email matches a ConvertKit subscriber load automatically. If neither signal is present, the bot defaults to a stranger persona and no ConvertKit context enters the prompt.

Indirectly. The bot can describe what should happen, like adding a workshop-interest tag, and trigger a webhook that lands in a ConvertKit automation. ConvertKit owns the actual tag add and any sequence entry rules, so consent and double opt-in flags stay enforced. Direct writes from the bot would bypass that logic, which is why SleekAI guides into your automations rather than emulating them.

Yes. Both plans share the same API and the same WordPress plugin behavior; what differs is feature availability inside ConvertKit itself, like advanced reporting and integrations. SleekAI treats either plan identically because the data shapes are identical. The bot can reference whatever the plugin syncs into WordPress, which depends on your ConvertKit account, not on SleekAI.

Yes. Use SleekAI's multibot feature with display conditions on ConvertKit tag presence, form submission, or logged-in state. A common setup is one bot for cold-traffic visitors focused on landing-page Q&A, plus a second bot for tagged subscribers that opens with their name and references the broadcast they just clicked.

Inside WordPress, with full session history per chatbot, the model name, token usage, and the URL the chat happened on. Creators review the logs to refine the prompt and to feed recurring objections back into the broadcast copy itself. Logs stay on your site; LLM providers see only the request payload at inference time, not a stored history beyond that turn.

Only if you remove the expired code from the prompt. SleekAI does not have a campaign-expiry concept; it answers from whatever is in the system message at the time of the request. The standard pattern is to keep an active-offers block in the prompt and rotate it when a launch ends. Once the code is out, the bot stops quoting it on the next request.

Yes. ConvertKit's confirmed, unconfirmed, and unsubscribed states are part of the subscriber record SleekAI reads. Filter the lookup to exclude unsubscribed contacts before exposing tag history, or strip personalization for that group entirely. The bot honors the same deliverability and consent rules your existing forms and sequences already enforce, rather than routing around them.