Using CRM parameters with Rule Builder

To recap, here are the conditions available to target using parameters:

  • String Parameter – bring in CRM merge text data based on subscriber data e.g. delivery city. For example, if the delivery city equals "London" you could choose to show a banner for an event in London but show different content if the delivery city field is anything else.
  • UTC Datetime Parameter – based on the datetime stamp merged in from the CRM/ESP, showing different content x time before a merged date, up until x time after merged date, from x time before a merged date or from x time after merged date. E.g. a use case would be in automated campaigns such as an offer lasts 48 hours after the welcome message 1 is first sent.
  • Numeric Parameter – bring in CRM merge numerical data based on subscriber data e.g. number of orders showing different content based on if they haven’t made an order yet or have made 10 orders.

Use Case 1: Dynamic Content

For those using ESPs that don't have a quick and easy solution to showing dynamic content, use Litmus Personalize.

dynamic content rule builder

Use Case 2: Gender

Show different countdown timers, hero images, content or even live products based on the gender associated with the customer. Again, great to use rather than having to set up two (or more) different sends in an ESP.

In the following example, we're showing womenswear / menswear products already set up in Content Automation to the gender attributed to each customer in the ESP. As a mainly womenswear brand, you can then show the default to be womenswear and vice-versa.

gender rule builder

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us