Marketing Growth
Marketing Growth gives a workspace the tools to collect opted-in subscribers, build audiences, send newsletter campaigns, and measure what happens when campaign traffic reaches the public site.
The console owns setup and operations. The sites app owns the customer-facing landing, confirmation, unsubscribe, preference, consent, and tracking behavior.
Surface Map
Sender setup
Console surface: Marketing > Sender setup
Public-site effect: Authenticates the workspace sending domain and provides the required mailing address for email footers.
Subscribers
Console surface: Marketing > Subscribers
Public-site effect: Tracks opt-in status, suppressions, unsubscribes, bounces, complaints, and subscriber tags.
Segments
Console surface: Marketing > Segments
Public-site effect: Creates reusable audiences from subscriber attributes and tags.
Campaigns
Console surface: Marketing > Campaigns
Public-site effect: Composes, tests, schedules, sends, and reviews newsletter campaigns.
Website content
Console surface: Website, Stories, Forms, Discovery
Public-site effect: Provides landing pages, signup entry points, campaign URLs, and short links.
Privacy and legal
Console surface: Settings > Privacy and Legal
Public-site effect: Controls consent posture, cookie categories, policy language, and customer expectations.
Console surface: Settings > Integrations > Google Analytics and Google Ads
Public-site effect: Measures landing traffic and conversion events when consent allows.
Marketing is an operator-controlled feature. If the Marketing pages are not available for a workspace, confirm that the newsletter feature is enabled and that the operator has the right admin access before troubleshooting deeper.
Sender Setup
Every workspace should complete sender setup before the first campaign.
Sender setup includes:
- Provisioning the sending identity for the workspace domain.
- Publishing the DNS records exactly as shown.
- Rechecking DNS until the sender is verified.
- Saving the physical mailing address required in marketing email footers.
- Confirming the from address and reply handling are appropriate for the workspace.
Campaign sending should not begin until the sender domain is verified. A pending sender can still be used for drafting and test planning, but not for live audience delivery.
Subscribers
Subscribers represent people who have opted into marketing email for the workspace.
Subscriber statuses:
Pending
Meaning: The confirmation email was sent, but the subscriber has not confirmed.
Operator action: Resend confirmation only when the customer expects it.
Active
Meaning: The subscriber has confirmed and can receive campaigns.
Operator action: Include in all, tag-based, or saved-segment audiences.
Unsubscribed
Meaning: The subscriber opted out and remains suppressed.
Operator action: Do not manually resubscribe without a new opt-in signal.
Bounced
Meaning: Delivery failed hard enough to suppress the address.
Operator action: Review address quality before attempting contact through another approved path.
Complained
Meaning: The recipient reported the email as spam.
Operator action: Leave suppressed and review campaign quality, source, and consent.
Tags are operator-managed audience building blocks. Use tags for stable business categories such as vip, spring-event, consultation-lead, or wholesale, not for one-off notes that should live on a customer record.
Segments
Segments are saved audience filters. They help operators reuse a target group across campaigns without rebuilding the same rules each time.
Segments can match subscriber fields such as:
- Tags.
- Status.
- Email.
- Name, when available.
A segment should have a business-readable name and a clear purpose. Good segment names tell the operator who will receive the message, such as “Active VIP subscribers” or “Pending consultation leads”.
Campaigns
Campaigns move through a simple lifecycle.
- Draft
- Editable campaign that has not been scheduled or sent.
- Scheduled
- Editable campaign queued for later delivery.
- Sending
- Campaign delivery is in progress.
- Sent
- Campaign is delivered and becomes read-only.
- Canceled
- Scheduled campaign was canceled before send.
- Failed
- Delivery failed and needs investigation.
A campaign contains:
- Internal campaign name.
- Subject line.
- Preview text.
- Body content.
- Audience selection.
- Optional scheduled send time.
- Test-send and final send actions.
Supported personalization fields are first_name, last_name, email, business_name, and unsubscribe_url. Use unsubscribe_url or another clear unsubscribe link in every marketing email.
The send path is guarded. A campaign needs a subject, at least one recipient, an unsubscribe link, no unresolved personalization fields, and a verified sender domain before it can be sent.
Public-Site Implications
Marketing operations are not only a console workflow. They also affect what customers see and what they consent to.
Public-site surfaces include:
- Landing pages, stories, forms, product pages, booking pages, and short links used by campaigns.
- Newsletter signup entry points and confirmation links.
- Unsubscribe links that require a deliberate confirmation action.
- Email preference pages that can opt the customer out of one email type or all customer-facing emails.
- Cookie consent controls for analytics and marketing categories.
- Privacy, terms, and policy content that explains data use.
Confirmation and unsubscribe links should be treated as customer-facing legal paths. Do not hide them, bypass them, or replace them with a manual console-only process when the customer has a valid email link.
Google Analytics And Ads
Google Analytics and Google Ads measure different parts of the growth loop.
Google Analytics
Best use: Page views, landing page behavior, campaign traffic, and content performance.
Consent dependency: Analytics consent must allow analytics storage.
Google Ads
Best use: Paid campaign attribution and configured conversion events.
Consent dependency: Marketing consent must allow advertising signals, unless an approved advanced consent mode is used.
Operational rules:
- Use production landing URLs in ads and campaign links.
- Keep UTM parameters on landing pages, but do not put sensitive tokens in ad URLs.
- Verify Google tags load only when the workspace consent posture allows them.
- Global Privacy Control should suppress advertising signals.
- Booking confirmation conversion events should not send booking tokens or sensitive query parameters to Google.
- Do not turn on paid traffic until the destination page, consent banner, and conversion path pass QA.
Ownership Rules
- The console is the source of truth for campaigns, subscribers, segments, sender setup, and integrations.
- The public site is the source of truth for what customers experience after clicking a campaign link.
- Consent and unsubscribe state must be honored even when an operator wants a broader audience.
- Bounces and complaints are deliverability signals, not just reporting noise.
- A campaign is not launch-ready until both the email and the destination path are tested.