Tool

Step: specific step of tool is viewable

context variables	description	required
name	name of the tool as described in tagging plan	yes
stepnumber	number of the step as described in tagging plan (use 1.1, 1.2 with optional steps)	yes
stepname	name of the specific step as described in tagging plan	yes
result	field values from the tool as described in tagging plan *be aware of which values are allowed to send!	no
option	changing option results in other flow like house owner or rental	no
type	type of tool e.g.: checkout, simulator, form, widget	no
placement	placement of tool on page	no

custom event

eventData: {
 "event": "tool-step",
 "info": {
  "name": "postcode 3check",
  "step": 0,
  "stepname": "postcode invoer"
}

data attribution

retueeryueiyeuyldfjsdlfjseoyu

Completestep: step of tool is completed (optional)

context variables	description	required
name	name of the tool as described in tagging plan	yes
stepnumber	number of the step as described in tagging plan (use 1.1, 1.2 with optional steps)	yes
stepname	name of the specific step as described in tagging plan	yes
result	field values from the tool as described in tagging plan *be aware of which values are allowed to send!	no
type	type of tool e.g.: checkout, simulator, form, widget	no
placement	placement of tool on page	no

custom event

eventData: {
 "event": "tool-step",
 "info": {
  "name": "postcode 3check",
  "step": 0,
  "stepname": "postcode invoer"
}

data attribution

retueeryueiyeuyldfjsdlfjseoyu

Laststep : last step of tool

context variables	description	required
name	name of the tool as described in tagging plan	yes
stepnumber	number of the step as described in tagging plan (use 1.1, 1.2 with optional steps)	yes
stepname	name of the specific step as described in tagging plan	yes
result	field values from the tool as described in tagging plan *be aware of which values are allowed to send!	yes
commerce	commerce object	no
option	changing option results in other flow like house owner or rental	no
type	type of tool e.g.: checkout, simulator, form, widget	no
placement	placement of tool on page	no

custom event

eventData: {
 "event": "tool-laststep",
 "info": {
  "name": "postcode 3check",
  "step": 1,
  "stepname": "laststep resultaat aanbod",
  "result": {
   "postcode": "9591b05332dd08ccf400747fe2a5bffa9dc0446a",
   "waardesturing": "laag",
   "metersoort": "enkel",
   "stroom": 0,
   "stroom-laag": 0,
   "gas": 0,
   "bewoners": 0
  }
 },

data attribution

retueeryueiyeuyldfjsdlfjseoyu

Error: error message is viewable

context variables	description	required
name	name of the tool as described in tagging plan	yes
stepnumber	number of the step as described in tagging plan (use 1.1, 1.2 with optional steps)	yes
stepname	name of the specific step as described in tagging plan	yes
fieldname	name of the specific field of the error	no
fieldtype	type of the field within the form	no
message	error message viewed by visitor	yes
errortype	type of error, e.g. by system or user	yes

custom event

eventData: {
 "event": "tool-fieldfocus",
 "info": {
  "name": "postcode 3check",
  "step": 0,
  "stepname": "postcode invoer",
  "fieldname": "postcode"
 },

data attribution

retueeryueiyeuyldfjsdlfjseoyu

Fieldfocus: Click on field

context variables	description	required
name	name of the tool as described in tagging plan	yes
stepnumber	number of the step as described in tagging plan (use 1.1, 1.2 with optional steps)	yes
stepname	name of the specific step as described in tagging plan	yes
fieldname	name of the specific field of the error	yes
fieldtype	type of the field within the form	no

custom event

eventData: {
 "event": "tool-fieldfocus",
 "info": {
  "name": "postcode 3check",
  "stepnumber": 0,
  "stepname": "postcode invoer",
  "fieldname": "postcode"
 }
}

data attribution

retueeryueiyeuyldfjsdlfjseoyu

Fieldcomplete: Field is filled, radiobutton or check box is selected

context variables	description	required
name	name of the tool as described in tagging plan	yes
stepnumber	number of the step as described in tagging plan (use 1.1, 1.2 with optional steps)	yes
stepname	name of the specific step as described in tagging plan	yes
fieldname	name of the specific field of the error	yes
fieldtype	type of the field within the form	no
value	value filled in the field *be aware of which values are allowed to send!	no

custom event

eventData: {
 "event": "tool-fieldcomplete",
 "info": {
  "name": "postcode 3check",
  "stepnumber": 0,
  "stepname": "postcode invoer",
  "fieldname": "postcode"
 }
}

data attribution

retueeryueiyeuyldfjsdlfjseoyu

Fieldvalidation: message below a field to describe why the value is not being accepted.

context variables	description	required
name	name of the tool as described in tagging plan	yes
stepnumber	number of the step as described in tagging plan (use 1.1, 1.2 with optional steps)	yes
stepname	name of the specific step as described in tagging plan	yes
fieldname	name of the specific field of the error ⁉️	yes
fieldtype	type of the field within the form	no
errortype	type of error, e.g. by system or user ⁉️	yes

custom event

eventData: {
 "event": "tool-fieldcomplete",
 "info": {
  "name": "postcode 3check",
  "stepnumber": 0,
  "stepname": "postcode invoer",
  "fieldname": "postcode"
 }

data attribution