White Label Options

Agency Logo

2. Click on "Agency Settings" in the Settings sub-navigation

3. Click on the "White Label" tab under Agency Settings

4. Click on the "Upload" button under Agency Logo

5. Use the presented file browser to find the desired image

6. Click on the image in the file browser

7. Click on the "Open" button in the file browser

8. Click on the "Save Settings" button near the bottom left

NinjaNote: Recommended maximum image dimensions for Agency Logo: 300 x 90

Agency Color Palette

2. Click on "Agency Settings" in the Settings sub-navigation

3. Click on the "White Label" tab under Agency Settings

4. Click on the color squares to set your desired default chart color set

Google Analytics 4 Tracking Tag ID

2. Click on "Agency Settings" in the Settings sub-navigation

3. Click on the "White Label" tab under Agency Settings

4. Enter the Tag ID in the provided field

📘

Find more info on the tracking tag ID here

Email SMTP

2. Click on "Agency Settings" in the Settings sub-navigation

3. Click on the "White Label" tab under Agency Settings

4. Enter the requested information into the fields under the "Email SMTP" section

5. Click on the "Verify" button to test the connection to your email provider

6. Enter an email address in the "Test Email" field to send a test email

📘

Multiple SMTP Configurations

Need to route email differently for different brands or advertisers? See Multi-SMTP Configuration to learn how to set up multiple SMTP servers and control email routing per whitelabel CName or per advertiser. Contact your CSM to enable this feature.

⚠️

Microsoft Office 365 / Exchange Online Limitations

If you are configuring NinjaCat to send through a Microsoft Office 365 / Exchange Online SMTP server, be aware of the following Microsoft-imposed limitations that can affect report and notification delivery:

• Sending limits: Microsoft 365 enforces a recipient rate limit (commonly 10,000 recipients per day per mailbox) and a message rate limit (~30 messages per minute). High-volume report sending can be throttled or blocked once these limits are hit.
• Authentication requirements: Microsoft has deprecated Basic Authentication for SMTP AUTH on most tenants. You may need to enable SMTP AUTH for the sending mailbox, use an App Password (when MFA is enforced), or work with your Microsoft 365 administrator to allow the connection.
• Sender address restrictions: The "From" address on outgoing email typically must match the authenticated mailbox, or the mailbox must have explicit "Send As" / "Send on Behalf" permissions. Mismatches will cause messages to be rejected.
• Connector / relay configuration: For high-volume sending, Microsoft recommends using a dedicated Exchange Online connector or an SMTP relay service rather than direct SMTP submission.
• NinjaCat visibility: NinjaCat reports a "Sent" status once the email is handed off to your SMTP server. If Microsoft throttles, rejects, or silently drops a message after that handoff, NinjaCat will not surface that error — you'll need to check your Microsoft 365 message trace / mail flow logs.

If you experience delivery issues with Microsoft Office 365 SMTP, consult your Microsoft 365 administrator or consider using a dedicated transactional email provider (e.g., SendGrid, Mailgun, Amazon SES) for higher-volume report delivery.