Trackers are pre-built tracking configurations that Multifeeds installs into your Google Tag Manager (GTM) container to send events (e.g., Page View, Add to Cart, Purchase) to platforms like Meta (Facebook), Google Ads, GA4, Pinterest, and AWIN.
A tracker is a single tracking setup you create in Multifeeds.
When you save a tracker, Multifeeds installs (or updates) the required GTM tags, triggers, and related configuration in your container.
Trackers help you avoid manual GTM setup and keep tracking consistent across events.
Client (Web) trackers: Installed into a GTM Web container and run in the browser.
Server trackers: Installed into a GTM Server container and run server-side (requires server-side tracking setup).
Tracking on ads platforms (Google/Meta/…) has become more complex over time. Trackers help you:
Install tracking faster without manual GTM setup
Keep tracking consistent across key ecommerce events (View Item, Add to Cart, Purchase, …)
Reduce common mistakes that lead to missing or inaccurate conversion data
Manage cost transparently using monthly credits (each tracker uses a defined number of credits)
Tracker Name is a label to help you identify the tracker in Multifeeds.
It does not change your platform account settings, but it helps keep your GTM setup organized.
Enabled trackers track events when they happen (and conditions are met).
Paused trackers are kept in your setup but do not track.
Events define what customer actions you track (examples: Page View, View Item, Add to Cart, Begin Checkout, Purchase).
Some trackers support multiple events (multi-event). Others may be single-event depending on tracker type.
For some trackers (e.g., GA4), certain events may be mandatory (such as page_view).
If your campaigns are new or have low purchase volume, consider optimizing with a “micro conversion” first (e.g., Add to Cart or Begin Checkout) because it happens more often and provides more data for the ads platform to learn.
After the campaign stabilizes and you get enough volume, you can switch the primary conversion goal to Purchase.
These options let you control where and when the tracker tracks:
Only track on specific currency
Use this if you want tracking to run only for a selected store currency.
Option: Whitelist non-currency contexts (useful if some pages/contexts don’t provide currency but you still want tracking).
Only track on specific URL pattern (regex)
Use this if you only want tracking to run on matching URLs.
Option: Whitelist checkout pages (ensures checkout-related URLs are still included when URL filtering is enabled).
If your store has multiple localized storefronts (e.g., fr.mystore.com in EUR and us.mystore.com in USD) and each market is managed by a different ads account, you can prevent data mixing by limiting a tracker to a market using:
Specific currency (EUR vs USD), and/or
Specific URL pattern (e.g., fr.mystore.com )
When using URL pattern, pay extra care not to block the tags on checkout pages unintentionally. If your checkout URL structure differs from storefront URLs, consider enabling the “Whitelist/Skip URL check on checkout pages” option (use together with a currency filter).
Do note that there are cases, for example use of URL subpath of a single domain, in which the checkout page URL pattern could be different from other pages of the market.
In those cases it might be desired to turn on the Skip URL check on checkout pages so the tags are fired when the URL matches OR when the visitor is on the checkout page regardless of the market. Should only be used in combination with the currency filter.
Skip URL check on checkout pages means the checkout tags (Purchase, Begin checkout, etc) will fire as long as the page URL has the "/checkouts/" text.
Use consent settings if you need trackers to track only after the correct user consent is granted.
Not set
Default behavior (no extra consent gating).
No additional consent required
The tracker is allowed to track without checking additional consent types.
Require additional consent
The tracker tracks only when the specified consent types are granted.
Learn more about how Multifeeds handle consent here (https://docs.woolytech.com/article/227-consent-and-tracking)
Many trackers have this setting, which is where you align the IDs being fired with the IDs stored in the ads platform. Matching them is very important, or the ads plaform (Google, Facebook, etc.) won't be able to match the conversions (or remarketing events) with products in their database (Google Merchant Center, Facebook catalog, etc.).
Some common Item ID formats:
shopify_XX_{product_id}_{variant_id}. XX is a 2-letter country code. This format is used by the Google Youtube channel app.
{product_id}_{variant_id}
{variant_id}
{sku}
Custom ids that are stored in metafields
For Google Ads remarketing tags, the item ID in tag has another option which is to match against item group ID in product feeds.
Most feed apps use the product ID as the item group ID as in Shopify, variants of a product is a native equivalence to the item groups in Google Shopping. Because of this, the item ID in the remarketing tags could be set to use Product ID.
When a purchase is made as an order, you have two options to set the conversion value to
Total price (include duties, shipping, and taxes)
Subtotal price (before duties, shipping, and taxes) - pick this if you want to focus on the sale value of the products and leave out the duties, shipping, and taxes which might be not relevant to your business
Monthly credits are a monthly allowance that represents how many trackers you can run.
They are billed monthly (if you have exceeded the freemium credits and subscribed for extra).
Your subscription price include Trackers add-on, which determines how many monthly credits you receive.
Every shop includes 6 monthly credits by default ($6/month equivalent).
The first GA4 Web tracker is free each billing cycle.
This applies only to GA4 Web (Client) trackers.
TrackerContainerMonthly credits | ||
Web | 1 | |
Google Ads Conversion | Web | 1 |
Facebook Pixel | Web | 5 |
Google Analytics 4 (GA4) | Web | 5 (first GA4 Web tracker free) |
Google Ads Remarketing | Web | 5 |
AWIN | Web | 5 |
Pinterest (1) + Google Ads Conversion (1) → uses 2/6 monthly credits (freemium).
Pay $33/month → you receive 33 monthly credits (plan-dependent).
GA4 Web installed first → GA4 Web “first 1 free” applies → that GA4 Web tracker contributes 0 monthly credits usage for the first one.
No. Monthly credits are billed monthly (recurring).
For example, 10 monthly credits means
10/month, not a one−time 10 payment.
Removing a tracker reduces your monthly usage, freeing monthly credits you can use for other trackers in the same billing cycle.
No — you don’t pay twice for the same period.
When you upgrade from 10 → 15 monthly credits , Shopify cancels the previous recurring charge and replaces it with the new one. Per Shopify’s prorating rules for app subscription upgrades, you’re charged:
Your original plan amount for the start of the billing cycle, plus
A prorated amount for the difference between the two plans for the remaining days in the cycle.So you pay only the prorated difference to move to 15 monthly credits for the rest of the current billing cycle, and then going forward you’ll be billed the 15-credit plan price each billing cycle.
Example (illustrative):
If your 10-credit plan is $10/month and the 15 − credit plan is $15/month, and you upgrade halfway through the billing cycle, Shopify charges (at the end of the cycle):
$10 + ($15 - $10) (days remaining / days in cycle) = 10 + 5 * (15/30) = $12.5
Reference: Shopify Help Center — App prorating for upgrades/downgrades
“Upgrade required” appears: Your available monthly credits are not enough for the tracker you’re trying to install. Click Add credit to purchase more monthly credits, then retry saving the tracker.
Usage seems delayed: If you just upgraded or changed trackers, refresh the page to ensure your latest usage is displayed.
