Financial Services · Managed platform (HubSpot)

Marketing Automation

Marketing email that respects consent, unsubscribes and compliance review

Overview

What you are buying

Moraph resells, implements and runs HubSpot for financial institutions that want to market by email without losing track of consent. HubSpot holds contacts, subscription types and the lawful basis for each contact, and sends campaigns with working unsubscribe links. Moraph configures it for CAN-SPAM, GDPR and your compliance review process, keeps the configuration under change control, and checks campaigns against your rules before they go out.

The problem it solves

Marketing teams at banks, credit unions, lenders and advisers want to send timely campaigns, while compliance needs every message reviewed and every recipient's consent respected. In practice contact lists are exported and re-imported, unsubscribes from one system do not reach another, consent records for European contacts are incomplete, and approvals happen by email attachment. When a complaint or regulator asks why someone received a message, the answer is hard to reconstruct.

  • Unsubscribes and consent held in more than one place and not kept in step
  • No record of the lawful basis for contacts covered by GDPR or UK GDPR
  • Compliance review of marketing content done by email, outside the platform
  • Customer data shared with a marketing tool without clear limits on what is used

Who uses it

  • Marketing teams at banks, credit unions, lenders, wealth managers and advisers
  • Compliance and marketing review staff who approve communications
  • Privacy officers responsible for consent and data protection
  • Institutions with customers or prospects in the United Kingdom or European Union
  • Teams that already use HubSpot and need it governed

Requirements it supports

CAN-SPAM Act (15 U.S.C. 7701 et seq.) and the FTC CAN-SPAM Rule (16 CFR Part 316)EU General Data Protection Regulation (Regulation (EU) 2016/679) and UK GDPRUK Privacy and Electronic Communications Regulations 2003 (PECR)Gramm-Leach-Bliley Act privacy provisions and Regulation P (12 CFR Part 1016)FINRA Rule 2210 (communications with the public), for broker-dealersSEC Marketing Rule (Rule 206(4)-1 under the Investment Advisers Act), for registered advisers

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

HubSpot provides the platform, Moraph implements and runs it to your compliance rules, and your institution decides what is sent and to whom.

AreaMoraphHubSpotYour organization
LicensingResells the HubSpot subscription and manages seats and renewals with youSets subscription terms, editions and limitsAgrees the edition and seats and accepts the vendor's terms
Platform availabilityMonitors integrations and sending health and raises vendor support casesRuns the HubSpot service under its own service commitmentsNone
ConfigurationConfigures subscription types, consent settings, templates, forms and permissions to the agreed baselineProvides the configuration options and documentationApproves the baseline and every change to it
Identity and accessConfigures single sign-on where the edition supports it, and runs user access reviewsProvides user management and sign-in optionsDecides who holds which role and tells Moraph about leavers
Content and audiencesRuns pre-send checks and advises on configurationProvides the tools to build and sendWrites content, chooses audiences and approves every campaign
Consent and opt-outsConfigures consent capture and keeps opt-outs synchronized across connected systemsProcesses unsubscribes and stores consent recordsApproves consent text and decides the lawful basis
MonitoringWatches integration failures, bounce and complaint levels and sending healthMonitors its own service and sending infrastructureActs on content or audience issues raised by Moraph
Incident responseContains configuration or integration issues and supports your responseResponds to incidents in its own serviceLeads incident response and any customer or regulatory notification
Changes and updatesAssesses HubSpot product updates for effect on your configuration and applies approved changesReleases product changes on its own scheduleApproves configuration changes
Policy decisionsRecommends settings that support CAN-SPAM, GDPR and your review rulesNoneDecides marketing policy, consent approach and data use

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of HubSpot itself, which belongs to its vendor.

  1. Step 1

    Onboarding tracker

    Implementation runs through consent design, integrations and migration, with decisions waiting on your team in view.

    WorkstreamOwnerStatusWaiting on
    Subscription types and consent textMoraph and privacy officerApprovedNone
    CRM integrationMoraphTestingNone
    Contact migrationMoraphHeldDecision on 4,210 contacts without known consent
    TemplatesMarketing managerIn reviewCompliance reviewer
    Archive integrationMoraphNot startedArchive contact
    Implementation runs through consent design, integrations and migration, with decisions waiting on your team in view.
  2. Step 2

    Configuration baseline review

    Moraph checks the running configuration against the approved baseline and lists what needs a decision.

    Example Federal Credit Union (fictional) · Quarterly baseline review

    Baseline version
    v2, approved by compliance
    Subscription types
    6, all match
    Forms checked
    14
    Users with export rights
    3
    Differences
    2

    Differences found

    • Form on events page missing consent text for UK contacts
    • One user with publish rights not on the approved list
    Moraph checks the running configuration against the approved baseline and lists what needs a decision.
  3. Step 3

    Pre-send check

    Before a campaign goes to compliance, Moraph's checklist confirms the required elements and the audience.

    Campaign: Spring auto loan rates (fictional)

    Subscription type
    Rate and product news
    Audience
    18,240 contacts subscribed
    Sender and postal address
    Present
    Unsubscribe link
    Present
    Rate disclosure
    Missing APR footnote

    Checks

    • Excluded contacts unsubscribed from this type: 1,102
    • No contacts without a lawful basis in the EU or UK segment
    • All links resolve to approved pages
    Before a campaign goes to compliance, Moraph's checklist confirms the required elements and the audience.
  4. Step 4

    Campaign approval

    Each campaign's approval history is kept with it, from first draft to send.

    Spring auto loan rates (fictional)

    1. Draft built from approved templateMarketer
    2. Pre-send check: disclosure missingMoraph service engineer
    3. Disclosure addedMarketer
    4. Content approvedCompliance reviewer
    5. Send scheduledMarketing manager
    Each campaign's approval history is kept with it, from first draft to send.
  5. Step 5

    Opt-out synchronization

    Moraph watches that opt-outs reach every connected system, and works failures until they clear.

    ContactOpted out inSubscriptionCRMOther senderStatus
    Contact 50217HubSpot email linkAll marketingUpdatedUpdatedComplete
    Contact 50233CRM, by phoneRate and product newsSourceUpdatedComplete
    Contact 50241HubSpot preference pageEventsFailedUpdatedRetrying
    Moraph watches that opt-outs reach every connected system, and works failures until they clear.
  6. Step 6

    Monthly service review

    Each month Moraph reviews campaigns, consent, opt-outs and changes with your team and records decisions.

    Monthly service review · Example Federal Credit Union (fictional)

    Campaigns sent
    11, all approved
    Pre-send checks returned
    3
    Opt-outs processed
    642
    Sync failures open
    1
    Data subject requests
    2, completed

    For decision

    • Approve consent text for new events form
    • Remove publish rights from one user
    • Review HubSpot product update affecting forms
    Each month Moraph reviews campaigns, consent, opt-outs and changes with your team and records decisions.

Workflows

The principal workflows

  1. Capture consent

    HubSpot forms record what each contact agreed to, the subscription types they chose and, where GDPR applies, the lawful basis for processing. Moraph configures the forms, subscription types and consent text you approve.

    • Subscription types defined for each kind of communication you send
    • Consent text approved by your compliance and privacy teams
    • Forms record the subscription, the consent text shown and the time
    • Lawful basis recorded for contacts covered by GDPR or UK GDPR
    • Double opt-in enabled where your policy requires it
  2. Build and review

    Campaigns are built in HubSpot from approved templates, and Moraph's pre-send checks confirm the required elements are present before compliance approves the content.

    • Marketer builds the email from an approved template
    • Pre-send check confirms sender identity, postal address, unsubscribe link and subscription type
    • Audience checked so only contacts with the right subscription are included
    • Compliance reviewer approves or returns the content with comments
    • Approval and the approved version recorded with the campaign
  3. Send and honor opt-outs

    HubSpot sends to the approved audience, suppresses contacts who have opted out, and processes unsubscribes from every message. Moraph keeps opt-outs in step with your other systems.

    • Campaign sent or scheduled after approval
    • Unsubscribed and suppressed contacts excluded automatically
    • Unsubscribe requests processed by HubSpot from each message
    • Opt-outs synchronized with your CRM and other sending systems
    • Bounces and complaints recorded against the contact
  4. Govern and evidence

    Moraph reviews the configuration, data flows and consent records with your team each month, and produces the evidence needed for complaints, data subject requests and compliance reviews.

    • Monthly review of consent, opt-outs, approvals and changes
    • Data subject access and deletion requests handled through HubSpot's tools at your direction
    • Contact data fields reviewed against the agreed data minimization list
    • User access reviewed and leavers removed

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Marketer

Marketing specialist, digital marketing coordinator, campaign manager

Builds campaigns, forms and audiences within the approved templates and rules.

Sees

  • Contacts and lists within their team
  • Templates, campaigns and their review status
  • Campaign performance reports

Does

  • Builds emails from approved templates
  • Creates audiences from subscribed contacts
  • Builds forms using approved consent text
  • Responds to pre-send check and compliance comments

Cannot

  • Send a campaign without compliance approval
  • Change subscription types or consent text
  • Export contacts unless granted separately
Approvals
Every campaign they build is approved by a compliance reviewer before it is sent.
Notified about
Pre-send check results, approvals and returned campaigns.

Compliance reviewer

Marketing compliance officer, compliance analyst, registered principal

Approves or returns marketing content before it reaches customers.

Sees

  • Campaigns waiting for review and their pre-send check results
  • The approval history of every campaign
  • Templates and their required disclosures

Does

  • Approves or returns campaigns with comments
  • Approves templates and changes to them
  • Samples sent campaigns for review

Cannot

  • Approve a campaign they built themselves
  • Change platform configuration
Approvals
Their approval is required before a campaign is sent; template approvals may need a second reviewer under your procedure.
Notified about
Campaigns waiting for review.

Privacy officer

Privacy officer, data protection officer, chief privacy officer

Decides how consent is captured, which data is used and how data subject requests are handled.

Sees

  • Consent and lawful basis records
  • The list of contact fields synchronized into HubSpot
  • Data subject requests and their status

Does

  • Approves consent text and lawful basis settings
  • Approves the data fields synchronized into HubSpot
  • Directs access and deletion requests
  • Decides on contacts with unknown consent status

Cannot

  • Send campaigns
  • Change configuration outside the change process
Approvals
Approves consent, data use and data subject request outcomes.
Notified about
Data subject requests, consent configuration changes and contacts held for a consent decision.

Marketing manager

Head of marketing, marketing director, marketing operations manager

Owns the marketing program and is the day-to-day contact for the service.

Sees

  • All campaigns, reports and service reviews
  • Users and their roles
  • Change requests and their status

Does

  • Schedules approved campaigns
  • Raises change requests
  • Requests user additions and removals
  • Attends the monthly service review

Cannot

  • Send a campaign that has not been approved
  • Grant export rights without privacy officer approval
Approvals
Configuration changes they request are approved by compliance or privacy where they affect consent, content rules or data use.
Notified about
Approvals, change status, integration issues and service review packs.

Moraph service engineer

Moraph marketing platform engineer, Moraph service manager

Configures and operates HubSpot for you under approved changes.

Sees

  • Configuration, integrations and sending health
  • Campaigns for pre-send checks
  • Moraph service portal records for your service

Does

  • Runs pre-send checks
  • Applies approved configuration changes
  • Monitors and fixes integration and opt-out sync failures
  • Assesses HubSpot product updates
  • Runs access reviews and the monthly service review

Cannot

  • Approve or send campaigns
  • Change consent settings or data fields without approval
  • Export contact data except as directed for a migration or request
Approvals
Every configuration change needs your approval.
Notified about
Integration failures, sync failures, complaint levels and vendor notices.

Auditor (read-only)

Internal auditor, compliance tester, examiner (under temporary access)

Reviews campaigns, approvals and consent evidence without being able to change anything.

Sees

  • Campaigns sent and their approval history
  • Consent and opt-out reports
  • Change history and access reviews

Does

  • Reads and exports reports within scope, with each export logged
  • Requests specific evidence through the marketing manager or compliance

Cannot

  • Change, approve or send anything
  • Keep access after it expires
Approvals
Access is granted by compliance with a scope and an end date.
Notified about
Nothing by default.

Permissions at a glance

ActionMarketerCompliancePrivacyMktg managerMoraph opsAuditor
Build campaigns and audiencesOwn work onlyNo accessNo accessFullNo accessNo access
Approve campaign contentNo accessApprovesNo accessNo accessNo accessNo access
Schedule or send approved campaignsOwn work onlyNo accessNo accessFullNo accessNo access
Run pre-send checksView onlyView onlyNo accessView onlyFullNo access
Change subscription types and consent textNo accessApprovesApprovesNo accessFullNo access
Change synchronized data fieldsNo accessNo accessApprovesNo accessFullNo access
Export contactsNo accessNo accessApprovesOwn work onlyNo accessNo access
Handle data subject requestsNo accessNo accessApprovesNo accessFullNo access
Manage users and rolesNo accessNo accessNo accessApprovesFullNo access
View campaign and consent reportsOwn work onlyView onlyView onlyView onlyView onlyView only
View change and approval historyNo accessView onlyView onlyView onlyView onlyView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • No campaign is sent without approval from someone other than the person who built it, and the approval is kept with the campaign.
  • Consent text, subscription types and the data fields synchronized into HubSpot are changed only with compliance or privacy approval, through a recorded change request.
  • Roles map to HubSpot permissions and teams, configured with you during implementation; exporting contacts is limited to the roles you choose.
  • User access is reviewed with your marketing manager on a schedule you set, and auditors receive temporary read-only access with a defined scope and an end date.

Features

What it does

Subscription types

HubSpot lets contacts subscribe to and leave each type of communication separately, such as product news, rate alerts or events, and Moraph sets them up to match your programs.

Consent and lawful basis

HubSpot records the lawful basis for processing and the consent given for contacts covered by GDPR or UK GDPR, configured with the consent text your privacy team approves.

Unsubscribe handling

Every marketing email carries an unsubscribe link, and HubSpot stops sending to the contact for that subscription type, or all marketing email, once they opt out.

Opt-out synchronization

Moraph connects HubSpot with your CRM and other sending systems so an opt-out recorded in one is respected in the others.

Approved templates

Email templates carry your sender identification, postal address, required disclosures and unsubscribe footer, so marketers start from a compliant layout.

Pre-send checks

Moraph runs a checklist on each campaign before approval: sender details, postal address, subscription type, audience, disclosures and links. Automated checks may flag issues; your reviewer decides.

Compliance approval

Campaigns are routed to your compliance reviewer for approval before sending, using HubSpot approvals where your subscription includes them, with the approval kept with the campaign.

Data minimization

Only the contact fields agreed with your privacy team are synchronized into HubSpot; account balances, account numbers and other nonpublic financial details are kept out unless you approve a specific use.

Data subject requests

Access and deletion requests for contacts are handled using HubSpot's privacy tools, at the direction of your privacy team, with each request logged.

Team permissions

HubSpot user permissions and teams limit who can edit contacts, build emails, publish and export data, configured to your roles by Moraph.

Retention and archiving

Sent emails and their approvals can be passed to your communication archive, so marketing communications are kept with your other records.

Change management

Changes to subscription types, forms, integrations and permissions go through change requests your team approves, and are recorded.

Integrations

How it connects to your systems

Connects toHowWhat flows
CRMContacts and opt-outs synchronized with your CRM, including Moraph's managed CRM for Finance, using HubSpot's integrations or the APIs on both sides.In: agreed contact fields. Out and in: subscription status and opt-outs.
Core banking and digital bankingWhere approved, limited customer attributes such as product held or branch are passed to HubSpot for segmentation, without account numbers or balances.In: agreed customer attributes on a schedule.
Website and formsHubSpot forms embedded on your website capture subscriptions and consent.In: form submissions with consent and subscription choices.
Communication archiveSent marketing emails passed to your archive, including Moraph's managed Communication Archiving, for retention and supervision.Out: sent emails and their metadata.
Identity providerStaff sign in through your identity provider where your HubSpot edition supports single sign-on.In: user identity for sign-in.
Moraph service portalChange requests, pre-send check results, integration alerts and monthly service reviews tracked in Moraph's service portal.Out: service records, check results and review reports.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Single sign-on

Your staff sign in through your identity provider where your HubSpot edition supports it, so your password and multi-factor policies apply; Moraph's service portal always uses your identity provider.

Role-based access

HubSpot permissions limit who can edit contacts, publish emails and export data, and exporting contacts is restricted to the roles you choose.

Data minimization

Nonpublic personal financial information is kept out of HubSpot unless your privacy team approves a specific field for a specific use.

Moraph staff access

Moraph engineers use named accounts with the permissions you approve, and their access is reviewed with yours.

Audit trail

Moraph's service portal records every change request, approval and pre-send check, alongside the activity history HubSpot keeps.

Audited operations

Moraph is SOC 2 Type II and ISO/IEC 27001 audited company-wide, and its service records are hosted in the United States, United Kingdom or Australia region you choose. HubSpot's own data hosting follows its available regions and terms.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

10 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Campaigns

Campaigns and approvals

For marketing manager, compliance reviewer, auditors

Every campaign sent, its subscription type, audience size, approver and approval date.

Break down by
Campaign, Subscription type, Approver, Period
Delivered as
Service portal view; CSV and PDF export
Used for
Evidencing that each message was reviewed before it was sent.

Pre-send check results

For marketing manager and compliance reviewer

Checks run on each campaign, items flagged and how each was resolved before approval.

Break down by
Check item, Campaign, Marketer, Period
Delivered as
Service portal view; monthly service review pack
Used for
Finding recurring content issues to address in templates or training.

Bounces and complaints

For marketing manager

Bounces, spam complaints and unsubscribes per campaign, from HubSpot's email reporting.

Break down by
Campaign, Subscription type, Period
Delivered as
HubSpot reports; monthly service review pack
Used for
Protecting sender reputation and spotting audiences that should not have been mailed.

Consent

Subscriptions and opt-outs

For marketing manager and privacy officer

Subscriptions gained and lost by type and source, and opt-outs from all marketing email.

Break down by
Subscription type, Source, Period
Delivered as
HubSpot reports; CSV export
Used for
Understanding what contacts want and evidencing that opt-outs are honored.

Lawful basis gaps

For privacy officer

Contacts in the EU or UK, or otherwise in scope of GDPR, without a recorded lawful basis, and how they were handled.

Break down by
Country, Source, Status
Delivered as
Service portal view; monthly service review pack
Used for
Keeping marketing to GDPR-covered contacts on a recorded legal footing.

Opt-out synchronization

For marketing manager and privacy officer

Opt-outs passed between HubSpot and connected systems, failures and how long each failure took to clear.

Break down by
Source system, Target system, Status, Period
Delivered as
Service portal view; weekly email
Used for
Making sure an opt-out in one place is respected everywhere.

Data subject requests

For privacy officer, auditors

Access and deletion requests received, actions taken in HubSpot, and completion.

Break down by
Request type, Status, Period
Delivered as
Service portal view; PDF export
Used for
Evidencing that requests were handled as directed.

Governance

Configuration change history

For compliance, privacy officer, auditors

Every change to subscription types, consent settings, forms, integrations and permissions, with requester and approver.

Break down by
Area, Approver, Period
Delivered as
Service portal view; CSV export
Used for
Showing that consent and content controls were changed only with approval.

User access review

For marketing manager, compliance

Users, their roles and export rights, and changes made at each review.

Break down by
Role, Team, Review cycle
Delivered as
Service portal view; PDF export
Used for
Keeping access to contact data limited to the people who need it.

Monthly service review

For marketing manager, compliance and privacy

Campaigns, checks, consent, opt-outs, changes, vendor updates and decisions needed, for the month.

Break down by
Month, Area
Delivered as
PDF pack and review meeting
Used for
Running the service with your team and recording decisions.

Exports, access and evidence

  • Campaign performance and subscription reports come from HubSpot itself; checks, approvals, changes and reviews come from Moraph's service portal.
  • Reports can be exported to CSV, and governance reports to PDF for compliance files and committee packs.
  • Sent communications and their approvals can be passed to your communication archive for retention and supervision.
  • Reports respect each viewer's role: marketers see their own campaigns, while compliance and privacy see the whole program.
  • Auditors can be given read-only access to reports within a defined scope, and exports are recorded.

Deployment

Where and how it runs

New HubSpot account

A HubSpot account provisioned through Moraph and configured to the agreed baseline.

Existing HubSpot account

Your existing HubSpot account brought under management after a baseline review of consent, permissions and integrations.

Data hosting

HubSpot data is hosted in the HubSpot data center region available for your account under HubSpot's terms; region choice is confirmed during discovery.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Discovery

We review your marketing programs, review procedures, consent practices and existing tools, and agree the configuration baseline. We need your marketing and compliance procedures and a privacy contact.

Consent design

Subscription types, consent text, lawful basis settings and double opt-in rules are designed with your compliance and privacy teams.

Data and integrations

The contact fields to be synchronized are agreed and minimized, and integrations with your CRM, website and archive are built and tested.

Contact migration

Existing contacts and their opt-outs are imported, with contacts lacking a known consent status held back for your decision.

Templates and review

Approved templates and the compliance approval process are set up, and marketers and reviewers are trained.

Transition to managed service

The service moves to steady-state operations: pre-send checks, integration monitoring, change management and monthly service reviews.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not HubSpot. Moraph resells, implements and operates the platform; HubSpot develops it and runs its service.
  • HubSpot's own service commitments, product roadmap and any outages apply. Moraph does not change them.
  • Licences are subject to HubSpot's terms, which you accept as part of the purchase. Some features, such as approvals, audit logs and single sign-on, depend on the edition you license.
  • Moraph does not write or approve your marketing content. Your institution decides what is sent and approves it.
  • Pre-send checks confirm the elements Moraph has agreed to check; they are not legal advice and do not replace your compliance review.
  • The service covers email marketing. Text messages and calls bring separate rules, such as the TCPA, and are not configured unless agreed separately.
  • Opt-out synchronization works with systems that can be integrated; opt-outs held in systems without an integration must be handled by your process.
  • HubSpot is not a records archive. Retention of sent communications relies on your archive.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Walk through how a contact's consent and subscription choices are recorded and shown
  2. Unsubscribe from a test email and check the opt-out reaches your CRM
  3. Review a pre-send check on one of your own past campaigns
  4. Confirm which contact fields would be synchronized and which kept out
  5. Check who could export contacts under the proposed permissions
  6. Read the responsibilities table with your compliance and vendor management teams

Questions

Frequently asked questions

Does this make our marketing compliant?

It gives you a platform configured to support CAN-SPAM, GDPR and your review rules, and evidence of consent, opt-outs and approvals. Whether a campaign is compliant remains your institution's judgment, made by your reviewers.

Will customer account data be sent to HubSpot?

Only the fields your privacy team approves. By default account numbers, balances and other nonpublic financial details are kept out.

We already use HubSpot. Can Moraph run it?

Yes. Moraph starts with a baseline review of consent settings, permissions and integrations, agrees what needs fixing, and then operates the account under the same change and reporting model.

How is it priced?

The HubSpot subscription is resold under HubSpot's terms, with Moraph's implementation and managed service priced separately, usually by the edition, number of contacts and integrations in scope. See Working with Moraph for what drives a quotation.

Can it handle broker-dealer or adviser review requirements?

The approval step can be configured so a registered principal or your compliance reviewer approves content before it is sent, and approvals can be passed to your archive. Your firm remains responsible for meeting FINRA and SEC requirements.

Does it cover text messages?

Not by default. Text and call marketing have separate consent rules, and any such channel is scoped separately.

Next steps

Evaluate Marketing Automation

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Marketing Automation guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Marketing Automation support guide.