Skip to main content

​
Billing

MDB operates on a simple, transparent credit system based on unique visitors per month, per site. This page explains how billing works and provides examples to help you estimate costs.

​
Credit System Overview

  • 1 unique visitor per month per site = 1 credit
  • Sessions don’t count - Only unique visitors matter
  • Monthly billing cycle - Credits reset each month

​
How Credits Are Calculated

​
Key Principles

  1. Unique visitors only - Multiple visits from the same person on the same site in the same month = 1 credit
  2. Site-specific - Same person visiting different sites = separate credits per site
  3. Monthly reset - Each month starts fresh for credit counting
  4. Identification required - Only identified visitors count toward credits

​
Billing Examples

Scenario: Person visits site-a.com 10 times in JanuaryBilling: 1 creditExplanation: Same person, same site, same month = 1 credit regardless of visit frequency
Scenario: Person visits site-a.com 2 times in January and 5 times in FebruaryBilling: 2 credits (1 per month)Explanation: Same person and site, but different months = 1 credit per month
Scenario: Person visits both site-a.com and site-b.com in MarchBilling: 2 credits (1 per site)Explanation: Same person, same month, but different sites = 1 credit per site
Scenario: Person visits site-a.com in January, February, and March, plus site-b.com in FebruaryBilling: 4 credits
  • site-a.com in January: 1 credit
  • site-a.com in February: 1 credit
  • site-a.com in March: 1 credit
  • site-b.com in February: 1 credit
Explanation: Each unique combination of person + site + month = 1 credit
Scenario: 3 different people each visit site-a.com once in JanuaryBilling: 3 creditsExplanation: Different identified visitors = separate 1 credit charges

​
What Counts Toward Credits

​
Included

  • ✅ Identified visitors - Visitors that MDB successfully identifies at the person level
  • ✅ Unique monthly visits - First visit by an identified person to a site in a given month

​
Not Included

  • ❌ Unidentified visitors - Visitors that MDB cannot identify don’t consume credits
  • ❌ Repeat visits - Additional visits by the same person to the same site in the same month
  • ❌ Sessions - Number of sessions doesn’t affect credit consumption

​
Billing Cycle

  • Monthly billing - Credits are calculated and billed monthly
  • Reset each month - Credit counting starts fresh each calendar month
  • Usage tracking - Monitor your credit usage in real-time through the MDB dashboard

​
Cost Optimization Tips

​
Minimize Credit Usage

  1. Consolidate tracking IDs - Use the same tracking ID across related sites when possible
  2. Monitor identification rates - Higher identification rates mean more credits consumed
  3. Use options strategically - Leverage pixel options for segmentation without affecting billing

​
Maximize Value

  1. Implement proper webhook handling - Ensure you’re capturing and utilizing all identification data
  2. Use enrichment features - Take advantage of upcoming behavioral and enrichment data
  3. Optimize for high-value visitors - Focus pixel placement on pages with your most valuable traffic

​
Dashboard Monitoring

Your MDB dashboard provides:
  • Real-time credit usage - See current month consumption
  • Historical data - Track usage trends over time
  • Site breakdown - Credits consumed per site/tracking ID
  • Identification rates - Percentage of visitors successfully identified
Credit usage is updated in near real-time, so you can monitor consumption throughout the month.

​
Frequently Asked Questions

No, you only pay for visitors that MDB successfully identifies at the person level.
Multiple page visits by the same person on the same site in the same month count as 1 credit total.
Each unique domain/subdomain with a pixel counts separately for billing purposes.
Yes, you can configure spending limits and alerts in your MDB dashboard to control costs.

​
Next Steps

  • Monitor your usage - Check your MDB dashboard regularly to track credit consumption
  • Set up alerts - Configure notifications for usage thresholds
  • Optimize implementation - Use the data to optimize your pixel placement and webhook handling