Skip to main content

Hosting Types

JUNE supports various hosting options for publishing content such as emails, landing pages, and assets.

Anni Wild avatar
Written by Anni Wild
Updated this week

When publishing landing pages or sending email campaigns or automated emails, you need to select and set up a hosting type. The following options are available:

1. JUNE Cloud

Standard hosting via our platform (yourdomain.my-june.com)

Content is hosted directly through the editor's infrastructure. This option is the easiest to set up and ideal for customers without their own hosting solution.

Advantages:

  • No external setup required

  • Automatic integration with all editor functions

2. SFTP

Upload via a secure file transfer server

Allows content delivery via the SFTP protocol (Secure File Transfer Protocol), e.g., to a customer's server. To set it up, you need your SFTP/FTP information:

  • Name

  • URL

  • Directory

  • Host

  • Port

  • Username

  • Password

  • (Private Key)

This information is usually found in the customer administration system (KAS) of your hosting provider.

Typical use:

  • Companies with their own hosting structure or internal processes

  • Increased security requirements

3. Episerver

Integration with the content management system (CMS) Episerver

Content can be published directly in Episerver, commonly used in more complex Digital Experience Platforms. To set it up, you need the following information from your Episerver:

  • Name

  • URL

  • Client ID

  • API User

  • API Key

  • Recipients List

  • Sender Email

  • Sender Name

  • ReplyTo Name

Especially suitable for:

  • Companies with CMS-based web structures

  • Headless CMS workflows

4. Salesforce Marketing Cloud

Direct publishing in SFMC

Content (e.g., email templates) is transferred to the Salesforce Marketing Cloud and managed there. To set it up, you need the following information from your Salesforce Marketing Cloud:

  • Name

  • URL

  • Client ID

  • Client Secret

  • Client API Path

Advantage:

  • Seamless integration into existing SFMC workflows and journeys

5. Webhook

Real-time transmission via HTTP Webhook

With every change or publication, a webhook is triggered that forwards content or information to another system. To set it up, you need the following information:

  • Name

  • URL

  • Webhook Publish

  • Webhook Invalidate Cache

  • Webhook Delete

  • Username

  • Password

  • Advanced

    • Curl Options Resolve

    • Curl Options Proxy

    • Curl Options Useragent

    • Curl Options HTTP Header

Use cases:

  • Integration into automation pipelines

  • Connection with third-party platforms (e.g., internal APIs)

6. Shopify

Direct hosting in Shopify environments

For e-commerce customers, content (e.g., landing pages or assets) can be used or linked directly in the Shopify store. To set it up, you need the following information from your Shopify:

  • Name

  • URL

  • API Token

  • Client API Path

Benefits:

  • Ideal for personalized campaigns in the shop environment

  • Easy integration into Shopify themes

7. Amazon S3

Storage in Amazon S3

Content is stored in Amazon's S3 storage service. To set it up, you need the following information:

  • Name

  • Bucket Name

  • Region

  • Access Key

  • Secret Key

Suitable for:

  • Companies with existing AWS infrastructure

  • Scalable and secure content delivery

Did this answer your question?