How does the 'Billing' Technical Workflow Calculate Active Profiles?

[SkylerQu2]

Hi,

The Active profiles monitoring | Adobe Campaign wiki and logs of the 'Billing' workflow give us the following information about active profiles:

• Targeted or communicated to in the past 12 months
• Exist in the broadLogRcp, broadlogEventHisto, broadLogOperatorLogs, broadLogBatchEvent, broadLogAppSubRcp tables

Our instance to date does not utilize the BatchEvent or AppSub features.

We have queried the broadLogRcp, broadLogEventHisto, and broadLogOperatorLogs tables and deduplicated on identifiers (recipient primary key for broadLogRcp, 'recipient identifier' for broadLogEventHisto, 'Primary Key (Operator)' for broadLogOperatorLogs, but the active profile count we get is slightly off. It is .8% less than the count given by the 'billing' technical workflow. 

Can someone please provide the specific logic used by the 'billing' technical workflow to obtain the active profiles count?

Thanks,

Skyler

[_Manoj_Kumar_]

Hello @SkylerQu2 

You will have to consider the exclusion logs as well. Any exclusion that happens by typology is considered in this calculation.

[SkylerQu2]

Hi @_Manoj_Kumar_  can you be more specific? This wiki page says "the profiles that were excluded during delivery preparation (by typology rules or quarantine mechanism for example) are not taken into account." Campaign Active profiles | Adobe Campaign

From what I have seen, excluded recipients are not added to broadLogRcp, so we are not including them in the calculation already.

Thanks,

Skyler

[_Manoj_Kumar_]

Hello @SkylerQu2  You will have to consider the entries from "Recipient Exclusion Logs" schema for this calculation.