> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pingtree.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reporting Hub

> The Reporting Hub is a white-label buyer-facing reporting portal that you can offer to your buyers under your own custom domain — giving them a branded, self-serve view of their campaign performance data.

## Overview

The Reporting Hub is a separate, buyer-facing web portal hosted under your own custom domain. It allows you to give buyers direct access to the performance data for the campaigns you have granted them access to — without exposing the rest of your Pingtree account.

Everything in the Reporting Hub is white-labeled: you control the domain, the branding images, and which campaigns each buyer user can see.

> **Video Walkthrough:** A step-by-step video guide for this feature is coming soon.

<Frame caption="Reporting Hub setup with custom domain and branding configuration">
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/pingtree/assets/images/placeholder.svg" alt="Reporting Hub setup with custom domain and branding configuration" />
</Frame>

***

## What Buyers See

When a buyer logs in to your Reporting Hub portal, they see a clean reporting interface scoped to the campaigns you have assigned to their account. They can:

* View campaign performance metrics (clicks, conversions, leads accepted, etc.)
* Filter by date range
* Review historical trends for their campaigns

Buyers have no access to your Pingtree account settings, other campaigns, distribution configuration, or financial data beyond what their assigned campaigns show.

***

## Setting Up a Custom Domain

To give buyers a fully branded experience, you can point your own domain (e.g., `reports.yourbrand.com`) to the Reporting Hub.

### DNS Requirements

Before starting domain setup in Pingtree, you must first update your DNS records so the domain points to Pingtree's Reporting Hub infrastructure. Contact your DNS provider or domain registrar to add the required A record or CNAME.

### Domain Verification and Binding

<Steps>
  <Step title="Enter Your Domain">
    Navigate to **Reporting Hub > Domain Settings** and enter the custom domain you want to use (e.g., `reports.yourbrand.com`).
  </Step>

  <Step title="Verify the Domain">
    Click **Verify**. Pingtree will check whether your DNS records are correctly pointed. If the domain is not yet pointed, you will see a prompt with instructions to update your DNS settings first.
  </Step>

  <Step title="Bind the Domain">
    Once verified, click **Submit** to start the domain binding process. A real-time progress bar will track the following steps:

    * Domain bind in progress (0–40%)
    * Domain bind successful (40%)
    * SSL installation in progress (40–100%)
    * SSL installed successfully (100%)
  </Step>
</Steps>

<Tip>
  SSL is provisioned automatically by Pingtree during the bind process. You do not need to purchase or upload an SSL certificate.
</Tip>

### Domain Binding Progress

The bind process streams live status updates to the screen. If an error occurs at any stage, the progress bar will display in red with an error message explaining what failed. Common causes include:

* DNS records not yet propagated (can take up to 48 hours)
* The domain is already in use by another Pingtree account

### Unlinking a Domain

To remove a custom domain from the Reporting Hub:

1. Go to **Reporting Hub > Domain Settings**.
2. Click **Unlink** next to the active domain.
3. Confirm the action. The domain binding and SSL configuration will be rolled back.

After unlinking, buyers will no longer be able to access the portal via that domain until a new domain is configured.

***

## Branding Configuration

Upload custom images to match the portal to your brand identity.

| Image                   | Where It Appears                                    | Recommended Use                     |
| ----------------------- | --------------------------------------------------- | ----------------------------------- |
| **Login Page Image**    | Background or hero image on the buyer login screen  | Brand photography, vertical banners |
| **Portal Header Image** | Header area within the reporting portal after login | Logo or brand wordmark              |

### Uploading Branding Images

<Steps>
  <Step title="Go to Page Configuration">
    Navigate to **Reporting Hub > Page Configuration**.
  </Step>

  <Step title="Upload Images">
    Upload your Login Page Image and Portal Header Image. Supported formats are JPG and PNG. Images are stored securely and served via CDN.
  </Step>

  <Step title="Save">
    Click **Save** to apply the images. Changes take effect immediately for all portal users.
  </Step>
</Steps>

***

## User Management

Create individual login credentials for each buyer who needs access to the Reporting Hub portal.

### Adding a User

<Steps>
  <Step title="Navigate to Users">
    Go to **Reporting Hub > Users** and click **Add User**.
  </Step>

  <Step title="Fill In User Details">
    Enter the buyer's first name, last name, email address, and a temporary password.
  </Step>

  <Step title="Save the User">
    Click **Save**. Pingtree will automatically send the buyer a welcome email containing their login URL, username, and the password you set. If a custom domain is configured, the login URL in the email will use your branded domain.
  </Step>
</Steps>

### Editing and Deleting Users

* **Edit** — Update a user's first or last name from the user list. Email addresses cannot be changed after creation.
* **Delete** — Remove a user's access entirely. Deleted users can no longer log in to the portal.

### Assigning Campaigns to a User

By default, a new Reporting Hub user cannot see any campaigns. You must explicitly grant access:

1. Open the user's record from **Reporting Hub > Users**.
2. Click **Manage Campaigns**.
3. Select the campaigns this user is permitted to view.
4. Click **Save**.

Users will only see data for campaigns you have assigned to them. All other campaigns remain hidden.

***

## IP Whitelisting

Restrict portal access to specific IP addresses for additional security.

<Steps>
  <Step title="Go to IP Settings">
    Navigate to **Reporting Hub > Whitelist IPs**.
  </Step>

  <Step title="Add Allowed IPs">
    Enter the IP addresses or CIDR ranges that are permitted to access the portal. Separate multiple entries with a new line.
  </Step>

  <Step title="Save">
    Click **Save**. Any login attempt from an IP address not on the whitelist will be rejected.
  </Step>
</Steps>

<Tip>
  If you enable IP whitelisting, make sure to include your own IP address so you do not accidentally lock yourself out of the portal for testing.
</Tip>

***

## How Buyers Use the Portal

Once a buyer has their credentials and the portal URL, their experience is straightforward:

1. Navigate to your custom domain (e.g., `https://reports.yourbrand.com`).
2. Log in with their email and password.
3. Select a campaign from the list of campaigns assigned to their account.
4. Use the date range picker to select the reporting period.
5. View performance metrics, trends, and any data available for that campaign.

Buyers cannot modify campaign settings, access distribution configuration, or see any data outside their assigned campaigns.

***

## Configuration Summary

| Setting             | Location                            | Purpose                                 |
| ------------------- | ----------------------------------- | --------------------------------------- |
| Custom Domain       | Reporting Hub > Domain Settings     | White-label the portal URL              |
| SSL Certificate     | Auto-provisioned during domain bind | Secure HTTPS access                     |
| Login Page Image    | Reporting Hub > Page Configuration  | Brand the login screen                  |
| Portal Header Image | Reporting Hub > Page Configuration  | Brand the portal interior               |
| User Accounts       | Reporting Hub > Users               | Buyer login credentials                 |
| Campaign Access     | User record > Manage Campaigns      | Control which campaigns each buyer sees |
| IP Whitelist        | Reporting Hub > Whitelist IPs       | Restrict portal access by IP            |