Platform·Guide

Built-in email or a separate tool

You delivered the gallery and sold the prints. Six months later you want past clients to hear about mini sessions. The people who bought from you already sit in your studio system. When email lives somewhere else, the useful context often stops at a CSV.

Before you commit

Questions to ask any platform that says it has email

  1. What kind of email is it?

    Transactional notices, lifecycle or sales triggers, or campaigns to a list. Three jobs share one marketing label.

  2. How does someone become a subscriber?

    Explicit opt-in from site signup or checkout. A customer can buy and still stay off the marketing list.

  3. What can the audience be based on?

    Subscriber status alone, or studio facts next to it: orders, products, purchase dates, and client history.

  4. Who sends, and who owns deliverability?

    What the recipient sees in From and Reply-To, plus who runs authentication, bounces, suppressions, and reputation.

  5. What happens after you send, and if you leave?

    Bounce and complaint feedback used for suppressions, plus whether you can export list and status fields if you leave.

Three things called email

Vendors label three different jobs as built-in email. Transactional mail tells a client their gallery is ready, their print shipped, or their access code arrived. Triggered sales automations fire from gallery dates, idle carts, or similar lifecycle events. Broadcast campaigns send one message to a list you chose.

ArtInStack Email Center is the third job: campaigns to a subscribed list. Receipts, invitations, and gallery access codes stay on the transactional path.

How someone joins the list

Customer acquisition and subscription acquisition are different events. On ArtInStack, people join the marketing list through explicit opt-in on the public site—blog and footer signup forms—or by checking marketing consent at checkout. Paying for a print or download does not subscribe them by itself.

Purchase data can help decide who belongs in a campaign audience. It does not, by itself, subscribe someone to ArtInStack marketing email. ArtInStack requires an explicit marketing opt-in before sending campaign mail.

A buyer is not a subscriber

This is the enforcement side of that rule. Orders and newsletter consent are separate records. A completed print or digital purchase does not add anyone to the mailing list. Segments can require a purchase and require subscribed status in the same filter.

When you schedule a campaign, the segment rule freezes into a recipient list. At send time the worker checks subscribed status and suppressions again. Someone who bought, subscribed, then unsubscribed after you scheduled does not receive that mail.

Campaign mail includes List-Unsubscribe and List-Unsubscribe-Post headers for one-click unsubscribe, plus a link in the message. Unsubscribing removes that address from future studio campaigns. Transactional mail stays on its own path.

Studio data as the audience source

A general email platform starts with a mailing list and email behavior. A studio platform can start with the relationship around the work: galleries, clients, products, and orders.

That is how segments become studio questions instead of list tricks. People who bought a print in the last year and have not booked again. Clients who took a digital download and never bought an album. Buyers of one collection who have not seen the new one. Past clients who purchased downloads.

On ArtInStack, campaign audiences start as filters on facts you already have in the same studio account. Consent still decides who is mailed.

Who sends, and who owns deliverability

Recipients see your studio name in the From display name on ArtInStack’s shared marketing address ([email protected]), with replies routed to your contact. The platform handles authentication, bounce and complaint handling, suppressions, and sending reputation for that path.

Custom-domain sending is not available today. Campaigns use the shared ArtInStack address rather than an email address on your own domain—an architectural tradeoff so the studio is not operating its own email-delivery stack.

What happens after you send

Email Center processes bounce and complaint events and maintains suppressions so ineligible addresses are not mailed again. It does not currently provide a published campaign analytics dashboard for opens or clicks. Unsubscribes are handled through List-Unsubscribe headers and an in-message link, separate from open/click reporting.

Who owns the audience

Subscriber export from Analytics lets you take email, name, status, source, and subscribe/unsubscribe timestamps to another tool. Treat that as list portability—not a complete consent-history migration record—unless you keep your own records elsewhere. The platform is where the audience lives while you work, not a trap that holds the list hostage.

Campaigns and automation are different products

Email Center is built for campaigns, studio-native audience, commerce-aware segments, and consent-aware sending. It does not run drip sequences, branching workflows, or cart-recovery automations.

Dedicated email platforms earn their keep on multi-step journeys, behavioral triggers, heavy template systems, and lifecycle automation. That is a different product category. ArtInStack does not need to recreate it to make email useful next to galleries and orders.

When a separate tool is the better choice

Choose a dedicated email platform when email itself is becoming a sophisticated marketing operation: multi-step automation, mail that sends as your own domain in the From address, or a design system built around elaborate templates.

Choose ArtInStack Email Center when your audience should live beside the galleries, clients, and orders that already define your studio—so campaigns start from relationship and commerce facts, and consent stays explicit.

Your orders pick the audience

Their opt-in decides who gets the email.

Also in Guides: Choosing the right platform · What leaves your site · One unified OS for your visual business

All Platform guides · Guides home