Search

  • Introduction to Templating
    Message templates can include simple customization or even complex segmentation. For example, you can address your customers by name, add special information for certain performances, or only send messages to certain customers. We're always happy to take a look at your templates and give advice o...
  • Inserting a datetime relative to another datetime
    We're all used to messages that say "doors open 45 minutes before the show" or "the show is 120 minutes". With crowdEngage you can turn those into an actual time - for example, "doors open at 6.15pm", or "the show will finish at 9pm". A datetime is the name for a date and time combined. For examp...
  • Dynamic pluralisation
    Keeping your messages grammatically correct with variable quantities   Sometimes you write messages where you need to refer to an unknown quantity. For example, each customer might have booked a different number of tickets to a performance. It could be one ticket, or it could be more.   crowdEng...
  • URL shortening
    crowdEngage has a built-in URL shortener which includes click tracking   Text messages over 160 characters are counted as one message per 153 characters, so it pays to be concise! crowdEngage includes a built-in URL shortener which will replace every web address included in a message with a uniqu...
  • Adding a link to mobile tickets, preorders, and Google Maps
    We call the place where customers can view their mobile tickets, place preorders, and get directions via Google Maps the Your Visit app. To insert a link to the Your Visit app you need to add the special tag: {{ your_visit_url }} We'd recommend combining it will a call-to-action, for example:...
  • Using order and ticket fields in message templates
    You can use any information about the order that your ticketing system exposes via its API.   crowdEngage combines all the orders for a customer so that you only send one message per customer rather than one message per order. Some fields are calculated automatically.   Orders Orders are held in ...
  • Using customer fields in message templates
      You can use any information about the customer that your ticketing system exposes via its API. Here's an abridged list: customer.first_name customer.last_name customer.full_name customer.phone_number customer.email For example:   Hello {{ customer.first_name }}! Would output:   Hell...
  • Using event and instance fields in message templates
    You can use any information about the event and instance that Spektrix exposes via its API. Here's the abridged list:   Instances instance.friendly_start_date instance.friendly_start_day instance.friendly_start_time instance.start instance.start_hour instance.start_minute Events e...
  • Conditional logic (if/else statements)
    You can use if/else statements to insert different content for different customers, or for different events.    If and else statements use a curly bracket and a percentage sign, like this:   {% if customer.first_name == "John" %} Remember that any if statement always needs an ending:   {% endif %...
  • Inserting merge fields/dynamic content
    Address your customers by name, including the performance start time, and more. You can insert data from the customer, event, instance, or order into each message. This is really handy as it means that the same message template can be used for multiple events, and personalized for each customer. ...