FunnelKit Automations Pro - WordPress Plugin

Guide to Setting Up and Using FunnelKit Automations Pro

FunnelKit Automations Pro is best viewed not as a standalone email plugin, but as an automation hub inside WordPress. In this guide, we'll look at how to prepare your site, which settings to review right after installation, how to build your first practical workflow, how to test an abandoned cart scenario, and where to look if emails, events, or REST requests are not firing.

This guide is written for WooCommerce store owners, marketers, site administrators, and developers who help implement automations without risky core modifications. It does not cover purchasing, license codes, or bypassing restrictions. The focus is on an already installed product, safe configuration, validating results, and understanding how the plugin works.

Special attention is given to the issues that often break setups like this: unreliable email delivery, disabled or unstable cron, aggressive caching, firewalls, unclear cart tracking settings, enabling complex branching too early, and weak test order validation. If you work through this guide step by step, FunnelKit Automations Pro will be much easier to implement without creating chaos in your contact database or accidentally emailing real customers.

What Problem the Plugin Solves and Where It Helps Most

The main job of FunnelKit Automations Pro is to connect on-site events with actions that would otherwise have to be done manually or handed off to an external system. In WooCommerce, this is especially noticeable: a customer adds a product to the cart, leaves an email address, places an order, receives a link, clicks through from an email, returns to the store, gets added to a list, or receives a tag. The plugin turns those events into action sequences.

The real value does not come from automation by itself, but from a disciplined connection between event -> condition -> action -> result validation. If the wrong event is selected, the email may go to the wrong segment. If the condition is too broad, the automation may start running for every customer. If you do not verify email delivery and cart tracking, you may see polished workflows in the admin panel without recovering a single real cart.

According to the official materials, the product covers several major areas: automated email and SMS sequences, contact profiles, lists and tags, segments, broadcast campaigns, an email builder, analytics, abandoned cart recovery, transactional emails, and integrations with WooCommerce, forms, CRMs, and external services. For a typical site, that may be more than necessary. For a store where repeat sales, abandoned carts, post-purchase emails, and winback sequences matter every month, it becomes a practical working tool.

Common Use Cases Where FunnelKit Automations Pro Makes Sense

It is best to start with use cases where the result is easy to verify. The simpler the first workflow, the lower the risk of sending unnecessary emails, and the faster the team will understand how the product works.

• Abandoned cart recovery when a contact leaves an email address on the checkout page or a logged-in user adds a product to the cart.
• Post-purchase email sequences: instructions, a review request, a related product recommendation, or a reminder about the next step.
• Customer segmentation by tags, lists, purchased products, order totals, or email activity.
• Broadcast email campaigns sent to a specific audience instead of the entire database.
• Sending data to an external CRM, spreadsheet, webhook, or communication service, if that integration is available in your version and confirmed by the documentation.

The plugin's strongest advantage is how closely it works with WooCommerce. It sees customer events and can connect them to marketing actions without constant database exports. But that does not remove the need for discipline: before launch, you need to configure email sending, verify sender addresses, enable cart tracking only with clear consent text, and avoid complex branching until you have tested everything on a separate contact.

Who FunnelKit Automations Pro Is For and When Another Approach May Be Better

FunnelKit Automations Pro is a strong fit for sites where WordPress and WooCommerce remain the main source of truth. If orders, contacts, carts, coupons, and emails need to stay visible inside the admin panel, this approach is often more convenient than constantly syncing with an external platform. It is especially useful for small and midsize stores, education projects, subscription sites, digital product businesses, membership sites, and stores with repeat purchases.

The plugin also makes sense for teams that want to edit workflows quickly without involving a developer every time. The visual builder, ready-made recipes, and nodes such as Action, Delay, Condition, Split Path, Goal, Jump, and Exit make scenarios easier to build than custom code. But "no-code" does not mean "no planning." Every workflow should have a goal, a limited audience, and a clear success criterion.

When the Plugin Is a Good Choice

The benefits usually show up when automation is tied to real user actions. For example, a store wants to recover some abandoned carts, send different emails to new and returning customers, account for tags, remember subscriptions, send SMS only in specific cases, or see purchase and engagement history inside the contact profile.

The plugin is worth considering if you already use WooCommerce, have a reasonably clean customer database, send email through SMTP or an email service, and have someone responsible for workflow quality. Even a powerful automation plugin quickly turns into a source of noise if nobody reviews the copy, send frequency, exclusions, and analytics.

When the Solution May Be Overkill

For a brochure site, a simple blog, or a store with only a handful of monthly orders, a full marketing engine may be heavier than necessary. If all you need is the standard WooCommerce order email, the built-in emails plus an SMTP plugin may be enough. If the team already works entirely inside a separate CRM and all business logic lives there, FunnelKit Automations Pro can act as a bridge, but it does not always need to become the primary communication hub.

There is also a basic technical reality check: if hosting is unstable, cron is disabled, the REST API is blocked by security rules, and email sending is not configured, automations will behave unpredictably. Fix the infrastructure first, then enable workflows.

What to Check Before Installation and First Launch

Preparation is not just a formality. FunnelKit Automations Pro works with contacts, orders, emails, REST requests, and a task queue. A failure at any layer can look like "the plugin doesn't work," even when the real issue is email, the firewall, cron, user permissions, or endpoint caching.

Before installation, review four areas: WordPress and WooCommerce, your email infrastructure, compatibility with caching and security rules, and your handling of personal data. It is better to spend time before launch than to clean up contacts later, cancel a campaign, and explain to the team why a test email went out to real customers.

Basic Checklist

• WooCommerce is installed and up to date if your automations will use orders, carts, and products.
• Email delivery is configured through SMTP or another known provider instead of relying on a random hosting mail function.
• WP-Cron or server-level cron runs reliably, because delayed actions and queues depend on it.
• Your firewall and cache do not block the plugin's REST endpoints, especially /wp-json/autonami-app/, /wp-json/woofunnels/, /wp-json/autonami/, and /wp-json/funnelkit-automations/.
• You have a test product, a test email address, a test customer, and a separate segment for scenario validation.
• The team understands which emails are marketing, which are transactional, and which require explicit user consent.

Practical rule of thumb: if you cannot send a test email and see it arrive in the right inbox, do not enable live automations. Fix deliverability first, then validate the workflow.

Why Cron and the Queue Matter More Than They Seem

FunnelKit Automations uses a task queue: actions are not always executed instantly, but are processed in small batches. This helps avoid overloading the server during traffic spikes. In practice, that means a delay of a few minutes may be normal, but endless waiting, stuck tasks, and missing emails are signs to check cron, the queue, and logs.

If the store is on weak hosting, do not start with a dozen workflows and a large contact import. Enable one short automation, confirm that it runs, and then add segments, delays, and conditions. This is especially important after a site migration or a cache plugin change.

Installation and Initial Validation Without Risk to Customers

The official documentation describes installation as three parts: the core FunnelKit Automations plugin, FunnelKit Automations Pro, and Connectors. This guide does not cover purchasing or entering a license, but it is important to understand the architecture: the core plugin provides the foundation, Pro enables the commercial features, and Connectors handle part of the integrations. After installation, make sure all required components are active in Plugins and visible in the admin panel.

Your initial validation should be short and controlled. Do not import the full database right away or enable ready-made recipes for a live audience. First create a test contact, configure the sender, send a test email, verify REST access, and only then move on to cart recovery or a post-purchase workflow.

Safe Launch Order

1. Install and activate the required plugin components through Plugins in WordPress.
2. Open the FunnelKit Automations settings and review your general business details, email sender information, and basic contact page settings.
3. Connect SMTP or another confirmed email delivery method, then send a test email to an external address.
4. Create a test list or tag so validation contacts stay separate from real customers.
5. Build a simple automation workflow without coupons or external services, and send the email only to yourself.
6. Check the logs, contact journey, and task statuses. If there is a delay, wait a few minutes and verify cron.

After these steps, you have basic confidence that the interface opens correctly, emails are sent, events are recorded, and contacts stay separated. Only then does it make sense to enable more complex nodes.

Post-Install Setup: What to Enable First

The most useful part of the admin panel after installation is not the builder, but the settings area. The builder tempts you to create a polished workflow right away, but without the correct sender, SMTP, cart tracking, consent text, and exclusions, the result will be unstable. The logic is simple: infrastructure first, then audience, then scenario.

FunnelKit Automations includes separate settings for email, SMS, cart, checkout consent, contact pages, subscribe/profile pages, double opt-in, birthday reminder, advanced settings, logs, and notifications. You do not need everything immediately. For most WooCommerce stores, the minimum starting set is email, cart, logs, notifications, and contact pages if you use public subscription or profile pages.

Email: Sender, SMTP, and Testing

In its documentation, FunnelKit recommends setting up WP Mail SMTP from the Tools section and then moving From Name and From Email into FunnelKit Automations > Settings > Email. That is a sensible order: FunnelKit should not be the only place where you try to fix deliverability. It creates emails and triggers actions, but reliable delivery depends on your mail provider and proper domain authentication.

Check three things: the sender name is clear to the customer, the sender email belongs to your domain, and the reply-to address goes somewhere the team actually monitors. If the sender looks random, users are more likely to distrust the message even if it is technically delivered.

How to Validate Email Settings

• Send a test email through your SMTP plugin and through the Send Email action inside a test automation.
• Check the inbox, spam folder, email subject, sender name, and reply-to address.
• Open the message on mobile and in a webmail client to make sure the template does not break.
• If the email does not arrive, check the SMTP log first, then FunnelKit logs and the task queue.

Cart: Cart Tracking, Wait Time, and Exclusions

Cart settings matter for abandoned cart scenarios. The documentation covers Enable Cart Tracking, Wait Period, Cool-off period, Lost Cart, GDPR notice, tags and lists for abandoned or lost carts, role exclusions, blacklist emails, and the checkout notice. These are not just checkboxes, but rules the plugin uses to decide when a cart counts as recoverable, abandoned, lost, or recovered.

For a typical store, enable cart tracking only after checking the checkout page and the consent wording. Do not make the wait period too short: the customer may simply have stepped away, opened payment in another tab, or been reviewing shipping options. But an overly long wait period also reduces value because the email arrives too late. It is better to start with a moderate value, review actual cart analytics, and only then adjust it.

What Not to Change Without a Reason

Do not add all abandoned users to one broad marketing list if you will not be able to separate them from regular subscribers later. Do not remove role exclusions for administrators and store managers, or your team's test actions will contaminate analytics. And do not use the blacklist as a substitute for proper segmentation: it is an exclusion tool, not an audience strategy.

Logs and Notifications

Logs matter before the first problem, not after it. Configure notifications so the responsible person sees important failures without getting spammed by every test. In larger stores, it helps to agree on ownership: who checks unsent emails, who watches the queue, who handles the firewall, and who edits campaign copy.

Short version: FunnelKit Automations Pro should first prove that it can safely send one test email, record a contact, process an event, and show a status. After that, you can start building marketing logic.

Contacts, Lists, Tags, and Segments: How to Avoid Turning Your CRM Into a Mess

One of the product's strongest areas is contact profiles. They can include lists, tags, custom fields, order history, engagement data, sent emails, and current automation journeys. But the more capability you have, the easier it is to create dozens of nearly identical tags and eventually lose track of which audience actually matters.

Before importing contacts or launching workflows, define a simple naming model. A tag should answer the question "what do we know about this contact" or "what action needs to happen." A list usually represents a more stable audience. A custom field is better for data that changes or stores a specific value. If you use tags for everything, search and filtering become difficult very quickly.

A Practical Segmentation Model

Do not import contacts without a source and consent. If the database came from an older service, validate the CSV format, consent history, unsubscribe statuses, and fields first. A user who already opted out should not suddenly start receiving new marketing emails just because the database was moved into WordPress.

The Visual Builder: Events, Conditions, Delays, and Goals

The builder in FunnelKit Automations Pro is convenient because it shows the workflow as a set of nodes. But every workflow should be read not as a pretty diagram, but as a set of rules for handling a contact. The event starts the automation, conditions decide where the contact goes next, delays control pacing, actions do the work, goals mark the target, and exit ends the scenario.

Start with short logic. A good first workflow fits into one sentence: "If a cart becomes abandoned, wait, send an email, check for a purchase, stop the workflow." A bad first workflow tries to combine coupons, SMS, CRM, split paths, multiple delays, multiple languages, webhooks, and repeat sales all at once. That is hard to test and even harder to explain.

How to Choose a Trigger

The trigger should be as close as possible to the real event. For cart recovery, that is Cart Abandoned; for a post-purchase email, it is an order event; for a form workflow, it is a supported form submission event. Do not choose an overly broad trigger if you plan to restrict everything later with conditions. The more precise the starting point, the less noise you create.

Delay as Protection Against Being Pushy

Delay is not just about timing. It is also about respecting user behavior. In cart recovery, an email sent too quickly can feel aggressive. In a post-purchase workflow, a review request should not go out before the customer has had time to receive a physical product or try a digital one. Delay settings should match the real purchase cycle.

Conditions and Split Path

Conditions help you avoid sending the same email to everyone. For example, you can distinguish a new contact from a repeat customer, segment by product or order amount, or check for a tag. Split Path is useful for testing variations, but it should not replace a real hypothesis. If you do not know what you are comparing or which metric matters, split path only makes the workflow more complicated.

Goals, Jump, and Exit

Goals are especially helpful when you need to stop unnecessary actions after the desired result has been achieved. In an abandoned cart workflow, that result may be a recovered purchase. Jump helps route a contact back to the right node or skip steps, but beginners should use it carefully. Exit should be explicit: a contact should not keep looping through a workflow forever once the goal is complete or the scenario is no longer relevant.

Practical Example: Recovering an Abandoned Cart in WooCommerce

For a concrete example, let's use cart recovery. This is one of the clearest use cases for FunnelKit Automations Pro: there is an event on the checkout page, a customer email address, a delay, an email with a recovery link, and a measurable outcome in recovered carts. That is exactly why it works so well as a first implementation.

Goal

You want to send a careful email to a customer who started checkout, entered an email address, but did not finish the purchase. If the customer returns and places the order, the automation should stop sending follow-up emails. If the customer does not return, you can send a second email with a softer reminder or a personalized coupon, if that approach makes sense for the store.

Preparation

• WooCommerce has a test product with a normal price and an available payment method for validation.
• Cart tracking is enabled in settings, the wait period is defined, and the checkout notice has been reviewed.
• Email sending is configured through SMTP or another chosen provider.
• You have a test email address that does not belong to a real customer.
• A test tag has been created in FunnelKit so the contact is easy to find after the check.

Setup Steps

1. Go to Automations and create a new automation with a clear name, such as Cart recovery test.
2. Select the Cart Abandoned event from the WooCommerce group and save the trigger.
3. Add a Delay. For the first email, do not set the delay to zero, so you do not annoy the customer and you have time to observe the cart state.
4. Add the Send Email action, set the subject, sender, and a short email body. For testing, use a merge tag with the customer's name or a recovery link only where the interface clearly supports it.
5. Add a condition or goal so the scenario does not continue after the purchase. If you use a ready-made recipe, verify that it already stops after recovery.
6. Enable the automation only after sending a test email and checking the contact profile.

Validating the Result

Open the site as a customer, add a product to the cart, go to checkout, enter the test email address, and close the tab before payment. After the wait period, check recoverable carts, the contact profile, and the queue. Then wait for the email, click the recovery link, and complete the order. In the admin panel, you should see the status change: the cart is no longer just abandoned, the order appears in WooCommerce, and the automation stops sending unnecessary reminders.

Note: for guest users, cart tracking usually starts working after the email address is entered at checkout. For logged-in users, the scenario may capture the cart earlier because the site already knows the contact.

Validating Results: Where to Confirm That the Workflow Actually Ran

In automation work, "the email was sent" is not enough. You need to know exactly where the result is confirmed. In FunnelKit Automations Pro, that means checking the contact profile, journey, logs, analytics, carts, and the WooCommerce order state. Each layer answers a different question.

If the email was sent but the order was not recovered, the problem may be the offer, the send timing, the recovery link, checkout, the payment method, or simply customer behavior. If there is no email at all, the problem is technical: SMTP, the queue, cron, the trigger, the condition, the contact status, an unsubscribe, or the firewall.

Validation Map

Once validation is successful, you can enable the scenario for a limited segment. Do not launch it across the entire database if you changed several conditions at once. It is better to change one parameter, verify the result, record your findings, and only then scale it.

Deliverability, Consent, and Communication Safety

FunnelKit Automations Pro can build powerful workflows, but it does not replace the basic rules of email deliverability or respect for the user. Technically, an email may be sent, but if the domain is not configured, the message looks suspicious, the user does not understand why they received it, or consent is missing, the result will be weak and risky.

In the email settings, review the sender, reply-to, bounce handling, and test sending. For marketing messages, use a clear unsubscribe option and do not mix them with transactional notifications. If an action inside an automation should be treated as transactional, verify the relevant interface setting and the legal logic for your project.

How Not to Damage Your Database at Launch

• Do not send a broadcast to an imported database without checking consent and unsubscribe statuses.
• Do not use the same copy for new leads, existing customers, and long-inactive contacts.
• Do not promise a coupon or bonus if the automation cannot reliably deliver it at the right moment.
• Do not enable SMS without separately validating the provider, pricing, user consent, and opt-out wording.
• Do not make emails too frequent: delays and goals exist to stop the scenario at the right time.

A safe practice is to maintain an internal test list where new emails, merge tags, and recovery links are verified. After every email change, send a test, open it as a user would, and click the link. That is much faster than dealing with complaints after a campaign goes out.

Integrations, Webhooks, and Working With External Services

FunnelKit Automations Pro supports many integrations: WooCommerce, forms, memberships, subscriptions, CRMs, SMS, webhooks, Google Spreadsheets, Slack, Zapier, Make, and other services, if they are available in your version and connected through the proper connectors. The important thing is not to treat the integration list as a requirement to connect everything at once.

For implementation, it is better to choose one external connection and validate it completely. For example, send a contact to a CRM after purchase, write an event to a spreadsheet, notify the team, or update a tag in a third-party service. The more external systems you place inside one automation, the harder it is to understand where a failure occurred.

How to Design an Integration

Start by deciding where the source of truth lives. If contact tags are managed in WordPress, do not also update them in the CRM unless you have reverse sync in place. If the CRM is the primary system, FunnelKit can pass the event along, but it should not independently maintain a separate segmentation model that nobody supports.

For webhooks and HTTP requests, agree on the data format in advance. The external service should receive only the fields required for the action. Do not send extra personal data "just in case." Validate the service response, log errors, and make the scenario reversible: if the integration fails, the user should not receive five duplicate emails.

Broadcast Campaigns, Recipes, and Repeat Sales

Automations handle reactions to events, while broadcast campaigns help you reach a selected audience manually. In FunnelKit Automations Pro, it is better not to blur those two approaches together. An automation should work consistently and predictably: a contact enters through an event, passes conditions, receives an action. A broadcast is a separate campaign sent to a segment, where the subject line, audience, test send, unsubscribe handling, and post-send analytics all matter.

The official materials show that the product supports segmented broadcasts, email and SMS marketing, email templates, and A/B testing for campaigns. But for practical implementation, the more important question is: who exactly are you emailing, and why should that contact receive the message? If the audience is defined as "everyone in the database," the broadcast becomes noise. If the segment is built from a purchased product, activity, list, or tag, the message becomes more useful and safer.

How to Use Recipes Without Blindly Importing Them

Ready-made recipes are convenient for getting started, but they should not be enabled as a universal solution. A recipe shows structure, but it does not know your store, shipping times, discount policy, brand tone, or legal copy. After importing it, review the trigger, delay, email text, merge tags, exit condition, lists, and tags. Pay especially close attention to coupons: if the email promises a discount, the coupon logic must be tested on a test order.

A good practice is to import a recipe, rename it to match a clear business purpose, and move it into test mode first. Walk through the workflow as a user: add a product, leave an email address, wait for the email, open the link, place the order, and confirm that the automation stops. Only after that should you switch the audience to real customers.

Post-Purchase Scenarios

After a purchase, do not immediately ask for a review or push another product. The scenario should reflect the product type. For a digital product, it makes sense to send instructions and a link to relevant materials. For a physical product, wait until the expected delivery window has passed, then ask about the experience. For a subscription, remind the user about features they have not activated yet. For repeat sales, offer a related product, but not before the customer has received value from the first order.

In FunnelKit, these scenarios are easy to build using an order event, product or category-based conditions, a delay, and the Send Email action. If you need a tag for future segmentation, add it after the confirmed event, not before. If the user has already received a similar email from another automation, use a condition to exclude them.

Winback and Reactivation

Winback workflows are useful only when the store has a clear definition of an inactive customer. Inactivity means different things for a coffee store and a high-end electronics business. So do not copy someone else's timing. Define how often customers normally return, which products they buy again, and what gap actually indicates lost interest.

For reactivation, a softer sequence usually works better: remind the customer of the value, send useful content, make a tailored offer, and finish with a final email that lets them opt out of similar messages. If the automation starts with a discount right away, you teach part of your audience to wait for coupons. If the sequence is too aggressive, unsubscribes and complaints will rise.

Analytics: How to Tell Whether the Automation Is Actually Helping

The plugin shows metrics such as opens, clicks, revenue, cart analytics, contacts added, unsubscribes, and other indicators depending on the section. That data helps you make decisions instead of guessing. But analytics is only useful when you already know which hypothesis you are testing.

For an abandoned cart workflow, email opens are not enough. Look at how many carts became recoverable, how many emails were sent, how many clicks came through the recovery link, how many orders were recovered, and what percentage of users unsubscribed. If opens are high but clicks are low, the issue may be the copy or the offer. If clicks exist but orders do not, check the recovery link, checkout, coupon, and payment flow. If very few emails are sent, go back to cart tracking and the wait period.

Minimum Metrics to Track

• The number of contacts who entered the automation, so you understand the real size of the scenario.
• The number of completed actions and queued delays, so you can see technical stability.
• Email opens and clicks, so you can evaluate the subject line, copy, and call to action.
• Orders or recovered carts, if the scenario is tied to revenue.
• Unsubscribes and complaints, so you do not improve revenue at the cost of audience trust.

Do not compare two email versions if you also changed the delay, segment, and coupon at the same time. You will not know what actually worked. Change one parameter, define the review period, and then evaluate the result. For a small store, data may be noisy, so do not make sweeping decisions based on only a few orders.

When It Is Better to Turn an Automation Off

Disabling an automation is a normal tool, not an admission of failure. If a scenario sends emails to the wrong segment, generates complaints, breaks checkout, creates too many queued tasks, or depends on an external integration that fails often, pause the automation and find the cause. It is better to lose a few sends than to damage your database and your domain reputation.

Before disabling it, document which contacts already passed through the workflow and which actions were completed. After the fix, you do not always need to rerun the scenario retroactively. In some cases, it is safer to start only with new events so you do not send outdated emails to users for whom the moment has already passed.

Performance and Scaling Without False Expectations

The official documentation highlights several engineering decisions: data is stored in separate tables, admin interfaces are built on APIs, actions run through a queue, and tasks are processed in small batches with load control. That is useful for stores with a growing database, but it does not mean you can ignore hosting quality and cron reliability.

A task queue is a normal part of how the system works. If an automation does not start instantly, that is not always an error. But if the queue is not moving at all, emails are not being sent, and the contact journey is not updating, you need to check WP-Cron, server cron, PHP errors, hosting limits, REST API blocking, and cache conflicts.

How to Scale Carefully

• Start with one automation and a limited segment, then add new workflows gradually.
• Do not import a large database during peak store traffic.
• Check tables and logs after a mass launch or a major broadcast.
• Do not enable complex split paths without a clear metric and an audience limit.
• Keep a staging site or a separate test workflow for email and integration changes.

If the site is already heavy, fix core performance and PHP error issues first. Automation should not be expected to compensate for weak infrastructure. It depends on that infrastructure.

Common FunnelKit Automations Pro Issues and Troubleshooting

Troubleshooting works best when you follow the chain in order: the event appeared, the contact was found, the condition passed, the task entered the queue, the email was sent, the external service accepted the request, and the result is visible in WooCommerce or the contact profile. If you jump straight to email settings, you may miss a blocked REST API or the wrong trigger.

The Email Does Not Arrive After the Automation Starts

Symptom: the contact enters the workflow, but no email shows up in the inbox and there is no clear success signal in the SMTP log.

Possible causes: SMTP is not configured, the action did not run because of the queue, the contact is unsubscribed, a condition filtered the user out, the message went to spam, or bounce handling marked the address as problematic.

What to check: send a test email from the Send Email action, review FunnelKit logs, SMTP logs, the contact journey, and the contact status. If the email never leaves WordPress, the problem is not the automation copy.

How to fix it: configure SMTP, check From Name, From Email, reply-to, bounce handling, and repeat the test with a new contact. If the email arrives after the change, do not blindly rerun the old queue without checking it first, or you may send duplicates.

The Abandoned Cart Is Not Being Captured

Symptom: the user adds a product, enters an email address, closes checkout, but no recoverable cart appears.

Possible causes: cart tracking is disabled, checkout is customized in a way that prevents the email from being stored in time, the wait period has not passed yet, the guest never entered an email address, the user's role is excluded, or the address is on the blacklist.

What to check: whether Enable Cart Tracking is on, the wait period, excluded roles, blacklist emails, the checkout notice, and how the checkout page behaves in your theme.

How to fix it: test on the standard checkout without aggressive caching, enter the email address before closing the tab, wait for the full wait period, and then check recoverable carts. If your theme or checkout plugin changes the field order, test on staging.

The Automation Runs for the Wrong Contacts

Symptom: employees, old customers, or users outside the intended audience receive the emails.

Possible causes: the trigger is too broad, there are no exclusions by role, list, or tag, imported contacts are not labeled properly, or the condition comes after the first email instead of before it.

What to check: the node order in the builder. The condition that limits the audience must run before the send action. Also verify role exclusions and test tags.

How to fix it: disable the automation, add the audience filter at the beginning, test with several contacts, and only then turn the scenario back on. If the wrong audience already received emails, do not start another send until the cause is clear.

The REST API or Builder Is Blocked by the Firewall

Symptom: the builder interface behaves inconsistently, request errors appear, endpoints return access-denied responses, or Cloudflare or another firewall shows blocks.

Possible causes: a WAF, Bot Fight Mode, REST request caching, or security rules that do not recognize FunnelKit Automations endpoints.

What to check: the endpoints /wp-json/autonami-app/, /wp-json/woofunnels/, /wp-json/autonami/, /wp-json/funnelkit-automations/, as well as cache rules and security rules.

How to fix it: add targeted exceptions in Cloudflare or another firewall according to the documentation, do not cache these REST paths, and test the builder again. If you are not sure, limit the exception to exact paths instead of disabling protection for the whole site.

The Task Queue Runs Too Slowly

Symptom: events are recorded, but actions run with major delays or get stuck.

Possible causes: cron is unstable, the server is overloaded, too many tasks were created at once, there are PHP errors, or the hosting provider limits background processes.

What to check: WP-Cron, server cron, system logs, the number of pending tasks, and any recent mass imports or broadcasts.

How to fix it: reduce the load, do not run several large automations at the same time, configure cron at the server level, and validate execution on a small segment. If the issue keeps happening, review your hosting logs and contact technical support.

Video Tutorial for Setting Up an Abandoned Cart Automation

The official cart recovery documentation includes a video tutorial on setting up an abandoned cart automation. It is useful as a visual companion to the practical example because it shows how to choose a trigger, add a delay, configure the email, and verify cart recovery. Use the video as a supplement to the written guide, not as a replacement for testing on your own site.

When FunnelKit Automations Pro Is the Right Choice

FunnelKit Automations Pro is worth using if you want to manage customer workflows directly inside WordPress: view the contact profile, trigger sequences from WooCommerce events, recover abandoned carts, send post-purchase emails, segment your audience, and validate results through analytics. It is not a magic sales-growth button, but a tool that performs well when configured carefully.

Before launching to a real audience, walk through a short setup path: configure SMTP, verify the sender, enable cart tracking intentionally, create a test contact, build one scenario, review the logs, and only then scale up. If you understand which events trigger emails and where the result is visible, you can download the ZIP archive and test the plugin more thoroughly on your own site.

The best implementation outcome is not a huge number of automations, but a few clear workflows the team can explain, validate, and disable safely when needed. Start with one scenario, make it stable, and only then add segments, goals, integrations, and broadcasts when they solve a real business problem.