You can now compare one date-based profile signal with another when creating Custom Segments. Instead of comparing dates against a fixed calendar date, you can compare dates relative to each contact's own timeline. This makes it easier to build churn, retention, and re-engagement segments that work consistently across different customer cohorts.

Previously, date-based profile signals could only be compared against fixed dates or predefined time periods. Since every contact starts interacting with your business at a different time, it was difficult to create accurate churn and retention segments.

With signal-to-signal comparisons, you can compare one date profile signal with another and define the number of days between them. This allows you to build segments based on each contact's activity timeline instead of using a fixed calendar date.

For example, you can create a condition such as:

This makes it easier to identify contacts who became inactive shortly after their first interaction or customers who remained engaged over a specific period.

When you create a condition using a date-type profile signal, you can compare it with another date-type profile signal using one of the following operators:

When you compare two date profile signals, Wati calculates a comparison date using the reference signal and the number of days you specify.

For example, if:

The comparison date is January 30. Contacts whose Last reply occurred before January 30 match the condition.

Because the comparison is evaluated against a calculated date, it works best when the relationship between the two profile signals has a natural chronological order. For example, First conversation date always occurs before Last reply, making it well suited for churn and retention use cases.

To create a segment using profile signal comparisons:

You can combine profile signal comparisons with other conditions using AND or OR to create more targeted audiences for campaigns and automation.

Identify contacts who became inactive within 30 days of their first conversation.

Example conditions:

Identify contacts who remained active for more than 30 days after their first conversation.

Example condition:

You can also reuse the same segment by changing the day offset to create 7-day, 30-day, 60-day, or 90-day cohorts.

Signal-relative comparisons work like any other Custom Segment condition. You can combine them with additional conditions using:

Segments created using these comparisons can also be used in:

Profile signal comparisons in Custom Segments are available to customers on the Pro and Business Wati plans.

Profile signal comparisons let you compare one date-based profile signal with another when creating Custom Segments. Instead of comparing dates against a fixed calendar date, you can compare dates relative to each contact's own timeline. This makes it easier to build churn, retention, and re-engagement segments.

You can compare one date-type profile signal with another using the following operators:

Wati calculates a comparison date using the reference profile signal and the number of days you specify. For example, if First conversation date is January 20 and the condition is Last reply is less than 10 days after First conversation date, the comparison date is January 30. Contacts whose Last reply occurred before January 30 match the condition.

Profile signal comparisons work best when the two date-based profile signals have a predictable chronological order. For example, First conversation date always occurs before Last reply, making this comparison well suited for churn and retention use cases.

Yes. You can combine profile signal comparisons with other Custom Segment conditions using AND or OR to create more targeted audiences for campaigns and automation.

Segments created with profile signal comparisons can be used in Broadcasts and Automation Rules.

Yes. You can reuse the same segment logic by changing the day offset to create 7-day, 30-day, 60-day, or 90-day cohorts.

Profile signal comparisons only support date-type profile signals. A date profile signal cannot be compared with itself. If either date value is empty for a contact, that contact does not match the segment.