Overview

A Constant Property is an event property that can be tracked across multiple events. Segmentation is done if multiple events are done with the same value of the event property held constant. This feature enables a marketer to create a single Campaign for all the values of the property held constant instead of individual campaigns for each value of the property.

Example #1 - Single Item Engagement

As a growth marketer for an E-Commerce app, you want to segment out an audience that has Viewed a product in the past but not bought that exact product. A straightforward segmentation would be to qualify people based on each product - Users who did Product Viewed Event where Product Name = Red Shoes in the last 30 days and Users who did not do Charged Event where Product Name = Red Shoes in the last 30 days. This would need to be repeated for all the items the E-Commerce app has available.

The "Constant Property" feature allows a single segmentation where you can mark the property "Product Name" to be kept constant, and the system will fire the same query for all the values of the Product Name and qualify those users accordingly. The "Constant Property" value will be available as a Personalisation key inside the Message body.

If User A has Viewed "Jenny red shoes" and not Purchased that exact product, then they would get an engagement as -
Hello A
You have added Jenny's red shoes to your cart. How about a discount code, Cashback20, to help you save more?

If User B has Viewed "Wonderland yellow jacket" and not Purchased that exact product, then would get an engagement as -
Hello B
You have added a Wonderland yellow jacket to your cart. How about a discount code, Cashback20, to help you save more?

Example #2 - Summary Engagement

As a growth marketer for the E-Commerce app, you may want to send a summary of Weekly Expenses and Savings on the User's transactions on the application. This can nudge the users to continue seeing value in purchasing from your E-Commerce platform.

The following are some sample engagement messages where John spent $100 over the last week and saved $20 using various coupons. Mary spent $120 the previous week and saved $40 using multiple coupons. You can send out a notification that says something like the following:

Hello John!

The weekend sale is here! You have been able to save $20!! from your purchases worth $100 over the last week. Shop more on the weekend and choose from exciting products with more than 20% OFF!!

Hello Mary!

The weekend sale is here! You have been able to save $40!! from your purchases worth $120 over the last week. Shop more on the weekend and choose from exciting products with more than 20% OFF!!

Example #3 - Category-Level Engagement

As a growth marketer for an e-commerce app, you want to engage users who viewed a product category, such as Shoes, but did not purchase any products in that category. Creating a separate segment for each product category is not practical. The Constant Event Property feature handles this with a single segment. Mark the product_type property as constant, and CleverTap evaluates the same category value across the Product Viewed and Charged events.

The segment logic is as follows:

User performed Product Viewed
User did not perform Charged
product_type from Product Viewed is held constant for comparison

If User A viewed product type = Shoes and did not purchase any item with product type = Shoes, the user qualifies for the segment. The campaign can then personalize the message using the constant property value.

📘
Note
This use case uses a category-level property (product_type) rather than an item-level property (product_name). Use this approach when you want to engage users based on broad interest in a category rather than a specific product.

Limitations

The Constant Event Property feature supports the Live Behavior (inaction) campaign types.

The following use cases are not supported natively:

Filtering users who performed an event with the same property value more than a specified number of times within a given time window. For example, users who viewed the same product type more than 3 times in the last 24 hours. Triggering a campaign on the nth occurrence of an event for the same property value.

Hold Event Property Constant

You can hold a property constant in an inaction campaign. Currently, the Constant Event Property supports Push, Email, SMS, and Webhook campaigns.

Alias Event Property

If different names call the same event property for various events, you can create an Alias property that will hold all the properties from other events. You can then use this across campaigns and analytics.

For example, the event Purchased has an event property that holds the product id of the item called product_id. However, the event Added to carthas an event property called Product ID that holds the same value. You can create an Alias Event property called Product ID containing the event property product_id and Product ID.

Navigate to Settings > Schema > Events > Alias event property.
Click the +Alias Event Property button. The Create Alias Event Property window displays.
Enter the name for the Alias event property.
Click the + Event property link to map current events and their properties to the new alias.

You can now use this Alias event property in all campaigns within the Constant Property option.

Inaction Campaign

You want to engage all the users who dropped off after adding a product to the cart. The event property across these events is Product Name. The value of this event property can be anything from Jenny's red shoes, running shoes, a Wonderland yellow jacket, a baseball bat, and so on.

You can define the conditions for the target audience and then select the constant event property.

To create a campaign:

From the dashboard, navigate to Campaigns.
Click Create Campaign.

Select a messaging channel.

Under the Start here section, select the qualification criteria as Live Behavior.
Click Done.

Under the Who section, select events, and properties, as required.
Select the Constant event property checkbox, then select Product name.
Click Done and personalize the message using Liquid Tags under the What section.

For example, you can send the campaign with the item name that the user who added an item to the cart but did not purchase.

Hurrah.. ! 
Complete your purchase of {{ ConstantEventProperty | default:"this item" }} with 15% off on using code GRT572E.

Following is a sample message the user gets:

Hurrah.. ! 
Complete your purchase of Jenny red shoes with 15% off on using code GRT572E.

We hold the property, such as Products, across all events. The Product property value can be anything, such as Jenny red shoes, Cool Ice blue goggles, or George High white hat. The Constant Event Property holds the value of the product.

📘
Note
If the campaign uses Constant Event Property personalization with a delay greater than 24 hours, default values are sent.

Stats

The stats page for Campaigns, where the Constant Property feature is used, shows comprehensive details as follows:

Event count for each value of the constant event property (Top 10 or Bottom 10)
User counts for each value of the constant event property for notification sent, viewed, clicked, converted, and in the control group.

You can change the conversion event, map its property to the constant event property, and track conversions for the same event property value.

Conversion Event

The conversion event helps you track conversions. To track revenue, set the user conversion event from the campaign setup.

Mapping a constant property with a conversion event property allows you to view the conversion rate for specific property values.
You can view metrics for any conversion event and track the conversion rate when any item is purchased, or track the conversion rate for a specific item that is added to the cart.

Advanced - Constant Property with Catalog Personalization

You can combine catalog personalization with constant event property to unleash the full power of campaign personalization.

For example, you can hold an event property (Product ID) constant and also add to it the rating and cost present in a catalog via catalog personalization.

First, you must map the constant event property to the catalog. To do so, perform the following steps:

From the dashboard, navigate to Campaigns.
Click + Campaign.
Select a messaging channel.
Under the What section, select a message type.
Click Go To Editor.

Click Personalization.

Under Catalog, select a catalog.
Select the required events and properties.
Click Apply.

Enter any mandatory content for your message.
Click Done.

Under the Who section, select the required events and properties.
Select the Constant event property checkbox, then select Product name.
Click Done.

Inaction Campaigns Personalization

For inaction campaigns, you can use the following liquid script to use a particular column from the selected catalog in the message.

Hurrah.. ! 
Complete your purchase of {{ ConstantEventProperty | default:"this item" }}, with 15% off on using code GRT572E.

{{ ConstantEventProperty | default:"this item" }} is rated {{ Catalog["Amount Catalog"].Rating | default:"3" }}-star and is currently priced at {{ Catalog["Amount Catalog"].Amount | default:"$99" }}.

A user receives a message like:

Hurrah.. ! 
Complete your purchase of Nautical White T-shirt, with 15% off on using code GRT572E.

Nautical White T-shirt is rated 4-star and is currently priced at $69.


Nautical White T-shirt is rated 4-star and is currently priced at $69.