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

var prefill = { first_name: 'John' };
encodeURIComponent(JSON.stringify(prefill))

{ 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: 

'<XXXX-XXXX-XXXX>'

for multi-use codes:

'<THE-CODE-YOU-DEFINED>'

doo_code

Widget bootstrap mode,

for starting with booking-edit login screen:

booker-login

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

booking-details

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: 

'<path_key>'

multiple:

'<path_key_1>,<path_key_2>,<path_key_3>'

doo_path_keys

Tickets prefill

data-viovendi-tickets-prefill='{
  "{{ticket_category_id}}": {{amount}},
  ...
}'

// example
data-viovendi-tickets-prefill='{
  "123": 1,
  "124": 3
}'

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

data-viovendi-ticket-selection-step-behavior="autosubmit"

doo_ticket_selection_step_behavior

Autosubmit information step

data-viovendi-attendee-data-step-behavior="autosubmit"

doo_information_step_behavior

Payment option prefill

data-viovendi-payment-option="{{ payment_option_internal_name }}"

// example
data-viovendi-payment-option="paypal"

doo_payment_option

Auto-accept terms & conditions

data-viovendi-terms-accepted="true"

doo_terms_accepted

Autosubmit information step

data-viovendi-payment-step-behavior="autosubmit"

doo_payment_step_behavior

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

data-viovendi-logging='{
  "sessionTracking": true,
  "resourceRequests": true,
  "httpRequests": "all"
}'

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

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

data-viovendi-access-code-field="active"
data-viovendi-access-code-field="hidden"

doo_access_code_field

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

Options: hidden, active

doo_promo_code_field

'{ 
    # default questions
	"salutation": 1, 
	"title": 1, 
	"first_name": "Hans", 
	"last_name": "Maier", 
	"company_name": "doo GmbH", 
	"country": "DE", 
	"street_name": "Hultschiner Str.", 
	"street_number": "8", 
	"zip": "81677", 
	"city": "München", 
	"email": "hans.maier@doo.net",
	
	# additional questions (text, paragraph, dropdown, date, phone, simple selection),
	"<question_name>": "<value>" 
	
	# additional questions (multiple selection),
	"<question_name>": ["1","2","4"],
	
	# additional questions (file)
    "<question_name>": {
      "file_name": "file-name.jpg",
      "file_path": "https://file-path"
    }
    
    # product,
	"<product_name>": 1
}'

• 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:

  Code Block
  language js
  '{ ...,  "external_customer_id": "0123456789", ... }'

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

  Code Block
  language js
  '{ ...,  "attendee_type": "Press", ... }'

  • 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).