10 Klaviyo Settings You Need to Get Right

Which Klaviyo settings actually affect revenue and deliverability?

The settings with the most operational leverage decide who receives a message, which sender identity the mailbox sees, what permission is recorded, which onsite events arrive, and whether the team can trust its measurement. This is a ZHS launch checklist, not a claim that every platform default is wrong for every brand.

Before changing anything, capture the current setting, owner, reason, test case, and rollback path. Klaviyo's interface and account options change; verify the current label in the account and against the relevant help documentation before a production change.

The short version

Review recipient determination, branded sending, list consent, billing, site tracking, attribution hygiene, anonymous visitor behavior, Shopify events, consent pages, and UTM conventions. Then run a test profile through the paths that matter. A setting is only useful when its behavior is documented and verified in the live account.

Checklist

ZHS Klaviyo settings launch gate

Campaign audience behavior is chosen deliberately and tested with a changing segment
Branded sending status is verified after relevant DNS or sender-infrastructure changes
Each list has an explicit opt-in and consent decision
Plan usage and message volume have an owner and review cadence
Email-to-site tracking is tested from a real email click
Attribution definitions and exclusions are documented before reporting results
Anonymous visitor collection has a consent and privacy review
Shopify app embed and onsite events are verified on a test profile
Consent and preference pages match the brand and the actual permission choices
UTM naming is consistent across email, SMS, analytics, and reporting

Complete this gate before scaling campaign volume or depending on lifecycle reporting.

1. Should campaign recipients be determined at send time?

For a future campaign aimed at a changing list or segment, ZHS usually enables recipient determination at send time. That gives the campaign a fresh audience snapshot close to delivery. It is a poor fit only when the offer, experiment, or operational process requires a frozen cohort.

Do not assume the behavior is identical for every timezone or send strategy. Schedule a harmless internal test, add and remove a test profile after scheduling, and confirm the final recipient behavior before using the setting on an important campaign.

2. Do you need a branded sending domain in Klaviyo?

Yes. Use a branded sending domain and make its verification status a launch gate. A dedicated, authenticated sender identity gives mailbox providers a clearer relationship between the message and your brand; it is not a promise of inbox placement by itself.

Verify the domain when DNS, sending infrastructure, or ownership changes, and keep a recurring check in the operating calendar. If the status changes, pause the assumption that the account is ready to scale and investigate before increasing volume.

3. Should you use single or double opt-in in Klaviyo?

Choose the consent model deliberately. Single opt-in reduces the steps between signup and subscription. Double opt-in adds a confirmation step that can improve confidence in the address and permission record. Neither choice is universally correct: legal requirements, acquisition source quality, sender reputation, geography, and the brand's risk tolerance all matter.

The ZHS default is to document the rationale per list, preserve the consent timestamp and source, and test the full signup-to-welcome path before scaling. Do not switch an existing list solely to chase faster growth or a perceived deliverability fix.

Single opt-in

Fewer steps between form completion and subscription
Requires a clear consent mechanism and monitored list quality
Test that the welcome path records the expected permission state

Double opt-in

Adds a confirmation step before marketing permission is recorded
Can be appropriate for a higher-risk acquisition source or market
Measure confirmation completion and downstream engagement before keeping it

4. How do you avoid surprises in Klaviyo billing?

Give one person ownership of plan usage, active-profile definitions, and messaging volume. Compare the current account's included usage and upcoming sends with the commercial plan before a high-volume launch. If the account will cross a tier, decide whether the right response is list hygiene, a sending-plan change, or a different launch sequence.

This is an operating review, not a universal cost warning. Keep a short decision log so a future team member can see why a profile was suppressed, retained, or sent.

5. Should email-to-website tracking be enabled?

Enable and test email-to-website tracking when the brand needs to connect an email click to on-site behavior. Send a test email to a controlled profile, click a tagged link, and confirm that the expected on-site activity appears on the right profile without creating a duplicate identity.

If your storefront, consent implementation, or privacy configuration prevents the expected behavior, resolve that architecture question before treating a flow report as complete.

6. How should you set attribution and reporting exclusions?

Start with a written reporting definition: what counts as a conversion, which channel receives credit, what attribution window applies, and which message types are excluded. Use the same definition in the dashboard, client reporting, and experiment readout so a gain in one article cannot become a different benchmark elsewhere.

Apple Mail Privacy Protection can create opens that do not represent a deliberate human open. Where the account supports it, identify those opens and avoid making high-stakes engagement decisions from them alone. Review bot-click handling and attribution settings in the current account before changing historical comparisons.

7. Should you enable anonymous visitor tracking?

Enable it only after the privacy, consent, and identity implications are understood for the brand's markets and storefront. The operational value is the ability to associate later-known visitors with earlier onsite behavior; the operational risk is assuming that every anonymous event is a marketable profile.

Test the path with a controlled browser and profile. Confirm when the identity resolves, which events are retained, and which consent checks still apply before using the data in a flow.

8. How do you verify Shopify onsite events and the app embed?

Do not treat an enabled toggle as proof that browse, product, cart, and order behavior is usable. In a controlled browser session, visit a product, add an item to cart, complete an allowed test purchase, and inspect the resulting Klaviyo profile activity. Confirm that the event names, timestamps, product properties, and identity match the customer record you expect.

Then preview every dependent segment and flow against that test profile. If the event is missing, duplicated, or tied to the wrong profile, stop and fix the connection before building more automation on top of it.

Make the preference, subscribe, unsubscribe, and confirmation experiences accurate before making them attractive. The copy should explain the customer's choices, use the correct brand identity, and send the chosen permission state to the expected list or profile.

Test each page with a controlled profile. Confirm that a subscriber can change preferences or unsubscribe, the data updates correctly, and the next lifecycle message honors that state.

10. Should you turn on global UTM tracking in Klaviyo?

Use a consistent UTM convention if analytics and campaign reporting need to distinguish email and SMS traffic. Set the source, medium, campaign naming rule, and owner before enabling automatic parameters, then verify links from an email and an SMS against the analytics destination.

Global settings reduce manual variation, but they do not replace governance. Review a live sample whenever templates, redirects, storefront domains, or reporting definitions change.

Should you turn Smart Sending on or off in Klaviyo?

Smart Sending skips a profile that has been messaged recently, so treat it as a message-level collision decision rather than an account-wide ideology. Keep it enabled where promotional overlap would make the customer experience worse; disable it only when a specific message must arrive as part of a verified sequence and another collision control already exists.

For each important flow message, record the intent, the Smart Sending choice, the competing messages, and the test result. Revisit the decision when campaign cadence or the flow architecture changes.

What are the most common Klaviyo settings mistakes?

The common failure is not a single bad toggle. It is an undocumented setting that no one has tested against a real customer path.

Audience behavior is assumed. A scheduled campaign uses a different recipient snapshot than the team expects.
Sender identity is not monitored. Domain status changes after DNS or infrastructure work and nobody catches it.
Consent logic is chosen by habit. A list's opt-in decision, source, and downstream behavior are not documented.
Tracking is declared live without a test. Events are missing, duplicated, or mapped to the wrong profile.
Reporting mixes definitions. Attribution windows, MPP treatment, and exclusions change from one readout to the next.
Customer paths collide. Smart Sending and flow logic have not been reviewed against the campaign calendar.

Fix the underlying operating gap, document the decision, and rerun the test profile. That produces a setup the team can maintain instead of a collection of settings nobody trusts.

Get Expert Help

ZHS can audit the account configuration, document the decisions, and test the customer paths that depend on them. The handoff includes a launch gate and evidence, not just a list of toggles.

See our pricing | Apply to work with us