Send Clang the products worth showing.

Clang is the original name of what is now called Deployteq, a Dutch marketing automation and email platform. The company rebranded from Clang (and, before that, CanopyDeploy) to Deployteq, but the "Clang" name still appears in technical artifacts that remain in active use — most notably the clang/module-clang Magento 2 extension, a free module with over 34,000 installs on Packagist that connects a Magento or Adobe Commerce store to the Deployteq platform for order and customer data sync.

In practice, when a store owner or agency refers to "the Clang integration," they almost always mean connecting their store to Deployteq's marketing automation and email suite — not a separate shopping feed destination like a comparison shopping engine or ad network.

Deployteq uses product and order data to power triggered and personalized email campaigns: abandoned-cart reminders, back-in-stock alerts, cross-sell and upsell blocks, and post-purchase follow-ups. The Magento module syncs order data directly from the store so these campaigns can reference real products, prices and images without manual template edits.

Feeding accurate, current product data into Deployteq — through the Magento connector or a feed shared with your implementation partner — keeps the dynamic content blocks it generates inside an email (recommended products, recently viewed items, personalized modules) aligned with what is actually in stock and correctly priced on the storefront.

Deployteq does not publish a single, fixed feed specification the way a comparison shopping engine or ad network does. For Magento and Adobe Commerce stores, the primary integration path is the clang/module-clang extension, which syncs order data directly from the Magento database rather than reading an external XML or CSV feed file.

Where Deployteq's dynamic content / feed-driven product blocks are used inside an email template, the underlying data is typically supplied as a structured feed that the template or a connected personalization partner pulls from at send time. Deployteq has not published a required file format, field list, or size limit for this publicly, so none is stated here — treat the exact format as something to confirm case by case with Deployteq or your implementation partner rather than a documented public standard.

Because Clang/Deployteq does not expose a standard, publicly documented self-serve feed endpoint, Feedance treats it as a custom destination:

1. Build a clean product feed in Feedance with the core fields most email personalization use cases need: product ID or SKU, title, price, availability, image URL and product page URL.
2. Export it as a hosted feed URL in the format your Deployteq implementation or connected recommendation partner asks for (XML, CSV or JSON).
3. Share the feed URL with your Deployteq account manager or implementation partner so it can be wired into the relevant dynamic content or feed touchpoint in your email templates.
4. If you run Magento or Adobe Commerce, remember the clang/module-clang extension syncs order and customer data separately from any product feed — the two integration paths are independent and may each need their own setup.

Since Deployteq does not publish a self-serve feed spec, confirm the exact format and field names with Deployteq support before finalizing the connection.

Deployteq has not published an official minimum or recommended refresh interval for feed-driven email content. As a general practice for feed-driven personalization, refreshing at least daily is usually enough to keep prices, stock status and promotions accurate for triggered campaigns such as abandoned-cart and back-in-stock emails. Stores with frequent price or inventory changes may want a more frequent refresh; confirm the practical cadence with your Deployteq implementation contact, since it depends on how the feed is wired into your specific templates.

These are general best practices for feed-driven email content, not confirmed Deployteq requirements:

1. Keep product titles and images in the feed consistent with what shoppers see on your storefront and at checkout, since mismatches undermine trust in triggered emails.
2. Exclude out-of-stock or discontinued products from any feed used for recommendation blocks so customers aren't shown items they can't buy.
3. Use stable, absolute image and product URLs so email clients that cache or prefetch content don't break personalized blocks.
4. Coordinate feed refresh timing with your email send schedule so price drops or promotions are reflected before campaigns go out.

Is Clang the same company as Deployteq? Yes. Deployteq is the current name of the company previously known as Clang (and, earlier, CanopyDeploy). The "Clang" name survives mainly in the Magento extension package name, clang/module-clang.

Does Feedance push data directly into Clang/Deployteq? Feedance can generate a hosted product feed formatted for email personalization use cases. Wiring that feed into Deployteq's templates or dynamic content blocks currently requires coordination with Deployteq or an implementation partner, since Deployteq does not publish a self-serve feed import.

Is this the same as the Magento order-sync module? No. The Magento module syncs order and customer data into Deployteq to power campaign triggers; a product feed for recommendation content inside emails is a separate data flow.

Clang is the former name of Deployteq, a Dutch marketing automation and email platform used by online retailers and other brands to run personalized customer communication. The company was previously known as CanopyDeploy and then Clang before rebranding to Deployteq, but the Clang name is still used in technical integrations such as its Magento 2 extension.

Deployteq is not a marketplace or a comparison shopping site. Instead, it uses customer, order and product data to power triggered and personalized campaigns: abandoned-cart reminders, back-in-stock alerts, cross-sell and upsell blocks, and post-purchase follow-ups sent by email and other channels.

For Magento and Adobe Commerce stores, the main connection runs through the Clang module, which syncs orders and customers with the platform. Deployteq does not publish a single standard product feed specification, so product data for email content is usually delivered as a custom feed agreed during setup.

Feed quality matters because the products in these messages are what customers click on. Outdated prices, broken links, missing images or items that are no longer in stock make personalized emails look unreliable and cost conversions. A clean, regularly refreshed product feed keeps the content in Deployteq campaigns consistent with what shoppers see in your store.