# Branding

Partners can apply their own brand identity across the Bullseye platform and tracking pixel. When your clients use the platform or view the tracking script, they see your logo, colors, and company name instead of Bullseye's.

## Overview

Custom branding ensures a consistent experience for your clients. They interact with your brand from the moment they install the pixel to when they view the dashboard. Branding is configured at the partner level and applies to all sub-organizations under your account.

## Branding Elements

| Element         | Description                                                         |
| --------------- | ------------------------------------------------------------------- |
| Logo            | Your company logo, displayed in the dashboard and tracking pixel UI |
| Primary color   | Main brand color (hex format)                                       |
| Secondary color | Accent color (hex format)                                           |
| Company name    | Your company or product name                                        |

## Configuring Branding

Update your branding with **PUT** `/partner/branding`:

```json
{
  "logoUrl": "https://your-domain.com/logo.png",
  "primaryColor": "#1a1a2e",
  "secondaryColor": "#16213e",
  "companyName": "Your Agency Name"
}
```

| Field          | Format              | Notes                                                                                           |
| -------------- | ------------------- | ----------------------------------------------------------------------------------------------- |
| logoUrl        | HTTPS URL           | Must be publicly accessible. Use a square or wide logo for best display. Can be null to remove. |
| primaryColor   | Hex (e.g., #1a1a2e) | Six-character hex code including the # prefix                                                   |
| secondaryColor | Hex (e.g., #16213e) | Six-character hex code including the # prefix                                                   |
| companyName    | String              | Required, 1–255 characters                                                                      |

## Where Branding Appears

### Platform

When your clients log in to the Bullseye dashboard (if they have access), they see:

* Your logo in the header and sidebar
* Your company name in the navigation and footer
* Your primary and secondary colors in buttons, links, and accents

### Tracking Pixel

The tracking pixel can display your branding in visitor-facing elements, such as:

* Identification toasts or overlays (if enabled)
* Script-loaded UI components that show your logo and colors

The exact placement depends on how the pixel is configured for each sub-organization.

### Script Configuration

**GET** `/partner/script-config` returns your current script configuration, including:

* `companyName` — Your configured company name
* `slug` — Your partner slug used in script URLs
* `scriptDomain` — Your custom domain (if set) or the default Bullseye domain
* `scriptDomainVerified` — Whether the custom domain has been verified

Use this endpoint to build the correct script tag for your clients.

## Color Guidelines

* Use hex format: `#` followed by six hexadecimal characters (e.g., `#FF5733`)
* Ensure sufficient contrast between primary and secondary colors for readability
* Test how colors appear in both light and dark contexts if your dashboard supports themes

## Logo Guidelines

* Use a high-resolution image (at least 200x200 pixels recommended)
* PNG or SVG format with transparent background works best
* Host the image on a reliable, HTTPS-enabled URL
* Avoid very wide or very tall aspect ratios; square or moderately wide logos display best


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bullseye.so/partner-program/branding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.