How Atomato works with Shopify's customer privacy settings

Shopify decides when Atomato's web pixel runs, based on each shopper's privacy choices, and the pixel is how message activity and click-based revenue reach Atomato. The storefront script that shows the bell, feed and messages runs for every shopper and keeps a few notes in browser storage.

This page describes what Atomato does, not what any law requires. For the full list of data, see What shopper data does Atomato collect?

What Shopify runs only when a shopper's privacy choices allow it

Atomato's pixel declares these purposes to Shopify: analytics, marketing and sale of data. It doesn't declare preferences, and it runs in Shopify's strict pixel sandbox. Shopify uses these purposes and each shopper's choices, from your consent banner or Shopify's customer privacy settings, to decide when the pixel runs.

When it runs, the pixel collects:

• Message events: impressions and clicks on every plan, plus hovers, dismissals, NotiSell add to carts and signups on paid plans.
• Revenue events: Shopify's add to cart, checkout started and checkout completed events after a shopper clicks from a NotiFeed, NotiPop or NotiSell message through to your store, or adds a product from NotiSell.

It sends waiting events to Atomato every 5 seconds. When the pixel doesn't run, messages still show and work, but that visit's message events don't reach Analytics, and its carts and checkouts aren't linked to a message click.

What still happens when the pixel is blocked

Atomato's storefront script doesn't check the shopper's privacy choices, so these steps happen for every shopper:

• When the Atomato app embed is on, it loads the script on every page. For a signed-in customer, it adds their customer ID, first name and last name to the page.
• On each page, the script asks Atomato for campaigns through your store's app proxy. The request address carries the page path and query string, device type, language, country and a signed-in shopper's first and last name, used for {customer.name} and {customer.last_name}. Shopify's app proxy adds the customer's ID.
• For Specific customer segments, Atomato asks Shopify whether a signed-in customer is in them and keeps the answer in memory for 3 minutes. For SKIO Integration rules, it uses the SKIO details it keeps for that customer, fetched from SKIO when missing or over a day old.
• A product added from a NotiSell message gets a _notisell line property. Atomato tags orders that contain it and counts NotiSell revenue from them, as Track NotiSell orders, revenue and basket impact explains.
• Seen messages and signup progress are still saved in the browser.

What Atomato keeps in the shopper's browser

Atomato's scripts use local storage and session storage rather than cookies, and Atomato's code doesn't write cookies itself. Adding a NotiSell product or applying a NotiEmail discount code uses Shopify's own cart, like the rest of your store.

• notifeed_seen_ids, notisell_seen_ids, notiemail_seen_ids and notipop_seen_ids (local storage, until the shopper clears it): messages the shopper has seen, so the badge clears and a NotiPop doesn't repeat.
• atomato_seen_ plus the campaign type (local storage, until cleared): which events each message has already sent, so later ones count as repeats.
• atomato_notiemail_progress (local storage): for signups whose Success step has Add discount on, the email or phone number and the code shown. Entries over 30 days old are removed only when Atomato next reads this key.
• A hashed key (session storage): NotiSell product details, reused for 5 minutes, only in that browser tab.
• atomato_revenue_session (local storage, only when the pixel runs): a random session ID, the clicked campaign and product, click time and device. Removed after an order, or when read more than 30 days after the click.
• atomato_queue and atomato_revenue_queue (session storage, only when the pixel runs): events waiting to be sent.

What to check for your store

Whether your consent banner and privacy notice should cover browser storage as well as cookies, and whether to name Atomato, is your decision. Check with your own legal adviser: this page isn't legal advice.

For Atomato's own policies, see where to find Atomato's privacy policy and terms. To see your store with empty browser storage, follow How to test Atomato on your store like a new shopper.