Use * syntax for faster search

Table of Contents


Overview

Buzz supports extensive white labeling capabilities, where the Buzz UI appearance can be changed and also set behind a CNAME, such as bidder.customername.com. In order to white label a Buzz instance, please follow the steps outlined below. 

UI Settings

The sections of the UI that can be rebranded are labeled in the screenshot and detailed in the table below. Share the system fields you want to white label with your Beeswax representative. If needed, these settings can also be applied across all accounts through a configuration that can be made by Beeswax Support.

API Note: These changes cannot be made via the REST API. 

System FieldValueNumbered label on imageEffect
Main HeaderHex colour string                1Color for main navigation bar
Button and LinksHex colour string                2Color for table header and primary button
TextHex colour string                4Color for navigation bar text
Custom Logo ImageURL string                5Image to use for website icon / favicon
LogoURL string                6Image to use for logo
Page TitleString                7Browser page title

Beeswax can also apply these settings to the login page. To have these settings applied, contact your Beeswax Account Representative for assistance.

Email Settings

Buzz sends out emails to users for the following processes: Alert emails, Query Tool scheduled reports, Reporting scheduled reports, user creation and password reset. The email address and email content can be white labeled for all these processes, with the exception of reports sent from Report Builder where the ‘from email address’ is always set to the bidderreport.com domain. 

The parts of the email that can be rebranded are labeled in the screenshot and detailed in the table below, the example provided is a user creation email. 

To white label emails sent from Buzz, please follow the below steps:

  1. Share the email address you wish emails to come from with your Beeswax rep. Beeswax will send a verification email to that address, please click on the link within the email to finalise the set up.
    • Note: Depending on your firewall settings, Beeswax Engineering may need to generate DKIM records and send the record set to you to configure on your end. Configuring DKIM records is a way for your server to register the signature that Beeswax adds to the emails.
  2. To white label the contents of the email, please provide the below details:
System Field                                              Value                                              Numbered label on image                        Effect
Email LogoURL String          1Logo to use in email templates
Project NameString          2Project name to use in email templates, e.g. "My Bidder"
Project WebsiteURL String          3URL to link to in emails
Email SenderString          4The sender for emails from this system e.g. email@mybidder.com
Email ‘From Name’       String          5The name of the sender for emails from this system, e.g. ‘My Bidder’
Email ‘From Address’String        N/AFrom address for emails, if different from the above ‘Email Sender’. Must be a valid email address.
From Address NameString        N/AFrom address for system alerts and emails, if different from above ‘Email From Name’. Not an email address.
Bidder UI URLString          6Any links in the email directing the user to the UI will use this domain for the landing page. This should match your CNAME bidder domain, discussed below. 

Bidder Domain Settings / CNAME

To white label the bidder domain, create a CNAME record and verify CNAME ownership.

  1. Share the desired domain name with your Beeswax rep.
  2. Your Beeswax representative will request an SSL certificate from AWS for the CNAME provided and generate a validation CNAME DNS record
  3. Your Beeswax representative will return the CNAME DNS record, which contains the following details:
    • name
    • type: CNAME
    • value
  4. Create a CNAME record using the information provided above to verify ownership of the domain within 72 hours, after which the verification will fail. The procedure for adding CNAME records can vary depending on the DNS service provider.
    • If verification fails, we will need to restart all processes starting from Step 2.
  5. Create a secondary CNAME record for the URL that is preferred for the UI (e.g. "mybidder.customer.com") and point it to ".beeswax.com" 
  6. Once verification is complete, Beeswax will finalise the CNAME deployment

Additional Notes

The following Buzz features cannot be white labeled:

  1. The Buzz REST API endpoint cannot use a CNAME
  2. Creative previews
  3. The cookie syncing process
  4. Segment Tags
  5. Postback URLs
  6. Conversion/Event Tags
  • No labels
Provide feedback on this article