<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog: guides and product news</title>
    <link>https://tracelog.io/en/blog/</link>
    <description>Guides to the problems a store meets when a tool stops counting its sales, and what is new in TraceLog</description>
    <language>en</language>
    <atom:link href="https://tracelog.io/en/blog/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Meta or Google Ads counting purchases twice: how to check</title>
      <link>https://tracelog.io/en/blog/ad-platform-counting-purchases-twice/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/ad-platform-counting-purchases-twice/</guid>
      <description>If Meta or Google Ads shows more purchases than your store took, the confirmation page may be sending some orders twice. Here is how to check by hand, and what TraceLog shows.</description>
      <pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Whether an alert already happened on another client, in the alert itself</title>
      <link>https://tracelog.io/en/blog/alert-on-another-client/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/alert-on-another-client/</guid>
      <description>On the Agency plan, History lists the alerts of all your clients, grouped when they are the same, and an alert's page shows which of your other clients had it before. Where clients share what changed, it says so. It does not say why, predict a break or prevent one.</description>
      <pubDate>Wed, 18 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>GA4 conversion drop alerts: fewer sales, or fewer recorded?</title>
      <link>https://tracelog.io/en/blog/ga4-conversion-alerts/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/ga4-conversion-alerts/</guid>
      <description>GA4 can email you when conversions drop: that's what custom insights are for. Then comes the question your client or your boss will ask: did sales fall, or did they stop being recorded? Answering it takes a second record, kept apart from GA4. TraceLog keeps one, beside GA4. If sales stop being recorded, it alerts you and holds back the affected figures, so you don't decide on half the data.</description>
      <pubDate>Wed, 18 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What changed on your site, on the day your figure moved</title>
      <link>https://tracelog.io/en/blog/site-changes-beside-your-figures/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/site-changes-beside-your-figures/</guid>
      <description>When a figure moves, the first question is whether the site changed, and on which day. Analytics now marks each day a change happened and lists what changed under the chart, on every plan. On WooCommerce and PrestaShop, TraceLog also notes a new theme or consent setup by itself. It states the day, never that the change moved a figure.</description>
      <pubDate>Wed, 18 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>WooCommerce orders missing in GA4 after payment</title>
      <link>https://tracelog.io/en/blog/woocommerce-orders-missing-in-ga4/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/woocommerce-orders-missing-in-ga4/</guid>
      <description>When WooCommerce has a paid order and GA4 or Meta has no purchase for it, the payment most often ended on another site — PayPal, Stripe Checkout, a bank's card page — and the buyer never came back to the order received page, where the purchase is sent. The page may also not load the tag, the buyer may not have consented, or a reload may send it twice.</description>
      <pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Each Monday, which visitors finish less often than the rest</title>
      <link>https://tracelog.io/en/blog/where-fewer-finish/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/where-fewer-finish/</guid>
      <description>From Pro, each Monday TraceLog names the group of visitors that finishes your main conversion less often than the rest of your store: a channel, a campaign, a device, a country or a landing page, among others. You see where it happens and decide what to look at first. TraceLog does not say why.</description>
      <pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Google Ads &quot;Awaiting conversions&quot;: how to check</title>
      <link>https://tracelog.io/en/blog/google-ads-conversion-status/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/google-ads-conversion-status/</guid>
      <description>Awaiting conversions means Google Ads recorded none in the last 7 days, which a quiet week and a conversion that stopped being recorded can both explain. Check your store's orders first.</description>
      <pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Meta pixel not active: how to check</title>
      <link>https://tracelog.io/en/blog/meta-pixel-not-active/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/meta-pixel-not-active/</guid>
      <description>When Meta says your pixel is not active, the pixel has stopped sending it events from your site. It usually follows a change — a theme, a checkout, a consent banner or a platform — and the site shows no error. Check the page and your store's orders before you change a campaign.</description>
      <pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Conversions dropped suddenly: sales or tracking?</title>
      <link>https://tracelog.io/en/blog/conversions-dropped-suddenly/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/conversions-dropped-suddenly/</guid>
      <description>A sudden drop in conversions has two very different explanations: fewer people bought, or your site stopped recording a step of the purchase while they kept buying. The second usually follows a change — a theme, a checkout, a consent banner or a platform — and shows no error. Compare the drop with your store's own orders first.</description>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>GA4 double counting purchases: how to check</title>
      <link>https://tracelog.io/en/blog/duplicate-purchase-events/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/duplicate-purchase-events/</guid>
      <description>When GA4 counts more purchases than your store took, the same order is usually reaching it twice: two tags send the purchase, or the event leaves without a transaction ID, so GA4 has nothing to recognise the second one by. GA4 removes a repeated purchase only when both carry the same transaction ID.</description>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>GA4 not tracking purchases: how to check</title>
      <link>https://tracelog.io/en/blog/ga4-not-tracking-purchases/</link>
      <guid isPermaLink="true">https://tracelog.io/en/blog/ga4-not-tracking-purchases/</guid>
      <description>When GA4 shows fewer purchases than your store took, or none, the cause is usually one of five: the purchase tag no longer runs on the order confirmation page, consent keeps it from sending, the event arrives without the data GA4 needs, the payment ends where the buyer never returns to that page, or the report has not caught up yet.</description>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
