# Changelog

{% updates format="full" %}
{% update date="2026-05-07" tags="improvement" %}

## More accurate Viewed Product tracking for Klaviyo

Viewed Product events sent to Klaviyo are now matched more accurately to customer profiles, improving the reliability of product browse data for segmentation and flows.
{% endupdate %}

{% update date="2026-05-07" tags="improvement" %}

## Setup and integration improvements

Several improvements have been made to setup and integrations:

* The Littledata Pixel status now accurately reflects whether the pixel is installed.
* Recharge webhooks are now removed automatically when you disconnect the Recharge integration.
* The welcome setup screen no longer appears for stores with the app embed disabled.
* Order plan limits now display correctly for all stores.
  {% endupdate %}

{% update date="2026-05-05" tags="improvement" %}

## Refreshed dashboard layout

The Littledata dashboard has a cleaner, more streamlined layout. It's easier to see the status of your connected destinations and understand what each source add-on does at a glance.
{% endupdate %}

{% update date="2026-04-28" tags="improvement" %}

## Improved Klaviyo event deliverability

We've improved how Added to Cart events are delivered to Klaviyo, ensuring more events are successfully tied to customer profiles.

* More ATC events now reach Klaviyo with a matched customer profile
* Increased profile coverage for Added to Cart activity, improving segment and audience accuracy
  {% endupdate %}

{% update date="2026-04-09" tags="improvement" %}

## Littledata pixel now supports Shopify Markets

The pixel now loads with market-specific destination keys, so brands can segment tracking data by the market where each event originated.

This improves tracking consistency to be inline with our support for Shopify Markets.
{% endupdate %}

{% update date="2026-04-08" tags="changed" %}

## Live order feed deprecation

We have deprecated our Live order feed to improve user experience, as it was running in our legacy app and contributing to confusion.

We're exploring ways to bring it back as part of our new app experience.
{% endupdate %}

{% update date="2026-04-07" tags="improvement" %}

## Improvement to the Littledata pixel

Littledata Pixel is now clearly marked as optional in the setup flow, so it is not mistaken for a critical issue when not yet configured.
{% endupdate %}

{% update date="2026-04-07" tags="improvement" %}

## Smarter multi-app handling

When two Littledata apps are detected in the same store, the secondary app's UI is now blocked to prevent unexpected behaviour.

The secondary app can be safely uninstalled - only one is needed.
{% endupdate %}

{% update date="2026-04-07" tags="tag" %}

## Microsoft Ads now available to connect

Our [Microsoft Ads ](https://www.littledata.io/shopify/microsoft-ads)destination has finally launched into public beta testing.

Customers can typically see an 80% uplift in tracked conversions is Microsoft Ads when using our [Enhanced Conversion](https://help.ads.microsoft.com/#apex/ads/en/60178/-1) server-side implementation.
{% endupdate %}

{% update date="2026-04-01" tags="improvement" %}

## Improved detection for first recurring purchases

We've improved how first recurring purchases are identified and sent to Meta and Microsoft Ads by leaning more heavily on the Recharge connection to determine subscription lifecycle events.

This means better event quality and more accurate attribution for stores using Recharge.
{% endupdate %}

{% update date="2026-03-27" tags="improvement" %}

## Headless store support for custom domains

Headless stores using fully custom domains can now bypass the app embed check during setup. This removes a setup blocker for stores that don't use a standard Shopify theme.
{% endupdate %}

{% update date="2026-02-13" tags="feature" %}

## Shopify Markets support (public beta)

<figure><img src="/files/rsIEuuT8fdlGoHv2r9l9" alt=""><figcaption></figcaption></figure>

Markets support is available in public beta. You can now tailor your data management to different Shopify Market configurations, so each market's customer behaviour flows to the right destination.

If you sell across multiple regions, you no longer need to rely on manual segmentation in Google Analytics, workarounds in server-side GTM for paid ads, or proxy attributes like country and language to segment email and SMS campaigns. Littledata handles the market context natively, giving you cleaner analytics, better ad optimisation, and the ability to localise your marketing flows by market.

<a href="https://help.littledata.io/integrations/shopify-markets/setup-and-sync" class="button primary">Learn more</a>
{% endupdate %}

{% update date="2026-02-09" tags="improvement" %}

## Smarter app embed and pixel detection

Audit checks improved for app embed and Littledata pixel status for stores with multiple Littledata installed. Previously, having more than one app could cause the checks to sometimes show an incorrect status.
{% endupdate %}

{% update date="2026-01-28" tags="improvement" %}

## Event Settings tab redesign

The Event Settings tab has a refreshed layout that is cleaner. All existing functionality remains the same.
{% endupdate %}

{% update date="2026-01-26" tags="improvement" %}

## Improved filtering for cloned checkout sessions

We’ve improved our bot protection to suppress extra checkout events created by Shopify checkout session cloning, which can inflate checkout metrics and impact conversion reporting.

Bot protection is currently in beta. To enable this feature on your destinations, please contact our support team!
{% endupdate %}

{% update date="2026-01-26" tags="improvement" %}

## Support for Segment regional endpoints

Littledata now supports both the[ US and EU Segment ingestion endpoints](https://www.twilio.com/docs/segment/guides/regional-segment).

If you’re using a European Segment workspace, you can choose the EU regional endpoint in your Segment destination settings to send data directly from Littledata to Segment within the EU.

This helps ensure your data stays in the correct region and aligns with Segment’s setup and compliance requirements.

The setting is found under the Tracking customisation tab of your Segment's connection settings.

<a href="/spaces/1QhTbrMraNWciQeDvu1b/pages/GhtQtguePhGwMdvcENfc#advanced-settings" class="button primary">Read documentation</a>
{% endupdate %}

{% update date="2026-01-21" tags="new,changed" %}

## GA4 property branding

GA4 properties connected through Littledata now automatically include "by Littledata" in the property name. This makes it clearer which ones are managed by Littledata. Existing connected properties have also been updated.
{% endupdate %}

{% update date="2026-01-20" tags="changed" %}

## New all-inclusive pricing

All destinations are now included on every tiered plan. Existing customers have been migrated to legacy plans. You will have to make a plan change to the current pricing if you want to take advantage of the new all-inclusive plans.
{% endupdate %}
{% endupdates %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.littledata.io/changelog/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
