/
increment metric counter

increment metric counter

 

The increment metric counter Public Template allows our users to “count” rows belonging to an individual that pass through a particular process, rule or branch of a rule. We then have the read metric counter that will read the counts out over two rolling date ranges 24hrs and 1 week. Any field can be counted and it's counted against the Alterian CXID.

 

image-20240123-140640.png
Increment Metric Counters

 

The original driver for this was to allow our customers to create rules that could record, then pull out and then control the number of emails sent to customers.

In this example the increment metric counter would be placed in the branch that split from the main flow that is going to the email tile. The example below shows this with the other switch cases going to other channels, direct mail etc. In this example only the rows going to the Email Manager - Henry tile will be counted against Marketing Emails.

If you wanted to count “Direct Mail” use you could add anther Increment Metric Counter in the Direct Mail branch but be sure to change the “metricTableNamePrefix” parameter to Direct mail or equivilent so they are counted separately.

 

 

image-20240125-141953.png

 

 

 


Input data

Field

Description

Example

Field

Description

Example

AlterianCXcxid

This template uses the CXID in the flow of the rule to create a key to record the metric information against.

 

Metric

This is the metric that has been chosen to be counted

 

Time Stamp

Timestamp. This will automap to the timestamp field in a standard rule.

 

Configuration

Field

Description

Example

Field

Description

Example

metricTableNamePrefix

This is the table in Alterian where the metric counters will be stored. The default is “MetricCounter”. In some cases you may want to count the same field multiple times over the same date range. For example you may want to count emailAddress being used for transactional emails separately to marketing emails. To enable this simply choose a separate but consistent metricTableNamePrefix value

For example:

transactional emails - transactionalemailcount

marketing emails - marketingemailcount

MetricCounter

image-20240125-143353.png
Example of Increment Metric Counter field mapping

 

Output Data

Field

Description

Example

Field

Description

Example

 

 

 

Related content