Understand how Message Center affects active profiles in ÃÛ¶¹ÊÓƵ Campaign v8
In ÃÛ¶¹ÊÓƵ Campaign v8, there’s often confusion about whether transactional messages sent through the Message Center (RT instance) count toward your active profile limit. These messages are billed separately based on throughput and don’t count toward active profiles—unless they re-engage an inactive known profile in the Marketing database. In that case, the profile becomes active and is tracked for billing. This article explains how ÃÛ¶¹ÊÓƵ tracks active profiles and how transactional messaging impacts billing.
Description description
Environment
ÃÛ¶¹ÊÓƵ Campaign v8
Questions
- Do transactional messages sent from the RT (Message Center) instance count as active profiles?
- How does ÃÛ¶¹ÊÓƵ calculate the number of active profiles?
- Do deliveries from the RT instance affect billing or profile tracking?
Resolution resolution
Here are the key clarifications about the Message Center (RT instance) and how it relates to active profiles:
- Transactional messages sent through the RT instance are licensed separately from active profiles. These messages are billed based on throughput, like the number of API calls per hour, not on the number of profiles.
- Only the Marketing instance contributes to the active profile count. RT instances don’t store or manage profile data the same way, so they don’t affect the active profile total.
- However, if a transactional email is sent from RT to a known profile in the Marketing database that was previously inactive, that profile becomes active. It is then included in the count of active profiles, which affects billing. ÃÛ¶¹ÊÓƵ tracks this change in the
nms:activeContacttable, which logs recipient and delivery activity for billing.
For more details, check ÃÛ¶¹ÊÓƵ’s official documentation on active profiles in Campaign Classic and Campaign Standard.
If you’re still unsure or need help reviewing your active profile count, reach out to ÃÛ¶¹ÊÓƵ Support.