Locale used for the booking process (translations, dates, numbers, currency…)

doo_locale

de-de, en-us …

doo Organization ID

doo Widget Config Name

see Details about prefilling booker and attendee data

doo_buyer_prefill

JSON stringify + encodeURIComponent

{ first_name: 'John' } → %7B"first_name"%3A"John"%7D

see Details about prefilling booker and attendee data

doo_first_attendee_prefill

JSON stringify + encodeURIComponent

for single-use codes: 

for multi-use codes:

doo_code

Widget bootstrap mode,

for starting with booking-edit login screen:

for autologin into self service booking edit (used together with data-viovendi-booking and data-viovendi-email):

doo_mode

For autologin into booking self service edit:

https://event_url.com?doo_mode=booking-details&doo_booking=TX-00000-000&doo_email=email@example.com

For entering booking-edit login page:

https://event_url.com?doo_mode=booker-login

Additional parameters &doo_booking=TX-00000-000&doo_email=email@example.com can be used for login form prefill

Booking invoice number TX-... (used with data-viovendi-mode)

doo_booking

Booker email (used with data-viovendi-mode)

doo_email

holds path keys to resolve provided payment options, the parameter can include one or several path keys

single: 

multiple:

doo_path_keys

Tickets prefill

doo_tickets_prefill

JSON stringify + encodeURIComponent

'{"123": 1,"124": 3}'

→ '%7B%22123%22%3A%201%2C%22124%22%3A%203%7D'

Autosubmit ticket-selection step

doo_ticket_selection_step_behavior

Autosubmit information step

doo_information_step_behavior

Payment option prefill

doo_payment_option

Auto-accept terms & conditions

doo_terms_accepted

Autosubmit information step

doo_payment_step_behavior

Configure logging of the user journey, resources requests, HTTP requests with AWS RUM

Performance metrics and JS errors are logged by default if logging enabled and their options are not configurable from our side at the moment

doo_logging (will be added with https://viovendi.atlassian.net/browse/DOO-23320 )

doo_logging=%7B"sessionTracking"%3Atrue%2C"resourceRequests"%3Atrue%2C"httpRequests"%3A"all"%7D

Hide the access code field or directly show the access code entry field

doo_access_code_field

Hide the promotion code field or directly show the promotion code entry field

Options: hidden, active

doo_promo_code_field

data-viovendi-event

Event id

data-viovendi-search-prefill

Filter events

Filter events by

doo_search_prefill

JSON stringify + encodeURIComponent

data-viovendi-event-filters

Add dropdown with options to filter events by attributes of checkboxes type

doo_event_filters

JSON stringify + encodeURIComponent

data-viovendi-event-attributes

someAttrName,canBeOtherName

• attribute names must not contain spaces, commas or other special characters

• applies listed attributes with logical AND

doo_event_attributes

Open the list-widget in the mode of the booking widget for the particular event.

doo_event_id

vv_event_id (legacy)

https://yourcompany.com/events/?doo_event_id=9128

• Salutation can be 1 (Herr/Mr.) or 2 (Frau/Mrs.);

  • don't add if you don't want a salutation

• Title can be 1 (Dr.) or 2 (Prof. Dr.);

  • don't add if you don't want a title

• NOTE: If you want to use custom values for Salutation and Title, please contact our doo Support Team under support@doo.net 

• Country needs to be a 2-letter ISO country code

• To prefill an external customer ID in a hidden field (for example an ID of an external CRM), include external_customer_id into the JSON object. For example:

• To define attendee type, include attendee_type into the JSON object. For example:

  • NOTE: If the value passed does not match any attendee type registration configured for the event, the attendee type information from the widget will be ignored (eg. system behaves as if no attendee type information was passed onto the widget). 
    
    

data-viovendi-form-id

doo form id

doo_form_id

vv_form_id (legacy)

data-viovendi-form-prefill

Form answers prefill

JSON representation of the array containing answers.

The prefill for questions should strictly follow the order in which the questions appear on the list.

["text prefill",[2,3],4] - text, checkboxes (natural indexes), stars

doo_form_prefill

vv_form_prefill (legacy)