Skip to main content
This guide takes a new workspace to a live send. The hands-on work is short. The waiting is not: DNS records take time to propagate, sender addresses need a confirmation click, and domain warmup ramps your volume over days. Read the whole page before you start. Two things stop merchants who follow it in order, and both are easier to plan for than to hit by surprise: an active paid plan is required before the dashboard opens, and you cannot send marketing email until both a domain and the specific From address are verified.

Before you start

Create a workspace

Sign up at app.senderz.app/register. You give a first and last name, a business email, a password, your store name, and your store platform. You can also sign in with Google. Google does not supply a store name or platform, so a Google signup is sent to a short complete your profile screen to add them. There is no skip.
Installing from the Shopify App Store does not create a workspace.The install parks a pending connection and sends you to normal Senderz registration or sign-in. After you are signed in, a Connect your store screen asks which Senderz workspace should receive that store’s customers, orders and storefront events. You pick an existing workspace where you are an owner or admin, or you create a new one there.No charge is created at that point. You review and approve any paid plan in Shopify before billing begins. See the Shopify guide.

Expect a paid plan step

Since 12 August 2026, a workspace needs an active paid plan before its owner or admin can use the dashboard. Until the plan is active, both roles are redirected back to the setup wizard no matter which page they open.
Workspaces created before 12 August 2026 are not gated. This is why an older account and a brand new one behave differently on the same screen.
A few details worth knowing up front:
  • The plan step has no skip. Finishing the five setup steps does not open the dashboard, and dismissing the wizard does not either.
  • Editors, designers and viewers are not redirected. Only owners and admins see the gate.
  • The contacts import screen stays reachable while the gate is active, so you can keep an import running.
  • The onboarding screen carries its own account menu. You can sign out from it, and if you belong to another workspace you can switch into it.
Plans are sized by contact count, from Senderz 500 up to Senderz 50,000, plus Enterprise for larger lists. Each tier gives you a contact limit and a monthly email allowance. Plans do not include SMS credits. Credits are bought separately as packs. The plan step shows this as “Credit packs, bought separately”. The step also shows two different contact numbers. Only marketable contacts, meaning contacts opted in to at least one channel, count toward your plan limit. Everyone else is stored free.

The setup wizard

On first sign-in the wizard opens on Connect store. It has five steps: The skip control is labelled Skip for now. The legal step has no skip, and its Continue button reads “Please approve all 3 items” until you tick all three.
To get back to the wizard later, use Initial Setup in the sidebar footer. There is no Integrations section inside Settings.

1. Connect your store

Your store is the source of contacts, orders and behavioural events. Connect it first so everything else has data to work with.
1

Pick your platform

Enter your .myshopify.com domain and continue to Shopify to approve access. This is the OAuth path, so no API key is involved. See the Shopify guide.
2

Or connect from Integrations

The wizard offers Shopify, WooCommerce and Konimbo. Magento, Wix and WordPress connect from Integrations in the sidebar footer, not from the wizard. See Magento, Wix and the integrations overview.
3

Watch the back-fill

Existing customers import in the background. New customers arrive by webhook from then on.

How much order history back-fills

Order history back-fills so lifetime value and predictive scores have something to work with on day one. How far back depends on the platform. A single back-fill run reads up to 25,000 orders. A run that hits that ceiling is reported as incomplete rather than silently truncated.
Back-filled orders record purchase history and revenue. They deliberately do not enrol anyone into automations. A two-year-old order will not trigger today’s abandoned-cart flow.

2. Import contacts

If you have a list outside your store, upload it. Go to Contacts and choose Import, or use the Import contacts step in the wizard.
1

Upload

Drop a CSV, Excel (.xlsx or .xls) or tab-delimited file. The limit is 10 MB and 50,000 rows per file. Keep one header row at the top.You can also choose Import from Google Sheets and pick a spreadsheet from your own Google Drive. Nothing is shared publicly. This option only appears where the workspace has it available. See Google Sheets.
2

Map fields

Every upload routes through mapping. Senderz auto-detects common headers, including Shopify and Hebrew consent columns. Confirm the map before you start.A column that does not match anything can be turned into a new custom field from the same dropdown, or excluded with Don’t import this column. An excluded column is genuinely excluded.
3

Review

Check the parsed rows before committing. Rows are validated for address syntax, mail-server records and quality, which covers disposable domains, role addresses and duplicates inside the file. Valid and risky rows import. Rejected rows are counted and each one is given a reason.
4

Subscription

The final step decides consent, and it is a screen of its own. It is covered below.

The Subscription step

This is the fourth and last step, and it is the one most people miss. By default, imported contacts are not subscribed to anything. A row is opt-in only where the file itself carries a consent column that you mapped and that row has a truthy value in it. The step says so plainly: “No channel selected. Imported contacts stay unsubscribed and cannot be sent marketing.” You can override that per channel. Tick Subscribed to email, Subscribed to SMS, Subscribed to WhatsApp, or all of them, and every imported row is marked subscribed on the channels you chose.
Force-subscribing a whole file is a legal assertion you are making on those contacts’ behalf. Senderz requires an acknowledgement checkbox before it will accept it: “I confirm these contacts gave permission to receive marketing on the channels I selected.”Under Israeli law marketing needs recorded, explicit opt-in. Only tick a channel where you actually hold that permission. Selecting nothing is a valid answer and keeps the conservative default. See Consent and compliance.
Two rules hold whatever you choose:
  • An import never turns an opt-out back into an opt-in. A contact who unsubscribed stays unsubscribed, even if the file says otherwise and even with force-subscribe ticked. Withdrawing consent is theirs to reverse, through the preference centre.
  • A subscribe is dropped for a channel the contact has no address for. Ticking email on a phone-only file does not create unreachable subscriptions.
More detail on the whole flow is in Importing contacts.

3. Verify a sending domain

Marketing email must send from a domain you control, and the domain has to prove that through DNS.
1

Open Domains and senders

Go to Settings, then Domains & senders. The old /domains URL redirects here.
2

Add your domain

Press Add domain and enter the domain used in your From addresses, for example example.com. Senderz places its own MX record on a separate bounce subdomain, so your existing business email is untouched.
3

Publish the DNS records

Senderz generates the records and groups them:
  • Authentication. Proves ownership and signs your mail with DKIM.
  • DMARC. Tells inbox providers how to treat mail that fails authentication. Strongly recommended.
  • Tracking. Serves open pixels and click redirects from your own subdomain.
  • Return-Path. Optional, see below.
If your DNS provider is supported, Auto-add records writes them for you. Otherwise copy each one into your DNS panel.
4

Wait

A background check runs about once a minute. You do not need to press anything. When the required records resolve the domain flips to Verified and warmup starts on its own.

The custom Return-Path is optional

The Return-Path group adds an MX record and a TXT record on a bounce subdomain. It is off by default and it is not required to verify a domain. Some DNS panels cannot put an MX record on a subdomain at all. Requiring it would leave those merchants unable to send, so Senderz does not. With it off, bounces use the platform default and your SPF, DKIM and DMARC are unaffected. The setting reads “Use a custom Return-Path” and can be turned on later. The SPF record shown in that group is still required either way.

Add and confirm a sender address

Verifying the domain is not the last step. Each individual From address needs its own confirmation. In the Sender addresses card, add the local part of the address, for example info, on one of your verified domains. Senderz emails that mailbox a confirmation link. The address shows Awaiting verification until someone opens it, and it cannot send until they do. If the email bounced, the card shows Failed and offers Resend. This proves someone actually reads the mailbox, so replies and bounces land somewhere real.
Your DKIM signing key is generated inside AWS KMS and never leaves it. Signing happens at send time. See Domains and authentication.

Verification is not permanent

A verified domain is re-checked on the same background sweep. If its DNS records are later removed or changed, the domain is demoted after three consecutive failing checks, and that immediately blocks sending. Senderz emails the workspace owner when it happens, and again when the records come back. The three-strike delay exists so a single flaky DNS lookup cannot knock a healthy domain offline. If you are changing DNS providers, expect a gap.

4. Send your first campaign

Go to Campaigns and press New campaign. The wizard has five steps.
1

Channel

Name the campaign and pick where it sends: email, SMS or push.SMS is blocked here until you have an approved Sender name and enough credits. The step says which one is missing and links to it. See SMS and Sender IDs.
2

Audience

Pick one or more segments. Overlaps are counted once, and the step shows the number of unique recipients.Every workspace is seeded with Email subscribers, SMS subscribers and Push subscribers, each meaning everyone opted in to that channel. The one matching your campaign’s channel is selected for you if you pick nothing else. You can also exclude segments. See Segments.
3

Content

Start from the gallery, from your own templates, or create a new one. For email this opens the block builder in place. Set the subject line, the preheader, the From name and the From address here. Only verified sender addresses are offered.
4

Schedule

Three send modes:
  • Fixed time. Everyone receives it at the same moment.
  • Optimal time per recipient. Each contact is sent at the hour they most often opened in the last 90 days, inside a window you set.
  • Throttled or staggered. Recipients go out in percentage batches, staggered from the start time.
Israeli quiet hours and Shabbat are applied automatically to SMS and push. See Quiet hours and Shabbat.
5

Review

The review step runs a pre-send checklist and shows a desktop and mobile preview of the exact message. It names anything that would block the send, such as an unverified From domain, a sender address nobody has confirmed yet, an empty audience, or a send time that falls inside a blocked window.When the list is clear, press Send now or Schedule.
There is no test send inside the campaign wizard. To send yourself a test, open the template in the template editor and use Send test on the preview pane. It asks for a verified sender address to send from. See Templates.

If your workspace requires approval

A workspace on a paid plan can turn on Require approval before sending under Settings, then Workflow & Approval. With it on, editors, designers and viewers no longer see Send. The review step offers Submit for approval instead, with an optional note for the reviewer. Owners and admins are unaffected and can still schedule directly. Submitted campaigns wait in the approvals queue, reachable from the Approvals tab on the Campaigns page. An owner or admin other than the submitter can Approve, Reject or Request changes. Editing a campaign’s content after approval clears the approval and it has to be resubmitted.

5. Automate with a flow

Campaigns are one-off. Automations react to events for as long as they are live. Go to Automations and press New automation, or start from Browse library.
1

Set up the trigger

An automation has one trigger card, and it can hold several triggers at once. Nothing else unlocks until you save it. Pick something like abandoned cart or order placed. See Flow triggers.
2

Decide how often someone can enter

Three choices, set on the same panel:
  • Enter only once. A profile can enter a single time, ever.
  • Enter every time the trigger fires.
  • Enter again after a set time. You set the window.
The default is once, so pick deliberately. Re-entry cannot be applied retroactively to contacts who already ran through.
3

Add steps

The palette covers far more than messages:See Flow steps.
4

Publish

A message step is not required. A tag-only, list-only or webhook-only automation is valid and publishable.What Senderz does block is an automation that would do nothing: if it has message steps, they are all still drafts, and it has no action step, you are asked to set at least one step live first.
Publishing enrols matching contacts on every future trigger. Every send-time rule still applies: consent, suppression, frequency caps, quiet hours and Shabbat, and the SMS credit wallet.
To reach people who already qualified before you published, open the live automation and use Add past profiles. You choose the last 30 days, the last 90 days, or a date. Added profiles enter at the first step and can receive real messages, so read the warning on that dialog before you confirm. See Publish and monitor.

Next steps

Core concepts

The objects, the send pipeline and the gates every message passes.

Workspaces and roles

Who can do what, and how to work across several stores.

Segments

Build audiences from behaviour, consent, lists and predictive scores.

Deliverability

Domains, sender addresses, Sender names and warmup.

Consent and compliance

Israeli opt-in rules, STOP handling and quiet hours.

API reference

Events, transactional sends and webhooks.