Skip to main content

Custom Domains

Rather than referencing system.spektrix.com throughout your sites integration, we have to use a custom domain that points directly to Spektrix. Rather than referencing system.spektrix.com throughout your sites integration, we have to use a custom domain that points directly to Spektrix.

In addition to keeping the customer on your domain, this will also ensure that the Spektrix cookies used in the booking pathway are consistently set as First Party. This avoids any issues with Safari’s Intelligent Tracking Protection (ITP) and other tracking prevention measures found in browsers. You can find out more about cross-domain issues for online customers booking with Safari here.

The following outlines the steps to activate your custom domain with Spektrix.

warning

You need to replace all references to system.spektrix.com with the custom domain, otherwise the customer’s cookie will not be shared across the journey which will lead to an empty basket and/or CORS errors. This includes iframes, web components and API calls.

Choosing the Subdomain​

We would suggest setting this up as a subdomain of tickets. For instance tickets.myvenue.com. If tickets is already in use we will be able to verify another custom domain.

Configuration​

CNAME​

On the chosen subdomain, a CNAME record needs to be added that points to customers.spektrix.com

Your new record might look like the sample entry below. Sample CNAME Record

CAA Records​

On your main domain myvenue.com, if you currently have any Certification Authority Authorization (CAA) records, you will need to add CAA records for the following authorities:

  • digicert.com
  • letsencrypt.org

If you already use one of these authorities, please add the remaining one. You do not need to duplicate your CAA records.

tip

If you do not currently have any CAA records on your domain, you do not need to add any of the above records. Please continue to the next section.

Multiple Domains​

If you have multiple websites running from separate domains on one Spektrix system (for example a myfirstvenue.com and mysecondvenue.com) then you can set subdomains for each site.

note

Please note that this will mean that customers will now have separate sessions / baskets across both sites.

Inform Spektrix​

Once the above steps have been completed please get in touch with Spektrix at support@spektrix.com providing:

  • the Spektrix clientname
  • the new custom domain
  • any deadlines we need to be aware of

We will then inform you and/or the client when we have completed the remainder of the setup. From here you will be able to proceed with the next step.

Updating Your Integration​

warning

Do not complete the following steps until the above setup has been confirmed by Spektrix support.

If you currently integrate with Spektrix, please do not update any of your references from system.spektrix.com to your custom subdomain until we have confirmed that all points of the domain set up and redirects are in place.

All the references need to be updated at once - if you have some pages running on your website on system.spektrix.com and some on tickets.myvenue.com then the customer’s session will not be shared across those pages. This will result to the customer getting an empty basket, even if they have added items to their basket.

Once your subdomain is ready, the below explains where this should be used and any additional considerations that may need to be made.

Iframes​

Our standard url structure for our Iframes references system.spektrix.com. This can be replaced with your custom domain.

tip

Don’t forget your standalone Iframes such as myaccount.aspx or LoginLogout.aspx. For a reminder of all the iframes you could be using check our Iframe Reference List

Spektrix Scripts​

Throughout your integration, there are additional scripts that can be used to add additional features to the purchase path. These scripts are hosted on the client’s Spektrix system, and can now be referenced using your chosen custom domain.

These are used to operate:

integrate.js​

As part of this update, integrate.js has replaced resizeiframe.js and includes the controls for resizing of Iframes. This should be referenced in the <head> of your site using the below:

Please ensure you replace subdomain.domain.com and clientname with your custom subdomain and the Spektrix client name you are integrating with:

<script
	type="text/javascript"
	src="https://subdomain.domain.com/clientname/website/scripts/integrate.js"
></script>

When moving to your custom domain, you should remove any references to resizeiframe.js - if you don’t do this then you’ll see that customers on Safari will be ‘bounced’ via system.spektrix.com the first time they load resizeiframe.js in a session.

For more information around Resizing Iframes click here.

Web Components​

If using our Web Components, a new attribute will need to be added inside the html of the component.

custom-domain=”subdomain.domain.com”

For example,

<spektrix-donate
	client-name="{client-name}"
	fund-id="{fund-id}"
	custom-domain="{subdomain.domain.com}"
>
</spektrix-donate>

API​

If using our API to add and remove items to baskets (such as a custom ticket purchase path) then you will need to update your client-side calls to reference your custom domain. Without doing this, these client-side calls will not share a session with the iframes on tickets.myvenue.com.

Your server-side calls (e.g. for populating a Content Managements System’s event database) can continue to use system.spektrix.com.

If using Spektrix Link, you or the client need to enter the custom domain URL in the Spektrix Link Configuration Console, as per instructions. The custom domain needs to be set up in addition to the customer facing subdomain that will appear in the address bar.

Last updated on by Nina Primeraki