Our Audience Builder is a very powerful tool but having a good understanding of the different parameters and aggregators is key to unlock all its power. Below we will list definitions and information regarding all different aggregators, parameters, and how to enter values correctly to ensure your Audiences capture the right number of users. 

Optional Aggregator

You can add this if needed only, if the criteria is a numerical value or you would like to aggregate the criteria a single number. The options are listed below:

• Total number of: Simple count of the criteria selected
• Number of unique: A distinct count of the criteria, counting the different parameters that are different between them. For example it will count the number of unique options for Vehicle Colours rather than counting how many times Vehicle Colours are present. 
• Sum of: Adding values together. The Total Number will count the criteria but the Sum will add these values together (if numerical values). 
• Average Value of: Calculates the average value of the criteria selected.
• Minimum of: Uses the criteria selected as a minimum value reference 
• Maximum of: Uses the criteria selected as a maximum value reference 

Criteria

Below we list the different options available in the Audience Builder and their definitions. These are divided in general values, values by market, and values related to other engagements. 

PRO TIP: If unsure, check your data in Explore to understand what values are associated with your calls or events to use in your Audiences.

General values

• Event Category: Different categories for Events in Kaisa (Call - Whatsapp - Web - Form - Email) 
• Event: Events within the categories listed above, to be used as a numerical value with an Aggregators (i.e. number of Events).
• Article: Articles to be used as a numerical value with an Aggregators (i.e. number of Articles). These are counted as unique identifiers, passed on to Kaisa normally as an ID (such as Article ID). Fields used are adId, propertyId, listingId or custom_101.
• Article Title: Title value sent to Kaisa on a dynamic number request. Fields used are adTitle, adName or vehicleName
• Article Price: The vehicle or property price sent to Kaisa on a dynamic number request. Field used is adPrice.
• Article Year: article year value sent to Kaisa on a dynamic number request. Field used is adYear
• Article Seller Language: Language passed on to Kaisa normally as adLanguage.
• Account Subscription Level: For cases where a subscription level is passed on to Kaisa and stored. 
• Browsing Device: Extracted from the session or passed on to Kaisa in the userAgent field (divided as Desktop - Table - Mobile)
• Call Type: Can be inbound or outbound
• Duration: call duration stored in seconds
• Geolocation: extracted from the browser session or passed on to Kaisa as part of the userAgent, or taken from the calling number if it is a local number for the country (i.e. "Barcelona, Spain" -or- "Spain (Mobile)" ).
• Medium: Media value for the event as stored in Kaisa.
• Number Type: this can be Dynamic or Static, as per Kaisa definitions.
• Referrer URL: For visitor tracking setups, this will be the referrer url for this unique visitor, the page visited before their session started with Kaisa.
• Landing URL: the first url stored in the session for a visitor. 
• UTM Parameters: as passed on to Kaisa in a request or automatically captured for fs.js users. 

Real Estate

The following values must be passed on to Kaisa as a custom value, either with our javascript solution or as parameters in the payload of a DNCS API request. Normally passed on as adSize or adCity. 

• Real Estate Land Size
• Real Estate number of Floors
• Real Estate Size
• Real Estate City
• Real Estate Property type
• Real Estate Listing Type
• Real Estate Floor
• Real Estate Number of bathrooms

Automotive

The following values must be passed on to Kaisa as a custom value, either with our javascript solution or as parameters in the payload of a DNCS API request. Normally passed on as adColour or adModel. 

• Vehicle Body type
• Vehicle Number Of Seats
• Vehicle Colour
• Vehicle Fuel Type
• Vehicle Model
• Vehicle Number Of Doors
• Vehicle Engine Power
• Vehicle Brand
• Vehicle Mileage
• License

Forms, email tracking and Whatsapp

For events other than calls.

• Form Category: A parameter sent to Kaisa when using our email tracking solution or forms (the value is defined by the customer)
• Conversation Created At: (Whatsap) Timestamp for a Conversation stored as "YYYY-MM-DD HH:MM:SS" in local time. 
• Conversation Duration: Duration in 
• Conversation Expired At: (Whatsap) Timestamp for a Conversation stored as "YYYY-MM-DD HH:MM:SS" in local time. 
• First Agent Message At: (Whatsap) Timestamp for when the first message from an Agent was sent, stored as "YYYY-MM-DD HH:MM:SS" in local time. 
• First Message At: (Whatsap) Timestamp for the first message in a conversation, regardless of origin, stored as "YYYY-MM-DD HH:MM:SS" in local time. 
• First Visitor Message At: (Whatsap) Timestamp for when the first message from a Visitor was sent, stored as "YYYY-MM-DD HH:MM:SS" in local time. 
• Last Message At: (Whatsap) Timestamp for the last message in a conversation, regardless of origin, stored as "YYYY-MM-DD HH:MM:SS" in local time. 
• Number of Agent Messages: Simple count of total messages sent by the Agent
• Number of Agent Rejects: Simple count of Conversations rejected by an Agent
• Number of Visitor Messages: Simple count of total messages sent by the Visitor
• Subject: The email Subject, stored as received by Kaisa. 
• Time to First Response: Duration in Seconds between a request and the first response in a Conversation.

Comparators

Based on the parameters selected, you can then use the following comparators to create the Criteria to be used for your Audience. 

NOTE: Strings are case sensitive