CTX Feed Pro - WordPress Plugin

A Practical Guide to Setting Up CTX Feed Pro for WooCommerce Product Feeds

CTX Feed Pro is not just a tool for exporting a list of products from WooCommerce. In a real store workflow, the plugin becomes the layer between product pages, advertising channel requirements, and the routine data checks you need before submitting a feed to Merchant Center, Meta Commerce Manager, TikTok Shop, Bing Shopping, or another catalog platform.

This guide walks through the practical workflow: what to verify before installation, how to create your first feed, which settings you should not skip, and how to work with product variations, filters, dynamic attributes, category mapping, automatic updates, and diagnostics. It is written for WooCommerce store owners and administrators who do not just want to click Generate Feed, but want to understand why a feed is accepted or rejected by a channel.

This guide does not replace the official WebAppick documentation or the requirements of individual marketplaces. Its purpose is to connect those sources into a practical working workflow, show typical solutions, and point out where it makes sense to pause and double-check your data before connecting the feed to paid traffic.

What Problem the Plugin Solves and Where It Fits in the Sales Pipeline

A product feed is a file or URL that contains product data such as the title, description, link, image, price, availability, category, identifiers, shipping details, and other attributes. An advertising channel reads that file and uses it to build product listings, catalogs, dynamic ads, or free product placements. If a required field is missing, the data does not match the product page, or the format does not meet the channel's requirements, the problem usually appears not in WordPress, but in Google, Meta, or another external platform.

CTX Feed Pro covers the gap between WooCommerce and the external channel. The plugin pulls data from products, variations, categories, attributes, custom fields, and store settings, then packages it into a format the selected channel can read. On the official product page and in the WordPress.org directory, the developer highlights support for many channels, ready-made templates, and multiple export formats. In practical terms, that means a store administrator does not have to hand-code XML or CSV files, but can manage the mappings through the WordPress interface.

The biggest advantage of this approach is not the speed of the first feed generation, but the control it gives you over a recurring process. Stores change prices, stock levels, descriptions, images, product statuses, and variations. The feed has to stay updated, otherwise the ad channel may show an outdated price, send shoppers to an unavailable product, or reject the item because it does not match the landing page.

The plugin becomes especially useful when the same catalog needs to be sent to multiple destinations. Google may require one set of attribute names, Meta another, a local aggregator a third format, and an affiliate network a separate file structure. CTX Feed Pro lets you build multiple feeds from the same WooCommerce catalog while applying different templates, filters, and processing rules to each one.

What Not to Expect from a Feed Manager

The plugin will not fix a weak product database on its own. If your products do not have solid images, clear titles, current prices, populated brand data, or proper identifiers, CTX Feed Pro can help output, transform, or filter some of that data, but it cannot turn empty product pages into a reliable commercial catalog. That is why it is better to start with a WooCommerce audit, not with a channel template.

The plugin also does not guarantee approval in an ad account. The external channel makes that decision based on its own rules. CTX Feed Pro helps you prepare a correctly formatted file, but you still need to verify image rules, restricted products, landing pages, language, currency, and shipping requirements against the channel documentation.

Who CTX Feed Pro Is For, and When a Simpler Option Makes More Sense

CTX Feed Pro is a strong fit for WooCommerce stores where product data is already being used, or will soon be used, in marketing channels. A typical scenario is a store that wants to send its catalog to Google Merchant Center, Meta Catalog, TikTok Shop, Bing Shopping, Pinterest, eBay, comparison shopping platforms, or affiliate networks. The more channels you use, and the more often products change, the more valuable a dedicated feed management tool becomes.

The plugin works well for a marketer who is responsible for product ad quality but does not want to ask a developer to edit XML every time. It also fits store owners with large catalogs who need to exclude products without images, change the price format, add UTM parameters, export only seasonal categories, or split feeds by country and currency. It is also useful for agencies managing multiple WooCommerce projects and wanting to reuse a proven feed structure.

If the store is small, sells only a few products, and uses just one official channel, a narrower solution may be enough. For example, Google for WooCommerce works well when the task is limited to connecting WooCommerce with Google. But if you need multiple files, flexible filtering, dynamic values, channel-specific categories, and control over output format, CTX Feed Pro gives you much more room to configure the workflow.

When the Plugin May Be More Than You Need

If products rarely change, the catalog is uploaded manually once every few months, and your ad channels do not require a complex structure, a full feed manager may be heavier than necessary. In that situation, first estimate how many feeds you will actually need, who will monitor errors, and whether the store has enough usable data to justify automation.

Another case is a store with a non-standard architecture where prices, stock levels, or images come from an external system and are not stored in WooCommerce in the usual way. Before going live, test on a site copy: create one feed, check whether the plugin can see the required fields, whether it handles variations correctly, and whether products disappear because of query settings, caching, or non-standard meta fields.

What to Check Before Installation and First Launch

The most common mistake in feed setup is starting with the channel before checking the source data. CTX Feed Pro can only work with the data that already exists in WooCommerce. If product pages are filled out inconsistently, the feed will be inconsistent too: some products will be missing descriptions, some images, some the right category, and some a valid identifier.

A Quick Product Data Audit

Before installation or initial setup, review several groups of products: a simple product, a variable product, a discounted product, an out-of-stock product, a product from an important category, and a product with custom fields. For each one, check whether the title, short and full description, main image, price, availability, SKU, brand, size or color attributes, categories, and tags are filled in. If some data is stored through ACF, an SEO plugin, a brand plugin, or a multi-vendor extension, note exactly where that data should come from.

For Google Merchant Center, the accuracy of the title, description, image, price, availability, and identifiers is especially important. Google's official documentation specifically warns that incorrect or missing information can lead to disapprovals, limited visibility, or inaccurate product display. That is why your first feed should be built on a small, controlled set of products, not on the entire catalog right away.

Technical Site Readiness

Make sure WooCommerce is working reliably, products load correctly on the public storefront, images are accessible without login, and your caching plugin is not serving outdated files from the uploads directory. CTX Feed stores generated files in the WordPress uploads folder, so problems with write permissions, aggressive caching, or blocked URLs may show up as "the feed is not updating" or "the channel sees the old price."

If the site's built-in WordPress cron is disabled or traffic is low, automatic updates may not work the way a marketer expects. WebAppick explains in its documentation that WP-Cron depends on site visits, and that you can use server cron or a third-party cron service for a more reliable schedule. This guide will not walk through server commands step by step, but the principle matters: for a store with frequent price and inventory changes, the feed schedule needs to be tested separately, not assumed to be reliable by default.

Practical pre-launch check: choose 10 to 20 products of different types, update the price on one, the stock level on another, and the image on a third, then after generating the feed make sure those changes actually made it into the file.

Installation and Initial Verification in WordPress

The base installation path is standard for WordPress plugins: through Plugins and Add New, or by uploading a ZIP archive. The free version listing on WordPress.org notes that after activation, the CTX Feed menu appears in the admin panel, and the first feed is created through CTX Feed and Make Feed. For Pro features, what matters is that the correct edition of the plugin is active, but this guide does not cover purchasing, license activation, or workarounds for obtaining the paid version.

After activation, do not rush to submit the feed to an ad platform. First open CTX Feed, Make Feed, Manage Feeds, Settings, and Status, and see which options are available in your installation. The interface may vary slightly between versions, but the logic stays the same: create a feed, choose a template, map attributes, generate the file, verify the URL, and configure updates.

First Steps After Activation

1. Open CTX Feed and make sure feed creation is available.
2. Go to Settings and review the general options, including debug mode, query settings, and plugin cache.
3. Open Status and check for obvious warnings related to WP-Cron, write permissions, or the environment.
4. Create a test feed for one channel, but do not connect it to an external account yet.
5. After generation, open the file in a browser and manually inspect several products.

Checking the file in a browser sounds simple, but it often saves hours. If the XML does not open, the CSV is empty, the URL shows an old price, or the file contains fewer products than expected, it is much better to catch that before uploading it to Merchant Center. In Manage Feeds, you can usually view, regenerate, download the file, export the configuration, and download the log. That is your working control panel, not just a list of created feeds.

Creating the First Feed: Template, Format, Country, and File Name

Feed creation starts not with attributes, but with context. You choose the country, channel or template, file format, and file name. Those settings determine which fields appear in the mapping table and how the external service will read the result.

Choosing a Channel Template

In WebAppick's documentation, the template is described as one of the key settings because it defines the attribute set for a specific channel. Google Shopping requires one group of required and recommended fields, Facebook Catalog another, and Bing or a local aggregator something else again. If you choose the wrong template, the feed may generate successfully, but the external channel will expect different field names or a different structure.

In practical terms, that means you should define the destination first. Not "make an XML file," but "build a Google Shopping feed for the main country," "build a Facebook Catalog feed for Meta Commerce Manager," or "build a separate CSV for an affiliate network." Once that is clear, choose the template and format.

File Format and Result Readability

CTX Feed supports several feed formats. Official sources mention XML, CSV, TSV, TXT, XLS, and JSON, although the availability of a specific format depends on the channel. XML is convenient for structured shopping channels, CSV and TSV are easier to review in a spreadsheet, and JSON is useful where a channel or integration expects that format. For a first test, XML or CSV is usually the easiest choice: XML opens quickly in a browser, while CSV is easy to inspect in tabular form.

The file name should be unique and easy to understand. Do not call the feed simply feed or google if you plan to have multiple countries, languages, or channels. A structure like google-main-us, meta-catalog-en, or bing-sale-products is much clearer. That makes it easier in Manage Feeds to see which URL is connected to which external account.

Country, Language, and Currency

The selected country affects channel requirements, shipping rules, taxes, and data localization. CTX Feed documentation separately covers language and currency settings, and the product page lists compatibility with popular multilingual and multi-currency solutions. If your store works in multiple languages, do not try to send everything in one universal file. In most cases, it is safer to create a separate feed for each language or country so that titles, descriptions, currency, links, and categories match what shoppers actually see on the landing page.

Do not mix markets unless there is a clear reason. If the channel checks whether price, currency, and language match the landing page, one "global" feed for multiple countries can create more errors than value.

Attributes, Product Variations, and Output Rules

Once the template is selected, the most important part of setup begins: attribute mapping. The feed table links each channel field to a data source in WooCommerce. For example, the channel expects title, and you choose the product name, a modified title, or a dynamic attribute. The channel expects image_link, and you choose the main image. The channel expects availability, and you choose the stock status or a transformed value.

Value Types in Attribute Rows

The feed creation documentation describes types such as attribute and static value, along with prefix, suffix, output type, and command. In day-to-day configuration, that gives you several practical scenarios:

• Live product field. Each product gets its own value: title, price, link, SKU, category, description, image, or variation attribute.
• Static value. The same value is sent for all products, for example a shared brand if the store sells only its own label.
• Output transformation. A description is stripped of HTML, a price is rounded, extra spaces are removed, or an XML value gets CDATA when needed for a valid file.
• Prefix or suffix. A symbol or text is added to the value, such as a currency or unit, if the selected channel allows it.

Not every transformation is safe to enable by habit. For example, removing HTML from a description is often useful because advertising channels usually want clean text. But adding an arbitrary suffix to a price can break the format if the channel expects the number and currency separately. The rule is simple: every transformation should either satisfy a channel requirement or solve a real data problem.

Variable Products

Variations are one of the biggest sources of product feed errors. In WooCommerce, the parent product may not have its own price or stock level, while the actual values live on the variations. CTX Feed lets you choose how to include variable products: only the parent product, all variations, default variation, first variation, last variation, or parent + variations. The documentation also describes settings for parent product price and quantity.

For clothing, shoes, cosmetics, furniture with color options, or products with multiple sizes, sending variations is often more useful because the channel needs the exact color, size, price, and availability. But for some catalogs, promoting the parent product page makes more sense so you do not fragment the reporting. The right choice depends on the channel, the store structure, and the quality of your variation data.

How to Verify the Selected Variation Mode

Take one variable product and calculate how many rows it should produce in the feed. If all variations mode is selected, the file should contain separate entries for the variations, not just the parent. If parent mode is selected, check where the price comes from: the first, minimum, maximum, or another logic available in the setting. Then compare the feed with the public product page. A mismatch in price or availability on variation items is a common reason for rejection in shopping channels.

Filters and Category Mapping: How to Keep Weak Products Out of Ads

Filters in CTX Feed Pro are not just there to make the interface look complete. They help protect budget and reduce the number of rejections. If your ads include products without images, with empty descriptions, no price, outdated stock, or incomplete categories, the channel may reduce visibility and shoppers may leave the page. WebAppick's official documentation specifically highlights basic filters, product/category filters, tax/shipping utilities, string replace, and advanced filter options.

Basic Quality Filters

For a first advertising feed, it is usually worth checking filters that exclude products missing key data. CTX Feed documentation mentions settings for removing products without a description, image, or price, along with excluding out-of-stock and backorder items. That is not a universal rule for every store, but it is a strong starting point for channels where data quality affects approval and click performance.

If you sell made-to-order products, backorder may be a normal state. If you run a preorder catalog, excluding those products may shrink the assortment too much. So you should enable a filter not because of its label, but because it matches the business logic. For each filter, ask: "If this product appears in ads, will the shopper be able to understand the price, see the image, and buy it without surprises?"

Advanced Filters for Profitable and Seasonal Product Groups

Advanced filters let you build conditions based on price, category, stock quantity, tags, custom fields, and other data, and combine those conditions through AND/OR logic. That is useful if you want to send to a specific channel only products above a certain margin, only seasonal inventory, only published products in selected categories, or exclude items with low stock.

Start with a single condition and check the number of products after generation. If you build a complex chain of five rules right away, it becomes hard to understand why half the catalog disappeared. In Manage Feeds, check the product count after generation and open the file. If the count is too low, temporarily disable the conditions one by one and regenerate the feed.

Category Mapping for Channel Requirements

WooCommerce categories are often written for shoppers and store navigation: "New Arrivals," "Gifts," "Sale," "Home & Comfort." A channel, however, may expect a category from its own taxonomy. Category mapping connects your store categories to the channel's categories. CTX Feed documentation describes the process through CTX Feed, Category Mapping, merchant selection, mapping name, and category matching, after which you need to clear the cache and select the mapping in the category attribute row.

For Google, it is useful to check against the official taxonomy. If there is no exact category match, do not force a random near-match just to fill the field. It is better to choose a broader but accurate level, or rely on automatic classification where that is supported and where the product titles and descriptions genuinely explain the item well.

Dynamic Attributes: When a Standard WooCommerce Field Is Not Enough

A dynamic attribute in CTX Feed Pro is a rule that returns a value based on product data. In WebAppick's official documentation, this mechanism is described as a way to generate custom labels, availability text, category overrides, title modifications, and other values through conditions. This is one of the most product-specific capabilities in CTX Feed Pro because it solves the problem of inconsistent data without forcing you to edit every product page manually.

Example: Fallback Description

Suppose an advertising channel must receive a product description, but in your store some products have only a short description while others have only the full description. WebAppick documents a scenario called "If Field A is Empty Then Get B": if the first field is empty, the plugin takes the second one. In practice, that means you can create a dynamic attribute such as DA_Description, using short description as the primary source and description as the fallback.

After saving the dynamic attribute, it is important to clear the plugin cache. The documentation specifically warns that without a cache clear, the new attribute may not appear in the dropdown when mapping fields. Then in the feed table, you need to select the created attribute from the dynamic attributes group, save the feed, and regenerate the file.

Example: Custom Label for Ad Segmentation

Custom labels are useful when a marketer wants to segment products by price, margin, season, sale status, or inventory condition. For example, products below a certain threshold might receive the value "budget," more expensive items "premium," and low-stock products a separate label for more cautious promotion. In CTX Feed Pro, this can be done with dynamic attribute conditions, and the resulting value can then be output to the channel's target attribute.

The key point here is not to confuse dynamic attributes with optimization magic. The plugin does not know your margins, seasonality, or ad strategy. It only executes the conditions you define. So first think through the business logic, then configure the rule, and only after that connect it to the feed.

A Safe Validation Order for a Dynamic Attribute

1. Create the rule on a small, well-understood set of products.
2. Set a default value so products with no match do not end up with an empty field.
3. Clear the CTX Feed cache after saving the rule.
4. Select the dynamic attribute in the row for the target feed field.
5. Generate the file and locate 3 to 5 products that should fall into different conditions.
6. If the value is empty, check the original WooCommerce fields and the default value.

Auto Updates, Cron, and Cache: How to Keep the Feed Current

Generating a feed once is not enough. Price, stock, promotions, availability, and descriptions change, while the ad channel keeps reading the same URL. If the file does not update, or the channel keeps pulling an old version, shoppers will see incorrect data. In CTX Feed, update management is handled in Manage Feeds, where you can regenerate the file manually, enable auto update, and choose an update interval.

How to Choose an Interval

In WebAppick's documentation, the free version includes intervals such as 1 hour, 6 hours, 12 hours, 24 hours, and 1 week, while Pro adds shorter intervals. The documentation also gives a cautious recommendation not to use an unnecessarily short interval because constant regeneration can increase server load. For a stable catalog, 12 or 24 hours is often enough. For a store with frequent stock, discount, or price changes, a shorter interval may make sense, but first you need to test the load and generation time.

If the catalog is large, do not start with the most aggressive schedule. First measure how long a manual regeneration takes, whether actions in the table stop responding, whether the process hangs, and whether your hosting load increases. If the feed takes a long time to build, running it too frequently can overlap with the next run or interfere with the store's normal operation.

WP-Cron and Server Cron

WordPress cron does not run like a system scheduler. It is triggered by site visits. On a live store, that often works well enough, but on a low-traffic site or during overnight hours, updates may be delayed. WebAppick recommends checking WP-Cron status in CTX Feed, Status, and using server cron or a third-party service if needed. Any changes to wp-config.php or server schedules should be made only by someone who understands the site's infrastructure and can roll the change back safely.

Cache and the Feed Directory

The generated file is usually stored in the WordPress uploads directory. Feed management documentation gives a path like /wp-content/uploads/woo-feed/[format]/[feed-name].[ext]. If a caching plugin, CDN, or server cache keeps serving the old file, CTX Feed may already have generated the new price, but Merchant Center will still see the old value. In WebAppick support guidance for outdated feeds, the recommended process is to open the URL in a private window, find the product by ID, regenerate the feed manually, verify the new file, exclude the feed directory from cache, and then fetch the file again in the external platform.

Quick freshness check: change the price of a test product, regenerate the feed, open the URL in a private window, and find that product by ID. If the price did not change in the file, the issue is on the generation or site cache side. If the file is correct but the channel still sees the old value, check the fetch schedule inside the channel itself.

Practical Scenario: A Google Shopping Feed for Part of the Catalog

Let us walk through a concrete scenario that fits most WooCommerce stores: preparing a Google Shopping feed only for published products with an image, a price, and a clear description, mapping categories, handling variable products correctly, and getting a URL ready for Merchant Center.

Goal

The result should be an XML feed for the store's main country. It should include only products that can be advertised without obvious issues: the product is published, available, has a price, an image, and a description. Variations should be represented in a way that keeps price, size, color, and availability aligned with the actual purchasable options. Store categories should be connected to Google categories where that improves classification.

Preparation

Before setup, review 10 to 20 products: a simple product, a variable product, a discounted product, an out-of-stock product, a product with multiple images, and a product from each important category. Note where brand, GTIN, or MPN data is stored, if those values exist. If identifiers are missing, do not invent them for the feed. It is better to leave a field empty or use the correct channel rule than to send a random value.

Setup Steps

1. Go to CTX Feed and Make Feed.
2. Select the country that matches your target market and shipping settings.
3. Choose Google Shopping or another Google template that fits your use case.
4. Select XML if the channel and your review workflow are built around a structured file.
5. Give the file a clear name, such as google-main-catalog.
6. Set the variation mode based on the store structure: all variations for products where exact sizes and colors matter, or parent if you are advertising the general product page.
7. Review the attribute rows: title, description, link, image link, price, availability, brand, GTIN, MPN, category, and shipping.
8. Enable filters against empty descriptions, images, and prices if those products should not appear in ads.
9. Create category mapping for your key categories and clear the CTX Feed cache.
10. Save the settings and click Update and Generate Feed.

Validating the Result

Open Manage Feeds, locate the created feed, open the URL through the view action, and inspect the file. Find several products by SKU or ID. Make sure the title does not contain stray service characters, the description is cleaned of unnecessary HTML, the link leads to the correct page, the image opens without login, the price matches the public product page, availability does not conflict with WooCommerce, and variations do not lose important attributes.

Then save the feed URL and add it to the external channel only after the internal review is complete. If the channel supports scheduled fetch, set the timing so it does not conflict with regeneration on the WordPress side. For example, if CTX Feed updates the file overnight, the external channel should fetch the URL after that, not a few minutes before the refresh.

The Detail People Often Miss

If the value you need does not appear in a dropdown after configuring category mapping or dynamic attributes, clear the CTX Feed cache first. This point comes up repeatedly in WebAppick documentation and related comments. Do not reinstall the plugin or rebuild the feed from scratch until you have checked the cache, source fields, and file regeneration.

Feed Quality Checks Before Connecting It to a Channel

Before you submit the URL to an ad account, run a separate quality check. It should not be a formality. Feed errors often cost more than the initial setup itself: ads do not launch, products get disapproved, campaigns spend budget on unprofitable items, or reporting becomes fragmented across the wrong variations.

What to Look For in the File

• Product count. It should match the logic of your selected filters. If you expected 800 products and got 120, look for an overly strict filter or a problem in the query settings.
• Prices and availability. Compare the file with the public product page, especially for discounts, variations, and low-stock products.
• Images. Open several image URLs. They should be accessible without logging into WordPress and should not point to a thumbnail instead of the main image.
• Categories. Check that category mapping is actually applied to the right categories, not just saved in a separate section.
• Description. Make sure it does not contain shortcodes, leftover HTML clutter, ad insertions, or empty values where the channel expects a description.
• UTM parameters. If you use Campaign URL Builder, make sure the parameters are added only to the intended links and do not break the product URL.

Cross-Checking with Merchant Center or Another Platform

After uploading the URL to the external channel, do not look only at the overall status. Open the list of errors and warnings for individual products. Google Merchant Center, for example, shows diagnostics for attribute issues, images, identifiers, and landing page mismatches. If the same error repeats across many products, do not fix it manually inside the platform. It is better to return to CTX Feed Pro and adjust the mapping, filter, output type, or dynamic attribute so the fix is systematic.

Pay especially close attention to warnings such as "missing required attribute," "incorrect value," "image not crawlable," "price mismatch," and similar messages. They almost always point to a specific part of the chain: the original WooCommerce data, the transformation in the feed, cache, update timing, or channel requirements.

Safe Improvements Without Editing Plugin Code

With CTX Feed Pro, you do not need to start with PHP snippets. Most tasks can be solved through settings, filters, dynamic attributes, output type, string replace, category mapping, and the update schedule. You should not modify the plugin core, WooCommerce files, or the theme template just for the feed: updates will overwrite those changes, and one mistake can break the store.

Improvement 1: A Separate Test Feed

Create a copy of the working feed using duplicate and give it a clear name, for example google-test-filtered. Use that copy to test new filters, dynamic attributes, and category mapping. Once the checks are successful, move the changes into the main feed. This is much safer than editing the only URL that is already connected to an ad account.

Improvement 2: Export the Configuration Before Major Changes

In Manage Feeds, you can export the configuration to a .wpf file. Use that before deleting a feed, making large edits, or moving settings to another site. WebAppick's documentation explicitly warns that deleting a feed removes both the configuration and the generated file, and there is no undo. Exporting gives you a simple restore point without touching the database.

Improvement 3: Exclude the Feed Directory from Cache

If the site uses a caching plugin, CDN, or server cache, add an exclusion rule for the feed directory. Do this in the cache plugin interface or at the server level together with the site administrator. After the change, clear cache, regenerate the feed manually, and check the URL in a private window. Rolling it back is simple: remove the exclusion rule and restore the previous cache configuration.

No code is needed here. The official sources provide enough interface-based actions, and a universal PHP snippet for every store would be risky because different hosts, caching plugins, CDNs, and uploads structures require different solutions.

Product Video

For a clearer visual explanation, WebAppick's official video on dynamic attributes is worth watching. It is specifically about CTX Feed and demonstrates a workflow that is often harder to grasp from text alone: creating a conditional value, clearing cache, selecting the dynamic attribute in mapping, and verifying the result in the feed. It directly addresses questions such as "how to set up a dynamic attribute in CTX Feed Pro" and "how to use a fallback field in a WooCommerce feed."

When CTX Feed Pro Is a Strong Choice

CTX Feed Pro is worth using if a feed is not a one-time export for you, but an ongoing part of WooCommerce store marketing. The plugin is especially useful when you need to manage multiple channels, different formats, variations, filters, category mapping, dynamic attributes, automatic updates, and generation logs.

Before going live, do not stop at the fact that the file was created. Review the source products, set up the first feed on a small product group, compare the values against the public product page, exclude incomplete items, verify category mapping, clear cache after adding new rules, and make sure the update schedule actually works. That approach reduces the risk of errors once the feed reaches the ad platform.

If that workflow matches your needs, you can download the ZIP archive, install it on a test site or staging copy, and walk through the process described here using real products. The best decision criterion is not the feature list on the product page, but a verified feed that opens correctly, updates reliably, and passes diagnostics in the channel you actually plan to use.