Blackthorn | Events supports custom domains. Currently, we cannot take over a root domain since that has to be forwarded to our service via CNAME.
You can have a subdomain on your main domain with the event slugs, such as subdomain.yourdomain.com/event-slug.
Example of one of our customers:
Note: We will only set this up for your organization if you're already live with our product as there is significant work on our end to set this up (helps us manage internal resources).
Note: Only use one domain per Salesforce Organization
This includes Sandboxes and any secondary organizations that may be configured.
Here's what we need from you:
- Available domain and subdomain
Choose a subdomain or domain and provide this information to us (Blackthorn). Please submit this information at least 48 hours before you plan on using this custom event domain.
We'll then provide you with a CNAME endpoint which you will update in your DNS records.
Lastly, we will generate your SSL Cert and enable this feature in your org. After this has been completed, please update the following objects and fields to use your customized events URL. Note: All communication and email templates should be updated to use these customize urls.
- Create a formula text field 'Custom Event Group URL' with the following formula on the Event Group Object:
“domain/” & $Organization.Id & "/g/" & conference360__Key__c
- Create a formula text field ‘Custom Event Page URL' with the following formula on the Event Object:
SUBSTITUTE(conference360__Event_Page_URL__c , “events.blackthorn.io", "domain")
- Create a formula text field ‘Custom AttendeeLink' with the following formula on the Attendee Object:
SUBSTITUTE(conference360__AttendeeLink__c, “events.blackthorn.io", "domain")
Update your Events Domain from Setup > Security > Remote Site Settings > Events_Domain.
Finally, please make sure to update the
Platform Domainfield located within Custom Settings > Blackthorn | Events Settings to match the Remote Site URL.
If you still have questions following the documentation please contact Blackthorn Support. We're happy to help!
What about SSL?
The reason for the way this is set up is from our Platform as a Service provider, Heroku. Heroku uses an Automated Certificate Management called Server Name Indication This replaces traditional SSL certificates, that require more setup and maintenance.
The validation mechanism Heroku uses for this type of SSL is through the existence of a CNAME record with a specific value pointing to Heroku. Removing that CNAME record detaches the SSL from the (sub)domain also. So the control is still guaranteed to be on the domain owner's side.
We still offer support for traditional Certificate Authority generated SSL certificates. Our customers can purchase their own and supply us a certificate, but this will require continued annual maintenance
Updated 4 months ago