TikTok Marketing Suite for Magento 2





All-in-One TikTok Integration for Magento 2
The TikTok Marketing Suite for Magento 2 helps you take full advantage of TikTok’s growing commerce platform. Designed for merchants who want to reach new audiences and boost conversions, this extension lets you easily connect your Magento store with TikTok’s marketing ecosystem.
Create a ready-to-use TikTok Product Feed directly from your Magento backend, fully optimized for TikTok Ads and Catalogs. Capture every key event with the TikTok Conversion API, including purchases, add-to-cart, and checkout initiations — all tracked with precision even when browser cookies are restricted.
Built for both marketers and developers, this lightweight suite provides powerful automation without unnecessary complexity. And with upcoming support for TikTok Shop integration, your products will soon be ready to sell directly on TikTok.
Effortless TikTok Integration
Create your TikTok Product Feed in minutes using our simple Magento admin interface, no coding, no manual setup required. Sync your catalog effortlessly and get your products ready for TikTok Ads and Catalogs out of the box.
Lightweight, Purpose-Built for TikTok Commerce
Keep things simple and powerful. This module is built specifically for TikTok marketing, tracking, and conversions, only the features you need, without unnecessary complexity.

Create a Feed

Set the TrackingPixel

Start Selling


Automatically Generate a TikTok-Ready Product Feed from Magento 2
The TikTok Marketing Suite makes it incredibly easy to generate a structured, TikTok-compliant product feed directly from your Magento 2 store. With just a few clicks, your entire catalog is converted into a clean, optimized feed — ready for TikTok Ads Manager or Catalog upload.
This feed includes all key product attributes such as name, description, price, stock status, and image URLs. Each product link is automatically formatted to meet TikTok’s requirements, ensuring that your catalog stays accurate, up-to-date, and fully compatible with TikTok’s advertising and shopping tools.
Whether you’re running dynamic TikTok Ads or preparing for future TikTok Shop integrations, this setup guarantees your listings are properly structured, discoverable, and easy to maintain — without any custom development required.
You can include or exclude specific categories, products, or stock rules to customize the feed output as needed. The result: a flexible, fast, and reliable TikTok Product Feed built for visibility and performance.
Track and Optimize with TikTok Pixel and Conversion API for Magento 2
Combine the TikTok Pixel and TikTok Conversion API to achieve accurate, privacy-compliant tracking in your Magento 2 store. This dual setup collects conversion data from both the browser and your server, improving ad performance, attribution accuracy, and campaign optimization across TikTok.
The TikTok Pixel can be enabled directly from the Magento admin. Simply enter your Pixel ID and select key events like PageView, AddToCart, InitiateCheckout, and Purchase. No coding required — just precise tracking of every step in the customer journey.
The Conversion API sends the same events server-side using your Access Token, ensuring consistent event delivery even when browser tracking is limited. This improves data quality and gives TikTok better insight into how customers interact with your store.
By combining both tools, your TikTok campaigns benefit from more complete data, smarter optimization, and deeper visibility into customer behavior — all managed natively within Magento 2.


Unlock New Growth by Connecting Your Magento 2 Store to TikTok
Reach millions of active TikTok users and turn viral content into real sales. The TikTok Marketing Suite for Magento 2 brings your products directly into the heart of one of the most engaging platforms online — where discovery and shopping naturally go hand in hand.
With an integrated product feed, conversion tracking, and upcoming TikTok Shop support, your Magento store becomes a seamless part of TikTok’s commerce ecosystem. Every product, price, and inventory update is automatically synced, ensuring your ads and product listings are always accurate and ready to perform.
Unlike traditional ad channels, TikTok connects storytelling with shopping — inspiring audiences through authentic, creative content. By linking your Magento store, you empower your brand to appear where buying decisions are made in real time, driven by trends, creators, and community engagement.
Stay ahead of competitors with a future-ready integration built to grow alongside TikTok’s expanding eCommerce tools. From product visibility to performance insights, your store is ready to meet customers where they’re already spending time.
Comprehensive TikTok Data Tracking Pipeline for Magento 2
Combine the TikTok Pixel and TikTok Conversions API to achieve complete and reliable tracking in your Magento 2 store. The Pixel tracks browser-side events, while the Conversions API sends server-side events for improved accuracy, attribution, and campaign optimization.
The TikTok Pixel loads automatically on the storefront and captures key events such as PageView, ViewContent, AddToCart, InitiateCheckout, and Purchase.
The Conversions API mirrors these events from the server, including hashed user information, product data, and cart values. This ensures tracking continues even when browser limitations prevent Pixel firing.
All events are configurable in the Magento admin. User data is hashed for GDPR compliance, validated before sending, and transmitted only when required.
Below is an overview of all supported Pixel and Conversions API events.
Frontend Events (TikTok Pixel)
Frontend events are tracked client-side using the official TikTok Pixel JavaScript library and fire directly in the browser whenever customers interact with your Magento 2 store.
| Event Name | Trigger | Description | Data Tracked |
|---|---|---|---|
| PageView | Every page load | Automatic page view tracking | Page URL, referrer |
| ViewContent | Product page view | When a customer views a product | Product ID, name, price, currency, category |
| AddToCart | Add to cart button click | When a customer adds a product to cart | Product ID, name, price, quantity, currency |
| ViewCart | Cart page view | When a customer views their cart | Cart contents, total value, currency |
| InitiateCheckout | Checkout page load | When a customer starts checkout | Cart contents, total value, currency |
| AddToWishlist | Wishlist page view | When a customer views wishlist | Wishlist contents, total value, currency |
| Search | Search results page | Product search performed | Search query |
| CompleteRegistration | Registration success | New account created | - |
| Purchase | Order success page | When a customer completes a purchase | Order ID, products, revenue, currency |
Backend Events (TikTok Conversions API)
Backend events are sent server-side through the TikTok Conversions API, providing more reliable tracking and filling gaps when browser-based Pixel events are blocked or lost.
| Event Name | Trigger | Description | Data Tracked |
|---|---|---|---|
| ViewContent | Product page view | When a customer views a product (server-side) | Product ID, name, price, user data (email hash, IP, user agent, _ttp) |
| AddToCart | Product added to cart | When a customer adds a product to cart (server-side) | Product ID, name, price, quantity, user data |
| AddToWishlist | Product added to wishlist | When a customer adds to wishlist | Product ID, name, price, user data |
| Search | Search results page | When a customer performs a product search (server-side) | Search query, user data |
| InitiateCheckout | Checkout page load | When a customer starts checkout (server-side) | Cart contents, total value, user data |
| AddPaymentInfo | Checkout payment step | When a customer adds payment information | User data, cart value |
| CompleteRegistration | Registration success | When a customer creates an account (server-side) | Email hash, customer ID, user data |
| Subscribe | Newsletter subscription | When a customer subscribes to the newsletter | Email hash, user data |
| Lead | Contact form submission | When a customer submits the contact form | Email, name, message content, user data |
| Purchase | Order placed | When a customer places an order (server-side) | Order ID, products, revenue, tax, shipping, user data |
User Data Tracking
For GDPR compliance, the extension tracks and hashes the following user data:
- Email: SHA-256 hashed
- Phone: SHA-256 hashed (normalized to digits only)
- IP Address: Collected from the request
- User Agent: Browser and device information
- External ID: SHA-256 hashed customer ID for logged-in users
- TikTok Click ID (ttclid): Captured from the URL parameter
- TikTok Pixel Cookie (_ttp): Captured from the TikTok Pixel cookie
- All tracked data is validated to a maximum length of 255 characters
- User data is only sent when related events are triggered
- Customer email and phone are automatically hashed before transmission
- No sensitive payment information is transmitted
Complete Frontend Implementation
- Uses the official TikTok Pixel JavaScript library
- Lazy-loaded for optimal performance
- Event data integrated directly into the page context
- Supports multiple checkout implementations
Reliable Backend Implementation
- Queue-based processing for reliability
- Automatic retry mechanism for failed events
- Captures tracking data during quote save
- Preserves user session data across checkout
- Supports both guest and registered customers
Knowledgebase
All familiar Help articles
A list of the most frequently asked questions from the TikTok Marketing Suite extension for . We've tried our best to help you with the installation, configuration and troubleshooting. If you do not find the answer you were looking for, you can always send us a message through this form.
Changelog 1.2.0 is released on 3 November 2026
Our plugins are regularly updated to ensure compatibility with the latest Magento release.
-
Features:
- Events API batching: the queued events of a store view go out together, up to 100 per request, and a rejected batch is retried event by event so one invalid event does not hold back the rest.
- New events ViewCategory, on the category page, and CustomizeProduct, on the first option chosen on a product page, for the Pixel and the Events API with a shared event id.
- Exclude Customer Groups: no Pixel and no Events API events for customers in the selected groups; NOT LOGGED IN excludes guests.
- Event names follow TikTok's May 2025 renames (CompletePayment to Purchase, SubmitForm to Lead); the old names are mapped to the new ones in the configuration and in `window.mmTikTokPixel.track()`.
- Catalog API: register the feed of each store view with a TikTok catalog for an hourly or daily fetch, see the result of the last fetch in the Feeds table, and unregister; with a button to test the credentials.
- Hooks for headless storefronts: consent and visitor data can be set per request.
- Consent mode: the Pixel holds events and the Events API skips them until consent is given, based on Magento's Cookie Restriction Mode or a consent tool's cookie. Off by default.
- Advanced Matching: the Pixel identifies customers with a hashed e-mail, phone and customer id, and the Events API adds hashed name and postcode plus city, state and country. A separate setting under Pixel and under Events API, on by default.
- Limited Data Use setting for the Events API.
- Self-test in the configuration header: PHP and Magento version, extension status, cron and Catalog API credentials.
- New "Use Parent Category for Simples" setting for configurable, bundle and grouped products: a simple without categories of its own takes the parent's.
- New "Parent Price" setting for configurable products: the configurable's own price, or the lowest or highest price of its variants.
- Product weights stored in grams or ounces are converted to kilograms or pounds in the feed. A new setting under Advanced says which unit the catalogue keeps.
- Generating a feed from the configuration page shows a progress bar. The run happens in the background while the row reports how many products have been written, the row says when it finished, and the page keeps its state. Improvements:
- The content id follows the feed wherever the chosen variant is known: the variant when only the linked simple products are exported, the configurable otherwise, so the cart events, the purchase and the server-side events all name the same catalogue item. A pixel event on a product page still reports that page's product, because no variant has been chosen yet.
- A product with no GTIN attribute mapped sends none. The default was the SKU, which is never a valid GTIN, so every item carried one the channel rejects; a shop that mapped a real GTIN keeps its setting.
- Feed generation reports how many products were written without a brand, and where to map the attribute. TikTok requires brand, and the feed leaves it empty rather than inventing one.
- Every feed item carries its product id as sku_id as well, the name TikTok's catalog parameters use; id stays for readers of the Google Shopping vocabulary.
- The Purchase event carries the order number as `order_id`, in the Pixel and in the Events API.
- AddPaymentInfo is no longer offered as a Pixel event: the Pixel has no payment step to fire it on, so selecting it did nothing. The Events API keeps sending it when a payment method is saved.
- Every product event of the Pixel carries `contents` with TikTok's field names: `content_id`, `content_type`, `content_name`, `quantity` and `price`, built by the same code as the Events API. The Pixel used Meta's `id` and `item_price`, which TikTok does not read.
- ViewContent on a configurable, bundle or grouped product reports the parent as one content under the id the feed carries, where it listed every child. The children of a cart or order are still reported as bought.
- The feed's product data and post-processing run on the shared drop-in that the other feed modules use; what differs per channel is passed in at the call site.
- Multi-store: product and image URLs use the base URL of each store view, and the feed settings are read per store view instead of from the first store generated.
- Product descriptions are cleaned the way the other feed modules clean them: list items become "- " with a line break, a closing paragraph a blank line, and Magento directives and style blocks are dropped.
- The "Only Parent Products" filter applies to configurable, bundle and grouped products.
- An image path that is already a full URL is used as it is.
- A configurable parent carries no `item_group_id`; only its variants do, all under the parent SKU.
- A product that is not visible individually and has no parent is left out only when the visibility filter is on and "Not Visible Individually" is not among the selected visibilities.
- "Use Default" is available on all 97 website- and store-scoped settings.
- The cron schedule lives in the field the administrator edits.
- The admin header logo comes from the Magmodules CDN for the extension and version, and the support link from composer.json.
- Three dead settings are gone, and `composer.json` states Magento 2.4 and PHP 8.1. Bugfixes:
- The cart and checkout events report the quantity the shopper chose and the price including tax, taken from the line they see. A configurable reported one item at the net price while the purchase of the same order reported three at the gross price.
- Add to cart reports the quantity the shopper chose. The payload is rendered with the page, before that choice exists, and always said one.
- The Purchase event reports the item prices in the order currency and including tax, like its grand total. The Pixel mixed the base currency price with the order currency total; the Events API sent the price excluding tax.
- The Search event carries the query as `query` and as `search_string`, in the Pixel and in the Events API; TikTok documents one name for each and the Pixel sent only the Events API name.
- The Pixel identifies a visitor once per page; the same customer data from the page, the cached customer section and its reload was passed to `ttq.identify()` up to three times.
- The Pixel sends `value` and item prices as numbers, where it sent them as text, which TikTok does not count as a value.
- Product links in the feed carry the store code when "Add Store Code to Urls" is on. Without it every link of a non-default store view opened the default store.
- A field left empty after post-processing, such as product_type with "Include Product Type" off, is no longer written as an empty element on every item.
- Children of a bundle or grouped product no longer receive the parent's SKU as item_group_id; only a configurable's variants form a group.
- Phone numbers are hashed in E.164 format, as TikTok requires.
- The Pixel and the Events API send the same event id, so TikTok deduplicates events instead of counting them twice.
- The InitiateCheckout Pixel event fires on Hyvä Checkout.
- ViewContent and Search reach the Events API for pages served from the full page cache.
- CompleteRegistration and AddToWishlist fire for the actual registration and the added product.
- The AddToCart Pixel event follows the Pixel events setting.
- AddToCart, InitiateCheckout and AddPaymentInfo report the child as content_id, where they reported the configurable parent.
- The AddPaymentInfo event of a guest carries the e-mail address from the payment step.
- The Shipping Prices table reaches the feed and produces the shipping node per item, and a comma decimal is accepted when the rows are saved.
- An empty category attribute falls back to the default category.
- Parents set to No or Only Linked Simple Products are left out when none of their children are included.
- The category filter leaves out a product in an excluded category, also when it sits in another category as well.
- A product with no price of its own keeps its own price. In a batch it could be published with the price of whichever product came before it.
- A catalog rule price is kept for a product without a final price.
- The feed grid mass delete removes the selected feeds; a select-all could remove every feed.
- The feed and queue grid mass actions answer a request without a selection with the message explaining that nothing was selected.
- The feed cleanup reports how many feed files and records it removed and how old they had to be.
- The feed's channel no longer carries a `result` element with the product count and run time; that run report is in the Feeds table and the log.
- Feed generation is on out of the box, and the generate-feed command reports a failure when the module or the feed is disabled for the requested store.
- Feed generation completes on PHP 8.5 for configurable children without a value for the super attribute, and a malformed attribute condition is skipped.
- The admin reports the installed version; it read a value in `config.xml` that no release updated and stayed on 1.1.0.
- The Debug Mode switch takes effect, and Include Item Group Id has a setting of its own.
- The self-test and version-check screens require the module's own permission, so access can be granted per admin role.
- A media URL is resolved per store view; one cron run over several stores gave every later store the first store's image links.
- An image stored as an absolute URL keeps that URL.
- HTML entities in catalogue text are decoded before the feed is written, so the feed stays well-formed XML.
- The UTM code is placed before a fragment in the product link, where it used to end up after the anchor.
- The feed file name is validated to a plain name so it cannot leave the feed directory.
- AJAX responses in the admin modals are escaped, and the changelog from the version host is reduced to its text formatting tags.
- The attribute mapper handles an empty result.
- The CLI documentation names the commands the module actually registers. Tests:
- An end-to-end spec for the chosen quantity on add to cart, including a quantity field attached to the form from outside it, the shape Hyva's product page builds.
- TikTok's catalog product parameters are pinned in `Test/spec/tiktok-feed-spec.json`, with the source and the date; a unit test checks every field name the feed can write against it.
- An end-to-end test generates the feed with "Add Store Code to Urls" on and checks every link; unit tests pin the store code in rewrite and fallback links, that an empty field writes no element, and that only configurable parents form an item group.
- The baseline end-to-end layer: everything on, everything off, every grid, every admin route. Every configuration section opened and saved, the dynamic-rows tables round-tripped, the feed grid actions, the Pixel and the Events API on the storefront, on Magento 2.4.7 and 2.4.9.
- Fifteen architecture tests pin what the code does not show on its own: Api interfaces against their di.xml preferences, data patches, cron wiring, every `config.xml` default against a declared admin field, and every website- and store-scoped field against `canRestore`. PHPStan runs at level 8 without a baseline. Compatibility:
- Magento 2.4.x and up
- PHP 8.1 and up
-
Features:
- Added option to add "Test Event Code" for better testing Bugfixes:
- Fixed issue with incorrect naming for availability in feed
- Added fallback to 1 if currency exchange is not set in feed Minimum requirements:
- Magento 2.3.x & PHP 7.4
-
Improvements:
- Added additional domains to the CSP list Minimum requirements:
- Magento 2.3.x & PHP 7.4
-
Features:
- TikTok Marketing Suite Minimum requirements:
- Magento 2.3.x & PHP 7.4
100% Unencrypted Code quality guaranteed.

Adobe Commerce Marketplace Approved
This extension is listed on the official Adobe Commerce Marketplace and has passed their review process for code quality, performance and security.
Adobe Marketplace approval means the extension follows Magento coding standards and integrates properly with the platform. Updates go through the same review process.

Hyvä Compatible Plugin
This extension includes full support for Hyva Themes. All frontend components, widgets and templates work natively with Hyva's Alpine.js and Tailwind CSS stack.
The extension works out of the box on Hyva and is tested with every new Hyva release to ensure continued compatibility.

GraphQL Made Ready
This extension exposes its data and configuration through Magento's GraphQL API. You can query and mutate data directly from headless frontends or custom applications.
The GraphQL schema follows Magento's conventions and covers all key functionality of the extension. This makes it ready for PWA Studio, Vue Storefront or any other headless setup.

Magento Cloud Support
This extension is fully compatible with Adobe Commerce Cloud (Magento Cloud). It works with the read-only filesystem, the build and deploy pipeline and cloud-specific caching layers.
No additional configuration or workarounds are needed for cloud environments. The extension handles static content deployment and config management the same way as on-premise installations.

Private Composer Repo
After purchase you get access to a private Composer repository with personal credentials. Install and update the extension with a single composer command, just like any other dependency.
Your Composer credentials are available in your account dashboard. Updates are published to the repository as soon as a new version is released, so you always have access to the latest version.
Playwright E2E Tests (102)
This extension is covered by 102 end-to-end tests using Playwright. These tests run automatically on every code change through our CI/CD pipeline.
The tests simulate real user interactions across checkout flows, configuration changes and edge cases to make sure everything works before every release.