Matomo and Google Ads: how to track campaigns, conversions, and Tag Manager in PrestaShop

Integrating Matomo into Google Ads campaigns allows you to analyze user behavior with greater control over data, especially when managing a PrestaShop ecommerce and you want to measure visits, orders, carts, and traffic sources clearly.

Tecnoacquisti.com® develops solutions to help merchants, agencies, and companies make the purchase journey more readable. In this guide, we see how to use Matomo together with Google Ads, how to configure campaign tracking, how to manage conversions, and how to set up Matomo Tag Manager to centralize tags without burdening daily work.

Why use Matomo together with Google Ads

Google Ads is the tool with which you create campaigns, ads, and bidding strategies. Matomo, instead, helps you analyze what happens after the click: pages visited, products viewed, carts started, orders completed, and traffic quality. Using both in a coordinated way allows you to make more solid decisions about campaigns.

For a PrestaShop ecommerce, Matomo can be useful because it offers an independent, configurable analytics environment oriented towards data ownership. If you want to integrate the tracking code simply, you can consider the Matomo Analytics for PrestaShop with ecommerce tracking module, designed to add Matomo to the store and enable ecommerce monitoring.

The main difference to keep in mind is this: Matomo helps you measure and analyze; Google Ads needs conversions correctly sent or imported to optimize campaigns and bidding. The operational connection between the two worlds must therefore be carefully designed.

Tracking Google Ads campaigns in Matomo

The first step is to ensure that Matomo correctly recognizes traffic coming from Google Ads. In many cases, Google Ads automatically adds the gclid parameter to destination URLs if auto-tagging is enabled. Matomo can detect visits coming from Google, but to have more readable reports it is advisable to also use consistent UTM parameters.

Recommended parameters for campaign URLs

When building final URLs or tracking templates, you can use parameters such as:

• utm_source=google: identifies Google as the traffic source.
• utm_medium=cpc: indicates that the visit comes from paid traffic.
• utm_campaign: reports the campaign name, useful for comparing performance and budget.
• utm_content: distinguishes ad variants, groups, or assets.
• utm_term: can be used for keywords or targeting criteria, when available.

A well-ordered URL helps Matomo better classify visits and makes it easier to analyze which campaigns generate useful sessions, viewed products, cart additions, and orders. The goal is not to collect as much data as possible, but to collect consistent and comparable data.

Configuring Matomo on PrestaShop

Before working on conversions, basic tracking must be stable. The Matomo code must be present on relevant store pages, including the order confirmation page, and ecommerce tracking must be configured to record carts, products, and transactions.

With the Matomo Analytics for PrestaShop with ecommerce tracking module, you can simplify the insertion of the tracking code and make the integration with your PrestaShop ecommerce tidier. This approach reduces the risk of tags manually inserted in incorrect theme points or modifications difficult to maintain after updates.

If your project also uses Google Analytics 4, for example for reports requested by the marketing team or agency, you can use different tools side by side while maintaining clear roles. The PrestaShop Module for GA4 integration allows you to integrate the GA4 tracking tag in a dedicated way, while Matomo can be used as an independent and more controllable analytics platform.

Conversions: what Matomo can do and what Google Ads needs

A conversion, in practice, is a valuable action: a completed order, a contact request, a registration, a download, or an event related to the sales funnel. In Matomo you can measure these goals as goals or ecommerce events. In Google Ads, instead, conversions are also used to optimize campaigns and bidding strategies.

It is important to clarify one point: Google Ads does not natively import conversions from Matomo as it does with some direct integrations of the Google ecosystem. To use Matomo conversions in campaigns, you generally have two operational paths:

• Send a conversion to Google Ads via tag: you create a conversion in Google Ads and activate the related tag when the desired action occurs in PrestaShop, for example, order completed.
• Use offline import: you save the gclid associated with the visit and, when the conversion occurs, you send the required data to Google Ads via import or API, respecting format, timing, and consents.

The first solution is often simpler for many ecommerce. The second is more suitable for complex flows, sales that close after days, leads managed by CRM, or manually validated orders.

How to import or send conversions to Google Ads

In operational language, we often talk about importing conversions, but the method depends on the chosen flow. If you want Google Ads to receive the conversion at the time of the order, you must create a conversion action in Google Ads and install the corresponding tag. This tag can also be managed with Matomo Tag Manager, using rules and triggers.

Method 1: Google Ads conversion triggered by Matomo Tag Manager

The typical process is as follows:

1. In Google Ads, open the conversions section and create a new action, for example ecommerce purchase.
2. Copy the conversion tag data, such as conversion ID and conversion label.
3. In Matomo Tag Manager, create a new suitable tag, often via custom HTML or available template.
4. Define a trigger on the order confirmation page or on a specific ecommerce event.
5. Insert any dynamic variables, such as order value, currency, and transaction ID.
6. Test the flow first in preview and then with Google Ads diagnostic tools.

This method allows Google Ads to receive the conversion and Matomo to continue recording the session and user journey. It is a practical solution when checkout ends on a reliable order confirmation page and no duplications are created.

Method 2: offline import with gclid

If the conversion does not happen immediately online, you can work with offline import. In this case, you must capture and store the gclid parameter linked to the visit coming from Google Ads. When the user completes a purchase or a subsequent commercial step, the system must associate the conversion with that gclid and send it to Google Ads.

This flow requires technical attention and proper data management. You must verify consent, import timing, file or API format, time zone, conversion value, and event uniqueness. It is a more advanced configuration but useful when the real value of the conversion is confirmed after the order or when the sales cycle does not end in the web session.

Setting up Matomo Tag Manager for Google Ads campaigns

Matomo Tag Manager is the tool that allows you to manage tags, triggers, and variables from a single panel. Instead of manually inserting different scripts into the PrestaShop theme, you can centralize management and publish changes more controlledly.

Recommended structure

For a PrestaShop ecommerce, we recommend a simple and readable structure:

• Base Matomo tag: records visits and page views.
• Ecommerce tag: sends information about products, cart, and orders when available.
• Google Ads conversion tag: activates only when the order is completed or when the chosen action occurs.
• Variables: collect order value, currency, transaction ID, product category, or other useful data.
• Triggers: define when a tag should fire, for example on order confirmation URL or custom event.

The most important rule is to avoid duplications. If the same purchase event is sent twice to Google Ads, data can be inflated and campaigns can optimize based on incorrect information. For this reason, it is useful to use transaction IDs, precise conditions, and tests before publishing.

Use of ecommerce variables

When the economic value of the conversion is available, sending it to Google Ads helps distinguish a small order from a more important one. In Matomo Tag Manager, you can configure variables that read data present on the page or in the data layer, if the theme or module makes them available.

The most useful variables are:

• Order value: transaction amount, preferably net or gross according to a stable rule.
• Currency: for example EUR.
• Order or transaction ID: useful for deduplication and data verification.
• Event type: purchase, lead, registration, or other relevant action.

If these data are not already available, a technical intervention may be necessary to expose them correctly. In this case, it is advisable to avoid improvised solutions and build tracking consistent with PrestaShop, theme, installed modules, and consent management.

Consent, privacy, and data quality

Every analytics and advertising configuration must respect user choices and the rules applicable to your market. Before activating advertising tags, verify that the cookie banner or consent platform is configured to block or enable tags based on expressed preferences.

Matomo can be configured in different ways, including settings more attentive to privacy. However, when you send conversions to Google Ads or use advertising tags, you must properly manage consent categories. Data quality does not depend only on the code: it also depends on a transparent, documented, and consistent configuration.

Checks before publishing

Before considering the integration complete, perform a structured check. A thorough check avoids errors difficult to detect after days of active campaigns.

• Check that Matomo correctly records visits from Google Ads campaigns.
• Verify that UTMs are consistent and do not change names between campaigns.
• Complete a test order and check that Matomo records the transaction.
• Verify that the Google Ads conversion tag fires only once.
• Check conversion value, currency, and transaction ID.
• Use Matomo Tag Manager preview mode before publishing.
• Compare data between Matomo, PrestaShop, and Google Ads knowing that attribution can differ.

Why Matomo and Google Ads data may not match

It is normal for Matomo and Google Ads to show different numbers. The platforms use different attribution models, time windows, cookie management, and deduplication logics. Google Ads can attribute a conversion to an ad click even if the order occurs days later; Matomo can show the path according to different rules and with a broader session reading.

The point is not to get two identical reports, but to understand how to read them. Google Ads is used to optimize advertising spend; Matomo is used to analyze site behavior and overall traffic quality. If data are configured consistently, differences become useful information, not a problem.

Conclusion: a clearer flow for better decisions

Integrating Matomo with Google Ads means building a more transparent measurement system: campaigns tracked with orderly UTMs, active ecommerce tracking, conversions sent to Google Ads, and tags managed centrally with Matomo Tag Manager.

For a PrestaShop ecommerce, starting from a stable technical base simplifies all subsequent work. The Matomo Analytics for PrestaShop with ecommerce tracking module helps integrate Matomo into the store, while the PrestaShop Module for GA4 integration can be useful when you also want to maintain GA4 tracking. With an orderly configuration, you can reduce manual work, improve result reading, and support more informed Google Ads campaigns.