Pricing

Risk Free, No Questions Asked Refund

We’ve got your back. Your purchase is covered by our no-risk 14 day money back guarantee. If for any reason you’re not completely happy with the plugin, you’re entitled to a full refund up to 14 days from your original purchase. No questions asked.

Frequently Asked Questions

A license entitles you to free updates and support for one month on the monthly plans and one year on the annual plans.

Your purchase is covered by our no-risk 14 day money back guarantee. If for any reason you’re not completely happy with the plugin, you’re entitled to a full refund up to 14 days from your original purchase. No questions asked.

Once you purchase, you will have access to the support section on your account. You can open tickets and we’ll get back to you within one business day.

Yes. When you upgrade from any license to a superior one you only pay the difference which is calculated against the time until your license period expires.

We will notify you to remind you of the upcoming expiry date. Licenses that are expired don’t benefit from the pro plugin functionality, updates, and support.

Yes. You can activate licenses on local environments without limit and they won’t take from your allowed activations count.

The simplest approach is to go to the WordPress translation page of this plugin here. You’ll need an active WordPress account in order to be able to contribute. Once the translations have been approved, they’ll be available for everyone who is downloading the plugin. Send us an email if the translations don’t get approve for more than a week. We will nudge the translation approvers to have a look. Alternatively we provide the standard .pot file in the /languages/ directory. You can use a tool like https://poedit.net/ to create your own translations.

Due to how the plugin integrates with WooCommerce it works fine with 99.99% of all plugins. There are a few exceptions with plugins that modify the output of the HTML and JavaScript output, like caching an minification plugins. We tested some of those and have compiled a compatibility list: https://docs.woopt.com/wgact/#/features?id=plugin-compatibility-list Usually there is a simple workaround the get everything working fine.

The way how the plugin is designed it almost doesn’t use any processor resources. Also the JavaScripts that are being injected are lightweight. However, the tracking pixels themselves access external servers and therefore depend on server uptime and connection speed. All tracking pixels today use asynchronous code which minimizes connection speed issues. And the tracking pixel providers use high-end CDN’s to serve the server side logic for the tracking mechanism. So the risk of slowing down the website is next to 0%. Also, we’re planning to implement a caching mechanism for the serverside pixel code, which reduces the risk even further.

Yes. You’ll find the changelog here: https://docs.woopt.com/wgact/#/changelog-pro