-
General information
-
Account Settings
- Creating & managing your personal doo account
- Organization settings: Managing your account settings
- Multi-user: Working as a team
- How to reset your password
- Changing the email address of your doo account
- The doo account packages
- What can I do if a doo site does not load
- Independently adapt standard designations of the doo booking process
- How do I delete my account
- Payment Process: How to manage payment options
- Password Security using doo: What options are available?
-
Events
-
- Edit email contents
- Using placeholders in booking email templates
- How to adjust invoice contents
- Attendee tickets and QR code scanning
- What do doo tickets look like?
- E-mail attachments for bookers and attendee
- Certificates & Co: Create custom documents
- Define your own booking conditions
- Revenue Disbursement: Entering and editing invoice address & bank account information
- Create bilingual (multilingual) events
- Bookings with manual approval
- Create a waiting list
- Access codes and promotion codes: Discounted tickets for your participants
- doo Widgets: Integration into your own website
- Custom event website
- How to create a booking process in english
- Providing flyers, event programs or direction sketches
- Tips for a smooth entry
- How does the booking process work for my attendees?
- How do I make test bookings?
- Creating exclusive registration access for selected contacts
- Delete ticket categories & change prices and sales periods after go-live
- Cancellation of events
- What are event fields and how do I use them best ?
- Shorten the booking process and prefill data: How to make the booking process as convenient as possible for bookers
- Tips for virtual events with doo
- Integration into your own Facebook page
- Event Templates: Creating templates for your events
-
Manage Bookings
- Manage bookings and attendees
- Monitoring incoming bookings
- The attendee overview
- Invitation list: Track the registration status of specific contacts
- Manual registration
- Resend automatically generated emails
- Rebooking: How to change existing bookings
- Cancellation & Refund Handling
- Booking self-service: Allow bookers to subsequenty access and edit their bookings
- Download booking overview and attendee list
- Change of attendee data and invoice address
- Bank transfer: How to deal with pending transactions
- What to do, if someone has not received their confirmation e-mail or ticket
-
Contact Management
- Contacts: Introduction and Topic Overview
- Contact details: Collect cross-event contact information
- Overview contact data fields
- Managing contact data fields
- Creating contacts - How do contacts get into the doo contact center?
- Contact import - Bulk creation and editing of contacts
- Managing existing contacts
- Creating and managing contact groups
- Datamatching & Synchronization of booking data and doo contact
- Email subscriptions: Double opt-in & opt-out options at doo
- Deleting contacts
-
Emails
-
- E-mail messages: How to create a new message
- Contact management: How to build up clean recipients list
- Performance report: How to evaluate the send-out of your email messages
- Email activities: What the status reports of your email messages mean
- Bounce management: Tips for high quality recipient lists
- Use liquid code in email messages for individual personalization
-
Websites
- The doo website editor: create an individual event page
- Mobile optimization: Customize your site for all your devices
- Installing different tracking tools on the website
- Creating a SSL certificat (HTTPS) to ensure data security
- Website Tracking: How to integrate doo into your Google Analytics To be Created
-
Additional Functions
- Optional Service: Refund handling via doo
- Ticket design: How to get your ticket in the desired design
- Forms - Set up surveys and feedback requests for your attendees
- Embedded Reports
- Customer specific sender emails
- Email inbox: How to manage email requests from your participants within doo
- Add calendar entries to your event communication
- Filtered cross-event widgets: How to show only selected events
-
Automations
-
Booker & Attendee FAQ
-
Developer Documentation
Use liquid code in email messages for individual personalization
With the help of liquid code it is possible for you to include variable fields in e-mail messages. This way you can individually fill emails with the contact data available in doo. This article will describe how to do this and what customization options you have.
- Inserting liquid code through personalizations
- Write liquid code yourself
1. Insert liquid code through personalizations
To customize email messages to recipient lists and contact groups, you can use personalizations. To do this, click on the text module you inserted in your e-mail message, in which you want to insert placeholders. This will bring up a window with editing options. Click “Personalizations” here and select the appropriate field. Organization-, contact- and event-related placeholders are predefined.
Instead of simply inserting the default personalizations , you can further customize them.
For example, take the salutation placeholder: {{ contact.salutation }}. The placeholder can be further modified using filters. To do this, insert | and the desired filter inside the placeholder.
Ex: {{ contact.salutation | default: “Hello” }}. This example of using filters is helpful when the gender of the recipient is not known and where normally “Dear Sir/Madam” is given as default.
Some filters that are helpful for you can be found in the table below. More detailed information can be found here in the Liquid documentation.
{{ … | capitalize }} | The input value is capitalized. title -> Title |
{{ … | date: “%a, %b %d, %y” }} | Dates are rendered in a different format. Here for example Fri, Jul 17, 15 |
{{ … | default: 2.99 }} | Placeholders are assigned a default value if no data is present. |
{{ … | downcase }} | The input value is written in lowercase. Title -> title |
{{ … | first }} | Returns the first value of an *array |
{{ … | join: ” and ” }} | Joins values of an *array with For example here and |
{{ … | last }} | Returns the last value of an *array |
{{ … | prepend: “List: ” }} | Prepends a **string (Here List: ) to the **string obtained from the data. |
{{ … | replace: “his”, “their” }} | Replaces the First word (Here his) with the Second word (Here their) in a **String. |
*Array = string of elements of a data type. The elements can be ordered by their position in the array (starting with 0).
**String = A string that results in words or sentences, for example, and is delimited by ” “.
2. Write liquid code yourself
With Liquid Code it is possible to define logical operations and a control flow. By using self-written Liquid Code in email messages, you can create standard emails that adapt their content to the type, timing, event status, size, etc. of the email. In addition, you can also customize the email to different groups of recipients so that customized information can be sent within a campaign.
To use Liquid Code properly and ensure that no incorrect content appears in email messages, you should only write code yourself if you have experience with other programming languages and concepts. In the approaches below, you will find examples of how some programming concepts are implemented in Liquid. For complete documentation on Liquid codes and uses, click here.
Defining variables:
{% assign organizer = "doo" %}
IF-Operations:
{% if event.price <= 20 %}
This is a cheap event.
{% endif %}
{% if event.name contains "Extra" %}
This is an additional event.
{% endif %}
{% if attendee.name and attendee.name.size > 10 %}
Wow, {{ attendee }}, you have a long name!
{% else %}
Hello!
{% endif %}
Split operator:
Splits a string into an *array at the defined char.
{% assign attendees = "John, Tim, Tina, Alex" | split: ", " %}
Address array indices:
{{ event.attendees[0] }}
{{ event.attendees[1] }}
{{ event.attendees[3] }}