Skip to main content
ADVANCED SUBSCRIBER INTELLIGENCE

E-Commerce modules built around one protected truth rail.

ASI integrates your ecommerce store, from WooCommerce and BigCommerce to Shopify, so operators can target from real purchase behaviour too. But store data does not get to decide who gets emailed. External platforms provide evidence. ASI Core owns truth. Operators approve action. Sending stays protected.

That means purchase history, category interest, repeat buying, refunds, and commercial behaviour can become useful evidence inside ASI Core, while consent, suppression, validation, bounce state, and send safety remain above targeting. Buying something is not the same as asking to be marketed to.

Purchase Behaviour
Category Interest
Repeat Buyers
Consent-Protected Targeting

e-commerce modules

Real purchase behaviour matters. So does permission.

ASI can use ecommerce evidence to help operators build smarter audiences, but Core still asks the harder questions first: are you allowed to email this person, is the address safe, does the send risk your reputation, and does the evidence still point to a defensible marketing action?

Examples of operator-reviewed ecommerce targeting

ASI helps build audiences from evidence the platform can prove, not from assumptions the operator has to guess at later.

Bought a specific product

Target customers who bought pink hair bands in the last 6 months, or a specific product line that points to a clear commercial interest.

Bought Product A, not Product B

Build reviewed audiences around customers who bought one product but not its companion, follow-up, or higher-margin alternative.

Repeat buyers

Find customers who bought twice but not in the last 90 days, or buyers whose repeat behaviour suggests a high-value retention opportunity.

High spenders in a category

Separate higher-value customers from one-time or low-value buyers using category and order evidence instead of shallow campaign activity.

Lapsed buyers

Identify customers with previous commerce activity who now sit in a useful reactivation window, without pretending every old customer is equally reachable.

Protected exclusions

See customers with commerce activity but missing marketing consent, or buyers suppressed because validation or reputation checks say “do not touch.”

E-Commerce module family

WooCommerce, Shopify, and BigCommerce feed purchase evidence into ASI Core so operators can build smarter audiences without handing store logic control of the truth rail.

Ecommerce Evidence

WooCommerce

WooCommerce helps ASI understand what customers actually do, not just whether they opened an email. Orders, products, categories, refunds, coupon behaviour, customer identity hints, and purchase patterns can all become evidence inside Core.

Operator outcome: build reviewed audiences around real buyer behaviour, product interest, repeat buying, and category movement.

Core protection: WooCommerce can feed evidence, but Core still owns identity, consent, suppression, validation, and send safety.

Ecommerce Evidence

Shopify

Shopify brings customer activity, store history, products, order signals, refunds, and commercial patterns into ASI Core so operators can work from a more complete buyer picture.

Operator outcome: build product-led, buyer-led, and reactivation audiences using evidence grounded in real store activity.

Core protection: store evidence does not bypass marketing consent, suppression truth, or send protection.

Ecommerce Evidence

BigCommerce

BigCommerce gives ASI access to order history, product and category evidence, customer behaviour, and commercial patterns that can support more disciplined audience building.

Operator outcome: turn commerce evidence into reviewed audience segments instead of broad guesswork and store-led noise.

Core protection: BigCommerce feeds evidence into Core. Core keeps the decision rail.

One Core. Store evidence in. Protected targeting out.

ASI ecommerce integrations do not become private databases with their own opinions. They feed ASI Core. Core resolves identity, checks eligibility, applies consent and suppression truth, respects validation and bounce state, and only then allows operator-reviewed targeting decisions.

Store Platform
↓
ASI E-Commerce Module
↓
ASI Core Evidence Layer
↓
Operator Review
↓
Protected Audience / Send Workflow

Modules feed Core. Modules do not own subscriber truth. Modules do not mutate lists directly. Modules do not wake sending. ASI protects the operator from bad automation.

The ASI difference

Yes, ASI understands purchase behaviour. But it also asks the harder questions before email action is approved.

What ecommerce evidence can tell you

It can tell you what someone bought, what category they care about, how often they buy, how much they spend, whether they refunded, and whether a pattern suggests a real commercial opportunity.

That is useful evidence. But evidence alone is not permission, and it is not a send decision.

What ASI Core still checks

ASI still asks whether you are allowed to email the contact, whether the address is safe, whether the send risks your reputation, and whether later engagement evidence still points to useful human outcomes.

That is the difference between omnichannel marketing and responsible contact infrastructure.

Buying something is not the same as asking to be marketed to.

That hits ecommerce operators right between the spreadsheets because it is true.

ASI can see purchase activity, but if we do not have valid marketing consent, we do not send.

ASI has already proved this rail in practice: it saw ecommerce consent but no marketing consent and refused to allow the send. That is the difference between “we have customer data” and “we have permission to use that customer data for marketing.”

Connected data does not bypass ASI safety.

Every connected commerce signal still sits below ASI Core checks. Consent, suppression, validation, bounce state, send safety, and operator approval remain above targeting. Store integrations can provide evidence, but they do not get to decide who ASI emails.

The same platform, a stronger commerce evidence lane.

ASI does not add channels to create more noise. ASI adds channels only when Core truth can prove the contact is eligible, consented, and safe to message. That is how store evidence becomes useful without turning the platform into reckless automation.