Back in stock
The variant someone viewed while sold out is available again. People who viewed it and did not buy it can enter the automation, within the window you set.
First-party pixel
People who only browsed can join too
Use interest in a product to build groups and start automations. Capture starts with cookie consent. Events stay only in the browser for 30 days, until identification by email or phone at checkout or login. Identification does not authorize marketing: each channel needs its own consent.
14‑day free trial on Shopify and a 30‑day money‑back guarantee.
Before identificationTailored trousers
After entering an email at checkoutEmily Carter
The earlier visit appears on the profile
Visit recorded with cookie consent. Marketing requires consent for the channel.
- Behavior becomes a group condition
- Earlier visits connect to the customer
- Your own pixel, no third-party cookies
The visit gets a name, and keeps its history
Follow someone who viewed a sold-out product, returned to the store and entered an email at checkout. The earlier visit joins their profile.
The visitor accepts cookies
Only then does the pixel record behavior. Capture is first-party, in the store itself, with no third-party pixel or cookies.
The history waits in the browser
Before identification, events stay only in the person’s browser for 30 days. None of that anonymous history reaches Vertia’s server.
Contact details connect visits to a profile
Only an email or phone number provided at checkout or login identifies the person. Events still stored join the profile, keeping the original date of each visit.
Where the behavior comes from
ExampleEmily CarterAustin · from the checkout email
Arrived and accepted the store’s cookies
6 days ago
Viewed a sold-out product
6 days ago
Came back and added another product to the cart
Today
Entered an email at checkout
Today
Emailemily.carter@example.comBecame Emily Carter
Today
The visit from 6 days ago is added to the profile.
Joined the group
Today
Viewed a sold-out product: now 35 customers.
Illustrative example. Identification does not authorize marketing.
What happened before the purchase
Store activity becomes conditions for your groups and automations. Every event keeps the time it happened.
- Visited the store
- Viewed a product
- Viewed a collection or category
- Searched
- Added to cart
- Started checkout
- Viewed a sold-out product
A sold-out product is a variant that was unavailable at the time of the visit, according to platform data.
The product changed. So did the reason to return
Use the interest someone has already shown to choose when to reconnect, always with consent for the channel.
Price drop
The variant’s price fell below what it was at the visit or cart addition. You choose which of those actions count and how much the price must drop. Only available variants qualify; people who bought the item within the window or already viewed or added it to their cart at the lower price are excluded.
The reference is the variant’s state at the time of the interaction. Without confirmed availability or price, the event does not qualify for these triggers.
Knowing who someone is does not give permission to send
Cookie consent allows behavior to be recorded. Marketing consent allows messages on that channel. They are separate choices.
The pixel does not create or change email or WhatsApp consent. Clicking a link does not identify the browser either: connecting visits to a profile requires contact details at checkout or login.
Put behavior to work in your next action
Groups by behavior
Combine what someone bought with what they viewed or added to their cart. The group keeps up with who matches.
Explore groupsAutomations
Use behavior to decide who enters and which path they take, including back-in-stock and price-drop triggers.
Explore automationsIn the customer’s timeline
Identified visits join the customer’s history with their original dates. Understand their interest before planning the next conversation.
Questions about first-party pixel
- How does the pixel handle consent and Brazil’s LGPD?
- Capture requires affirmative consent to analytics and marketing cookies. The store is the data controller; Vertia processes data on its behalf. Behavior is included in the person’s export and deletion requests. Identification does not create marketing permission.
- What is stored?
- The action, store, product and variant where applicable, original time and an occurrence identifier. To interpret product visits, the CRM reads availability and selling price from the platform. Capture does not store IP addresses; cost, margin and stock quantities are excluded.
- How long are visits stored?
- Before identification, for 30 days, only in the browser. When someone identifies themselves, events still stored connect to their profile. Customer retention then applies, as described in the Privacy Policy; when it expires, the link to the person is removed. A group or trigger window is separate and counts from the original visit date.
- How do I install the pixel in my store?
- The Vertia app installs the pixel through the platform’s official route, via your store integration. Capture only starts with the visitor’s cookie consent. This applies to Shopify, Nuvemshop and other integrated platforms.
- Can a message click identify someone?
- No. The click records that interaction but does not prove who is browsing. To connect visits to a profile, the person must identify themselves by email or phone at checkout or store login.
Connect your store today
Start from what's ready and fine-tune at your pace.
14‑day free trial on Shopify and a 30‑day money‑back guarantee.