In this article

• Objective

• User Benefit

• Inclusions

• Before you begin

  • What you'll need

• Steps

  • Vanity URL

    • We have TLS requirements, and we want Coconut to use the cert we provide

    • We have TLS requirements, we have our own certificate authority, and we are unable to provide the cert directly to Coconut

    • We don’t have TLS requirements, but we do have a CAA record; we’ll add a CAA for Let’s Encrypt

    • We don’t have TLS requirements, we do have a CAA record, but we will not add a CAA for Let’s Encrypt

    • We don’t have TLS requirements and we don’t have a CAA record

    • Vanity URLs and SSO

  • Custom no-reply notifications

    • Using a domain

    • Using a single email address

  • Google Tag Manager

• A sample setup workflow

  • Vanity URL

  • Custom no-reply notifications

  • Custom GTM tags

• A note on access and visibility

Objective

Configure Premium Branding to provide clients with an experience that aligns to your organization’s marketing requirements and increases brand awareness.

NOTE: Premium Branding is an add-on feature. Please connect with your Customer Success Manager to get started.

User Benefit

Premium Branding removes reference to Coconut in your implementation. This can increase user trust in your brand because booking flows reference your organization without mention of Coconut.

Inclusions

Premium Branding includes the following:

• Removal of the “Powered by Coconut” logo within the application

• Removal of Coconut’s cookie notice within the application

• Removal of Coconut’s privacy policy and terms & conditions (to be replaced with your organization’s materials)

• Replacement of the standard URL with a vanity URL that is determined by your organization

• Replacement of the email address that references Coconut in notifications to that of your organization

• The ability for your organization to use Google Tag Manager to access services outside of Coconut

NOTE: Premium Branding does not support the use of vanity URLs for Coconut Connect calls at this time.

One example of a Premium Branding inclusion: The "Powered By Coconut" logo does not display during the online booking process when Premium Branding is enabled

Before you begin

What you’ll need

Once you’ve kicked off the process for enabling Premium Branding at your organization, you’ll be asked for the following:

• The vanity URL CNAME your organization will use

• Your organization’s terms & conditions (these will replace Coconut’s in the client booking process)

• The email address or domain your organization wants to use to send custom no-reply notifications to your clients

  • Hot Tip! Coconut leverages Postmark for custom no-reply notifications; to help you decide which is best for your organization, please refer to their documentation

Also, if your organization will be leveraging Google Tag Manager to track activity across domains, you’ll also need to add these domains to your Client View Settings in Coconut. For more information on Google Tag Manager, please refer to their documentation.

Lastly, if your organization is using SSO, please refer to this section of our SSO setup article to determine which approach your organization will take and the steps required for each.

Steps

Vanity URL

The workflow for setting up a vanity URL at your organization will depend on your organization’s requirements. Please refer to the following scenarios to determine which applies to your organization and what next steps are required.

If your organization is using SSO, a step to add the new URL to your IDP is also required.

We have TLS requirements, and we want Coconut to use the cert we provide

No problem. Your organization will be asked to provide the cert. Coconut will complete the necessary steps and inform you when your vanity URL is ready for use.

We have TLS requirements, we have our own certificate authority, and we are unable to provide the cert directly to Coconut

Not a problem. Coconut will generate a CSR and share it with you. Your organization signs the CSR and then Coconut uses the cert that was generated when the CSR was created.

We don’t have TLS requirements, but we do have a CAA record; we’ll add a CAA for Let’s Encrypt

Coconut leverages Let’s Encrypt. Once your organization adds a CAA for Let’s Encrypt, the vanity URL will be ready for use. For more information on Let’s Encrypt, please refer to their documentation.

We don’t have TLS requirements, we do have a CAA record, but we will not add a CAA for Let’s Encrypt

Coconut will need to leverage different methods for setting up your vanity URL. Let your Implementation and/or Customer Success contact know asap that this scenario applies to your organization so that next steps can be discussed.

We don’t have TLS requirements and we don’t have a CAA record

In this scenario, no additional requirements are necessary to set up your organization’s vanity URL.

Vanity URLs and SSO

If your organization uses SSO, the vanity URL will need to be added to your IDP. For more information on integrating SSO with Coconut - and for links to documentation for common IDPs - please refer to this article.

Custom no-reply notifications

The workflow for setting up custom no-reply notifications will depend on whether your organization decides to use a domain or a single email address. Coconut leverages Postmark for custom no-reply notifications; to help you decide which is best for your organization, please refer to their documentation.

Using a domain

If choosing to send custom no-replies from a domain, the following workflow takes place:

1. Coconut generates a key, a DKIM, and CNAME (return path) DNS record, then sends these to your organization

2. Your organization adds the DNS records to your name server or DNS provider for the chosen domain

3. Coconut verifies the records and completes setup

Using a single email address

If choosing to send custom no-replies from a single email address, the following workflow takes place:

1. Your organization shares the email address to be used with Coconut

2. Coconut completes required setup steps

3. Your organization confirms the email address through a “sender signature” workflow from Postmark

Google Tag Manager

With Premium Branding, your organization can configure custom tags from Google Tag Manager in Coconut to access services outside of Coconut (for example, an ad tracking pixel).

For more information on using Google Tag Manager in Coconut and links to use cases, please refer to this article.

To leverage this functionality:

1. Within your organization’s instance of Google Tag Manager, configure the custom GTM tag

   • Hot Tip! For more information on configuring tags in Google Tag Manager, please refer to this documentation

2. In Coconut, from the navigation menu, click Settings

3. Click Client View

4. Navigate to Google Tag Manager Configuration

5. In Container ID, enter your GTM Container ID as found in Google Tag Manager

6. In Used Domains, enter the URL associated with the custom tag in Google Tag Manager

7. Click +Add Another and repeat as required for each custom tag

A sample setup workflow

The following is an example workflow for the fictitious Oceanscape Financial. To begin, Oceanscape has made the following decisions and shared the following requirements:

• The vanity URL will be a subdomain: bookings.oceanscapefinancial.com

• They have TLS requirements, and will provide Coconut with the cert they want to use for the vanity URL

• They will use a domain for custom no-reply notifications

Based on these choices and requirements, the following takes place:

Vanity URL

1. Oceanscape Financial creates a CNAME record with their domain register or name server that points the new vanity URL to the initial oceanscapefinancial.coconutcalendar.com URL

2. Oceanscape Financial shares the CNAME and cert with Coconut

3. Coconut completes required setup and notifies Oceanscape Financial when complete

4. Oceanscape adds the new vanity URL to their existing SSO application so that users can sign-in seamlessly

Custom no-reply notifications

1. Coconut generates a key, DKIM, and CNAME (return path) DNS record and shares these with Oceanscape Financial

2. Oceanscape Financial adds the info to their name server or DNS provider for the domain that will be used for custom no-reply notifications

3. Coconut verifies the records and completes setup

Custom GTM tags

NOTE: For additional details on Google Tag Manager, please refer to this documentation.

1. Oceanscape Financial creates a tag in their GTM account

2. Oceanscape Financial logs into Coconut and navigates to Settings>Client View>Google Tag manager Configuration

3. In Used Domains, Oceanscape Financial adds the URL associated with the tag they created in their GTM account

4. The update is automatically saved

A note on access and visibility

Admin users can make related SSO updates and GTM updates through Settings. Organizations may also require the support of their IT teams for steps related to CNAME and DNS updates.