🇬🇧 EN
🇬🇧 EN 🇹🇷 TR
Logo
☰ Dashboard
Shop

About WDC Campaign
WISDOMERA / WDIGITALCHANNEL

WDC Campaign

Defines execution, agenda, customer, and integration rules of a campaign.

Execution flow

For automatic execution, the campaign must be active and working, start type must be automatic, agenda time must be eligible, and an active channel design must exist. Success analysis requires additional follow-up, department, customer-persistence, and integration conditions.

Code limitations: Parameter 45 is saved but not read or applied; parameter 48 is not wired; parameter 36 has a schema-to-record-format mismatch.
0. status
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

0. status

Campaign parameter behavior and execution relationships

ID: 0 Type: select TR: durum EN: status

Description

Activation status of the campaign. Active is one of the required conditions for automatic execution; customer addition and agenda-generation checks fail for a passive campaign. Active alone is not sufficient: lifecycle must be working, start type must be automatic, the agenda must be eligible, and at least one active channel design must exist.

Options

Value Turkish English Behavior
0 pasif passive Excludes the campaign from automatic execution checks.
1 aktif active Includes the campaign in active execution checks.

Example

1 — aktif / active
1. life cycle
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

1. life cycle

Campaign parameter behavior and execution relationships

ID: 1 Type: select TR: yaşam döngüsü EN: life cycle

Description

Determines the design and execution stage of the campaign. With working lifecycle, active automatic campaigns may run when agenda and channel conditions are also eligible; planning, designing, testing, maintenance initiated, or cancelled does not satisfy the production automatic-execution condition.

Options

Value Turkish English Behavior
0 planlanıyor planning Keeps the campaign in the planning lifecycle and does not satisfy the automatic-execution condition.
1 dizayn ediliyor designing Keeps the campaign in the designing lifecycle and does not satisfy the automatic-execution condition.
2 test ediliyor testing Keeps the campaign in the testing lifecycle and does not satisfy the automatic-execution condition.
3 bakıma alındı maintenance initiated Keeps the campaign in the maintenance initiated lifecycle and does not satisfy the automatic-execution condition.
4 iptal edildi cancelled Keeps the campaign in the cancelled lifecycle and does not satisfy the automatic-execution condition.
5 çalışıyor working Selects the working lifecycle required by automatic campaign flows.

Example

5 — çalışıyor / working
2. contact details location
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

2. contact details location

Campaign parameter behavior and execution relationships

ID: 2 Type: select TR: iletişim detay lokasyonu EN: contact details location

Description

Determines where customer contact information such as telephone details is obtained. With integration, when the user application programming interface configuration in parameter 46 exists, its code is executed to obtain the customer list; with customer process, information stored in journey and customer records is used.

Options

Value Turkish English Behavior
0 entegrasyon integration Selects the integration behavior.
1 müşteri işlem customer process Selects the customer process behavior.

Example

0 — entegrasyon / integration
3. campaign name
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

3. campaign name

Campaign parameter behavior and execution relationships

ID: 3 Type: text TR: kampanya adı EN: campaign name

Description

Descriptive name used for the campaign in management screens and reports. A clear name distinguishes campaigns created for the same product or audience.

Example

Hasta Memnuniyeti 2026
4. campaign short name
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

4. campaign short name

Campaign parameter behavior and execution relationships

ID: 4 Type: text TR: kampanya kısa adı EN: campaign short name

Description

Short name that may be used in compact areas and integration output. When the full name is long, a short but distinctive value keeps lists and external-system mappings readable.

Example

HM-2026
5. save customer
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

5. save customer

Campaign parameter behavior and execution relationships

ID: 5 Type: select TR: müşteriyi kaydet EN: save customer

Description

Determines whether customer and journey records are persisted. Yes allows customer addition, automatic agenda, and success-analysis flows to create records; no specifically fails the success-analysis eligibility condition in the scheduler.

Options

Value Turkish English Behavior
0 hayır no Disables the related behavior.
1 evet yes Enables the related behavior.

Example

1 — evet / yes
6. product code
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

6. product code

Campaign parameter behavior and execution relationships

ID: 6 Type: text TR: ürün kodu EN: product code

Description

Business code associating the campaign with its product. When populated, external systems and reporting processes can separate campaign results by product; the inspected main campaign-execution condition does not use this field as a direct gate.

Example

HOSPITAL_SURVEY
7. external campaign id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

7. external campaign id

Campaign parameter behavior and execution relationships

ID: 7 Type: text TR: dış kampanya id EN: external campaign id

Description

Identifier of the campaign in an external system. The value is used for matching with external integrations; an empty or incorrect value may prevent external records from being associated with the correct campaign.

Example

CRM-CAMP-4821
8. genel bilgi
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

8. genel bilgi

Campaign parameter behavior and execution relationships

ID: 8 Type: text TR: information EN: genel bilgi

Description

General description of the campaign purpose, audience, and operational scope. The field is stored in configuration but does not directly participate in the automatic eligibility decision; detailed content helps campaign operators interpret the rules consistently.

Example

Taburcu hastalara 24 saat içinde anket gönderimi.
9. start type
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

9. start type

Campaign parameter behavior and execution relationships

ID: 9 Type: select TR: başlama tipi EN: start type

Description

Determines whether the campaign starts manually or automatically. With automatic, customer and channel flow may start when status is active, lifecycle is working, the agenda is eligible, and the channel list is populated; manual does not satisfy this automatic condition.

Options

Value Turkish English Behavior
0 manuel manuel Keeps the campaign in manual-start mode.
1 otomatik auto Enables automatic customer and channel flow when the agenda is eligible.

Example

1 — otomatik / auto
10. minimum time (days) for customer re-acceptance
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

10. minimum time (days) for customer re-acceptance

Campaign parameter behavior and execution relationships

ID: 10 Type: float TR: müşteri yeniden alınabilmesi için minimum süre (gün) EN: minimum time (days) for customer re-acceptance

Description

Minimum number of days that must pass after the previous start date before the same customer can be accepted into the campaign again. A new acceptance is rejected before the period expires; when empty, this day-based waiting check is not applied.

Example

30
11. automatically deactivate the customer after x days
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

11. automatically deactivate the customer after x days

Campaign parameter behavior and execution relationships

ID: 11 Type: select TR: müşteriyi x gün sonra otomatik pasif et EN: automatically deactivate the customer after x days

Description

Determines whether an active customer journey is automatically made passive after a number of days. When yes is selected and parameter 12 has a value, the duration is added to the start date; after current time passes that boundary, the journey is added to the deactivation list.

Options

Value Turkish English Behavior
0 hayır no Disables the related behavior.
1 evet yes Enables the related behavior.

Example

1 — evet / yes
12. after how many days will it automatically deactivate?
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

12. after how many days will it automatically deactivate?

Campaign parameter behavior and execution relationships

ID: 12 Type: float TR: kaç gün sonra otomatik pasif et EN: after how many days will it automatically deactivate?

Description

Number of days added to the journey start for automatic deactivation. The field is effective only when parameter 11 is yes; an empty value does not run the deactivation check.

Example

14
13. campaign type
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

13. campaign type

Campaign parameter behavior and execution relationships

ID: 13 Type: select TR: kampanya tipi EN: campaign type

Description

Determines whether the campaign is digital marketing, survey, or digital advertising. This selection controls which campaigns enter child flows such as survey-link generation and integration-based success analysis; the success scheduler accepts digital marketing and digital advertising types.

Options

Value Turkish English Behavior
0 dijital pazarlama digital marketing Selects the digital marketing behavior.
1 anket survey Selects the survey behavior.
2 dijital reklam digital advertising Selects the digital advertising behavior.

Example

1 — anket / survey
14. customer success followup time (day)
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

14. customer success followup time (day)

Campaign parameter behavior and execution relationships

ID: 14 Type: integer TR: müşteri başarı takip etme süresi (gün) EN: customer success followup time (day)

Description

Number of days for which success is followed after the last channel operation. Success analysis adds this duration to the last-operation date to calculate the end time and query-day range; when empty, scheduler eligibility for success analysis is not satisfied.

Example

30
15. select departrment
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

15. select departrment

Campaign parameter behavior and execution relationships

ID: 15 Type: list_parameter TR: departman seçimi EN: select departrment

Description

List carrying one or more department selections used in success analysis. Each item contains parameter 16 department value; the scheduler requires a nonempty list for integration-based success analysis.

Example

Kardiyoloji; Kalp ve damar cerrahisi
16. department
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

16. department

Campaign parameter behavior and execution relationships

ID: 16 Type: select TR: departman EN: department

Description

Healthcare service or organizational unit in the department list. Selected values determine success-query scope; choosing an incorrect unit may collect success from unrelated departments or fail to find target records.

Options

Value Turkish English Behavior
0 katlar floors Adds floors to success-follow-up scope.
1 doğumhane delivery room Adds delivery room to success-follow-up scope.
2 acil kliniği emergency clinic Adds emergency clinic to success-follow-up scope.
3 ağız diş ve çene cerrahisi oral and maxillofacial surgery Adds oral and maxillofacial surgery to success-follow-up scope.
4 ağız ve diş sağlığı oral and dental health Adds oral and dental health to success-follow-up scope.
5 ağız diş ve çene radyolojisi oral and maxillofacial radiology Adds oral and maxillofacial radiology to success-follow-up scope.
6 ağrı kliniği pain clinic Adds pain clinic to success-follow-up scope.
7 aile danışmanlığı family counseling Adds family counseling to success-follow-up scope.
8 aile hekimliği family medicine Adds family medicine to success-follow-up scope.
9 diğer other Adds other to success-follow-up scope.
10 akupunktur acupuncture Adds acupuncture to success-follow-up scope.
11 algoloji algology Adds algology to success-follow-up scope.
12 anestezi ve reanimasyon anesthesia and reanimation Adds anesthesia and reanimation to success-follow-up scope.
13 genel yoğun bakım general intensive care Adds general intensive care to success-follow-up scope.
14 aromaterapi aromatherapy Adds aromatherapy to success-follow-up scope.
15 beslenme ve diyetetik nutrition and dietetics Adds nutrition and dietetics to success-follow-up scope.
16 beyin cerrahisi brain surgery Adds brain surgery to success-follow-up scope.
17 beyin cerrahisi yoğun bakım neurosurgery intensive care Adds neurosurgery intensive care to success-follow-up scope.
18 bütüncül tıp holistic medicine Adds holistic medicine to success-follow-up scope.
19 cerrahi onkoloji surgical oncology Adds surgical oncology to success-follow-up scope.
20 cerrahi yoğun bakım surgical intensive care Adds surgical intensive care to success-follow-up scope.
21 check up check up Adds check up to success-follow-up scope.
22 cihaz el ve ayak sağlığı merkezi device hand and foot health center Adds device hand and foot health center to success-follow-up scope.
23 cihaz medikal estetik device medical aesthetics Adds device medical aesthetics to success-follow-up scope.
24 cihaz ses konuşma ve yutma bozuklukları device sound speech and swallowing disorders Adds device sound speech and swallowing disorders to success-follow-up scope.
25 çocuk acil child emergency Adds child emergency to success-follow-up scope.
26 çocuk allerjisi child allergy Adds child allergy to success-follow-up scope.
27 çocuk beslenme hastalıkları child nutritional diseases Adds child nutritional diseases to success-follow-up scope.
28 çocuk beyin ve sinir cerrahisi pediatric brain and neurosurgery Adds pediatric brain and neurosurgery to success-follow-up scope.
29 çocuk böbrek nakli pediatric kidney transplant Adds pediatric kidney transplant to success-follow-up scope.
30 çocuk cerrahisi pediatric surgery Adds pediatric surgery to success-follow-up scope.
31 çocuk endokrinoloji pediatric endocrinology Adds pediatric endocrinology to success-follow-up scope.
32 çocuk enfeksiyon hastalıkları pediatric infectious diseases Adds pediatric infectious diseases to success-follow-up scope.
33 çocuk gastroenteroloji pediatric gastroenterology Adds pediatric gastroenterology to success-follow-up scope.
34 çocuk gelişimi child development Adds child development to success-follow-up scope.
35 çocuk göğüs hastalıkları pediatric chest diseases Adds pediatric chest diseases to success-follow-up scope.
36 çocuk hematoloji pediatric hematology Adds pediatric hematology to success-follow-up scope.
37 çocuk immünoloji pediatric immunology Adds pediatric immunology to success-follow-up scope.
39 çocuk kalp ve damar cerrahisi pediatric cardiovascular surgery Adds pediatric cardiovascular surgery to success-follow-up scope.
40 çocuk karaciğer nakli pediatric liver transplantation Adds pediatric liver transplantation to success-follow-up scope.
41 çocuk kardiyoloji pediatric cardiology Adds pediatric cardiology to success-follow-up scope.
42 çocuk sağlığı ve hastalıkları child health and diseases Adds child health and diseases to success-follow-up scope.
43 çocuk üroloji pediatric urology Adds pediatric urology to success-follow-up scope.
44 çocuk nefrolojisi pediatric nephrology Adds pediatric nephrology to success-follow-up scope.
45 çocuk nöroloji child neurology Adds child neurology to success-follow-up scope.
46 çocuk onkoloji child oncology Adds child oncology to success-follow-up scope.
47 çocuk ortopedisi pediatric orthopedics Adds pediatric orthopedics to success-follow-up scope.
48 çocuk psikiyatri child psychiatry Adds child psychiatry to success-follow-up scope.
49 çocuk romatoloji pediatric rheumatology Adds pediatric rheumatology to success-follow-up scope.
50 denge merkezi balance center Adds balance center to success-follow-up scope.
51 dermatoloji dermatology Adds dermatology to success-follow-up scope.
52 dil ve konuşma terapisi speech and language therapy Adds speech and language therapy to success-follow-up scope.
53 diyabet kliniği diabetes clinic Adds diabetes clinic to success-follow-up scope.
54 diyabetik ayak diabetic foot Adds diabetic foot to success-follow-up scope.
55 el cerrahisi hand surgery Adds hand surgery to success-follow-up scope.
57 el ve ayak sağlığı hand and foot health Adds hand and foot health to success-follow-up scope.
58 elektrofizyoloji ve aritmi electrophysiology and arrhythmia Adds electrophysiology and arrhythmia to success-follow-up scope.
59 emzirme danışmanlığı ve relaktasyon polikliniği breastfeeding consultancy and relaxation clinic Adds breastfeeding consultancy and relaxation clinic to success-follow-up scope.
60 endodonti endodontics Adds endodontics to success-follow-up scope.
61 endokrin cerrahi endocrine surgery Adds endocrine surgery to success-follow-up scope.
62 endokrinoloji endocrinology Adds endocrinology to success-follow-up scope.
63 enfeksiyon hastaliklari yoğun bakim infectious diseases intensive care Adds infectious diseases intensive care to success-follow-up scope.
64 enfeksiyon hastalıkları infectious diseases Adds infectious diseases to success-follow-up scope.
65 enjeksiyon injection Adds injection to success-follow-up scope.
66 ergoterapist occupational therapist Adds occupational therapist to success-follow-up scope.
67 evde bakım home care Adds home care to success-follow-up scope.
68 fizik tedavi ve rehabilitasyon physical therapy and rehabilitation Adds physical therapy and rehabilitation to success-follow-up scope.
69 fonksiyonel tıp functional medicine Adds functional medicine to success-follow-up scope.
70 gastroenteroloji gastroenterology Adds gastroenterology to success-follow-up scope.
71 gastroenteroloji cerrahisi gastroenterology surgery Adds gastroenterology surgery to success-follow-up scope.
72 gastroenteroloji kliniği gastroenterology clinic Adds gastroenterology clinic to success-follow-up scope.
73 genel cerrahi general surgery Adds general surgery to success-follow-up scope.
74 geleneksel ve tamamlayıcı tıp traditional and complementary medicine Adds traditional and complementary medicine to success-follow-up scope.
75 genetik genetic Adds genetic to success-follow-up scope.
76 geriatri geriatrics Adds geriatrics to success-follow-up scope.
77 girişimsel radyoloji interventional radiology Adds interventional radiology to success-follow-up scope.
78 göğüs cerrahisi thoracic surgery Adds thoracic surgery to success-follow-up scope.
79 göğüs hastaliklari yoğun bakim chest diseases intensive care Adds chest diseases intensive care to success-follow-up scope.
80 göğüs hastalıkları chest diseases Adds chest diseases to success-follow-up scope.
81 göz hastalıkları eye diseases Adds eye diseases to success-follow-up scope.
82 hava ve uzay hekimliği aerospace medicine Adds aerospace medicine to success-follow-up scope.
83 hematoloji hematology Adds hematology to success-follow-up scope.
84 homeopati homeopathy Adds homeopathy to success-follow-up scope.
85 iç hastaliklari yoğun bakim internal diseases intensive care Adds internal diseases intensive care to success-follow-up scope.
86 iç hastalıkları internal medicine Adds internal medicine to success-follow-up scope.
87 immünoloji ve alerji hastalıkları immunology and allergic diseases Adds immunology and allergic diseases to success-follow-up scope.
88 inme merkezi stroke center Adds stroke center to success-follow-up scope.
89 inme merkezi yoğun bakim stroke center intensive care Adds stroke center intensive care to success-follow-up scope.
90 işyeri hekimliği workplace medicine Adds workplace medicine to success-follow-up scope.
91 iyot odası iodine room Adds iodine room to success-follow-up scope.
92 kadın hastalıkları ve doğum obstetrics and gynecology Adds obstetrics and gynecology to success-follow-up scope.
93 kalp sağlığı merkezi heart health center Adds heart health center to success-follow-up scope.
94 kalp ve damar cerrahisi cardiovascular surgery Adds cardiovascular surgery to success-follow-up scope.
95 kardiyoloji cardiology Adds cardiology to success-follow-up scope.
96 kulak burun boğaz kliniği ear, nose and throat clinic Adds ear, nose and throat clinic to success-follow-up scope.
97 kemoterapi chemotherapy Adds chemotherapy to success-follow-up scope.
98 kök hücre stem cell Adds stem cell to success-follow-up scope.
99 koroner yoğun bakım coronary intensive care Adds coronary intensive care to success-follow-up scope.
100 kardiyovasküler cerrahi yoğun bakım cardiovascular surgery intensive care Adds cardiovascular surgery intensive care to success-follow-up scope.
101 laboratuar laboratory Adds laboratory to success-follow-up scope.
102 medikal onkoloji medical oncology Adds medical oncology to success-follow-up scope.
103 medikal estetik medical aesthetics Adds medical aesthetics to success-follow-up scope.
104 meme cerrahisi breast surgery Adds breast surgery to success-follow-up scope.
105 meme sağlığı polikliniği breast health clinic Adds breast health clinic to success-follow-up scope.
106 mri mri Adds mri to success-follow-up scope.
107 nefrolofi kliniği nephrology clinic Adds nephrology clinic to success-follow-up scope.
108 nefroloji yoğun bakim nephrology intensive care Adds nephrology intensive care to success-follow-up scope.
109 neonatoloji neonatology Adds neonatology to success-follow-up scope.
110 nöroloji neurology Adds neurology to success-follow-up scope.
111 nöroloji yoğun bakim neurology intensive care Adds neurology intensive care to success-follow-up scope.
112 nöroradyoloji neuroradiology Adds neuroradiology to success-follow-up scope.
113 nükleer tıp nuclear medicine Adds nuclear medicine to success-follow-up scope.
114 obezite cerrahisi obesity surgery Adds obesity surgery to success-follow-up scope.
115 odyoloji ve konuşma bozuklukları audiology and speech disorders Adds audiology and speech disorders to success-follow-up scope.
116 odyometri audiometry Adds audiometry to success-follow-up scope.
117 omurga sağlığı ve skolyoz spine health and scoliosis Adds spine health and scoliosis to success-follow-up scope.
118 organ nakli transplantation Adds transplantation to success-follow-up scope.
119 ortodonti orthodontics Adds orthodontics to success-follow-up scope.
120 ortopedi ve travmatoloji orthopedics and traumatology Adds orthopedics and traumatology to success-follow-up scope.
121 ortopedi ve travmatoloji yoğun bakim orthopedics and traumatology intensive care Adds orthopedics and traumatology intensive care to success-follow-up scope.
122 palyatif bakım kliniği palliative care clinic Adds palliative care clinic to success-follow-up scope.
123 palyatif yoğun bakım palliative intensive care Adds palliative intensive care to success-follow-up scope.
124 pandemi kliniği pandemic clinic Adds pandemic clinic to success-follow-up scope.
125 parkinson ve hareket bozuklukları parkinsonism and movement disorders Adds parkinsonism and movement disorders to success-follow-up scope.
126 patoloji pathology Adds pathology to success-follow-up scope.
127 pedodonti pedodontics Adds pedodontics to success-follow-up scope.
128 perinatoloji perinatology Adds perinatology to success-follow-up scope.
129 periodontoloji periodontics Adds periodontics to success-follow-up scope.
130 plastik cerrahi plastic surgery Adds plastic surgery to success-follow-up scope.
131 podoloji podology Adds podology to success-follow-up scope.
132 protetik diş tedavisi prosthetic dental treatment Adds prosthetic dental treatment to success-follow-up scope.
133 psikiyatri psychiatry Adds psychiatry to success-follow-up scope.
134 psikoloji psychology Adds psychology to success-follow-up scope.
135 psikometrik testler (çocuk) psychometric tests (child) Adds psychometric tests (child) to success-follow-up scope.
136 radyasyon onkolojisi radiation oncology Adds radiation oncology to success-follow-up scope.
137 radyoloji radiological Adds radiological to success-follow-up scope.
138 restoratif diş tedavisi restorative dental treatment Adds restorative dental treatment to success-follow-up scope.
139 romatoloji rheumatology Adds rheumatology to success-follow-up scope.
140 saç ekimi hair transplantation Adds hair transplantation to success-follow-up scope.
141 sağlıklı yaşam healthy life Adds healthy life to success-follow-up scope.
142 spor hekimliği sports medicine Adds sports medicine to success-follow-up scope.
143 tıbbi farmakoloji medical pharmacology Adds medical pharmacology to success-follow-up scope.
144 tıbbi mikrobiyoloji medical microbiology Adds medical microbiology to success-follow-up scope.
145 tüp bebek test tube baby Adds test tube baby to success-follow-up scope.
146 üroloji urology Adds urology to success-follow-up scope.
147 uyku hastalıkları sleeping sickness Adds sleeping sickness to success-follow-up scope.
148 yara birimi wound unit Adds wound unit to success-follow-up scope.
149 yeni doğan kliniği newborn clinic Adds newborn clinic to success-follow-up scope.
150 yeni doğan yoğun bakım neonatal intensive care Adds neonatal intensive care to success-follow-up scope.
151 çocuk uyku polikliniği children's sleep clinic Adds children's sleep clinic to success-follow-up scope.
152 çocuk yoğun bakım pediatric intensive care Adds pediatric intensive care to success-follow-up scope.
153 dahiliye yoğun bakım internal medicine intensive care Adds internal medicine intensive care to success-follow-up scope.
154 kalp damar cerrahisi cardiovascular surgery Adds cardiovascular surgery to success-follow-up scope.
155 çocuk metabolizma hastalıkları pediatric metabolic diseases Adds pediatric metabolic diseases to success-follow-up scope.

Example

95 — kardiyoloji / cardiology
17. customer source
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

17. customer source

Campaign parameter behavior and execution relationships

ID: 17 Type: select TR: müşteri kaynağı EN: customer source

Description

Classifies whether the customer record originates from WisdomEra or the website. Source is used for reporting and flow separation; a value inconsistent with the actual source may group campaign performance incorrectly.

Options

Value Turkish English Behavior
0 wisdomera wisdomera Selects the wisdomera behavior.
1 website website Selects the website behavior.

Example

0 — wisdomera
18. advertisement type
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

18. advertisement type

Campaign parameter behavior and execution relationships

ID: 18 Type: select TR: reklam tipi EN: advertisement type

Description

Indicates whether the digital-advertising record is a lead form or an appointment. The selection defines processing and reporting context for advertising customers; when campaign type is not digital advertising, operational effect depends on the related flow.

Options

Value Turkish English Behavior
0 lead form lead form Selects the lead form behavior.
1 randevu appointment Selects the appointment behavior.

Example

0 — lead form
19. agenda type
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

19. agenda type

Campaign parameter behavior and execution relationships

ID: 19 Type: select TR: ajanda tipi EN: agenda type

Description

Agenda model determining the days and hours in which the campaign is eligible. Depending on the choice, fields 20 through 25 or 26 through 31 are used; when required day or hour values for the selected mode are empty, the campaign is not eligible in that time window.

Options

Value Turkish English Behavior
0 tüm günler ve saatler all days and hours Selects the all days and hours behavior.
1 seçilen gün ve saatler selected days and hours Selects the selected days and hours behavior.
2 tüm günler ve seçilen saatler all days and selected hours Selects the all days and selected hours behavior.
3 gün ve saat aralığı ayrı seç select day and hours range separately Selects the select day and hours range separately behavior.
4 tüm günler ve saat aralığı ayrı seç select all days and hours range separately Selects the select all days and hours range separately behavior.

Example

3 — gün ve saat aralığı ayrı seç
20. selected calendar hours for all days
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

20. selected calendar hours for all days

Campaign parameter behavior and execution relationships

ID: 20 Type: checkbox TR: tüm günlerde seçilen ajanda saatleri EN: selected calendar hours for all days

Description

List of individual hours applied commonly to all days. When agenda type uses selected hours, the time condition passes when the current Coordinated Universal Time hour is in this list; stored values are converted to hours 1 through 24 by adding one in code.

Options

Value Turkish English Behavior
0 1 1 Includes hour 1 in the related agenda rule.
1 2 2 Includes hour 2 in the related agenda rule.
2 3 3 Includes hour 3 in the related agenda rule.
3 4 4 Includes hour 4 in the related agenda rule.
4 5 5 Includes hour 5 in the related agenda rule.
5 6 6 Includes hour 6 in the related agenda rule.
6 7 7 Includes hour 7 in the related agenda rule.
7 8 8 Includes hour 8 in the related agenda rule.
8 9 9 Includes hour 9 in the related agenda rule.
9 10 10 Includes hour 10 in the related agenda rule.
10 11 11 Includes hour 11 in the related agenda rule.
11 12 12 Includes hour 12 in the related agenda rule.
12 13 13 Includes hour 13 in the related agenda rule.
13 14 14 Includes hour 14 in the related agenda rule.
14 15 15 Includes hour 15 in the related agenda rule.
15 16 16 Includes hour 16 in the related agenda rule.
16 17 17 Includes hour 17 in the related agenda rule.
17 18 18 Includes hour 18 in the related agenda rule.
18 19 19 Includes hour 19 in the related agenda rule.
19 20 20 Includes hour 20 in the related agenda rule.
20 21 21 Includes hour 21 in the related agenda rule.
21 22 22 Includes hour 22 in the related agenda rule.
22 23 23 Includes hour 23 in the related agenda rule.
23 24 24 Includes hour 24 in the related agenda rule.

Example

9, 10, 11
21. selected agenda days
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

21. selected agenda days

Campaign parameter behavior and execution relationships

ID: 21 Type: checkbox TR: seçilen ajanda günleri EN: selected agenda days

Description

Selects weekdays to which the common agenda rule applies. In the related agenda mode, when the current Coordinated Universal Time weekday is not in this list, the campaign is not time-eligible.

Options

Value Turkish English Behavior
0 pazartesi monday Includes monday in the related agenda rule.
1 salı tuesday Includes tuesday in the related agenda rule.
2 çarşamba wednesday Includes wednesday in the related agenda rule.
3 perşembe thursday Includes thursday in the related agenda rule.
4 cuma friday Includes friday in the related agenda rule.
5 cumartesi saturday Includes saturday in the related agenda rule.
6 pazar sunday Includes sunday in the related agenda rule.

Example

0, 1, 2, 3, 4
22. all agenda days start hour
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

22. all agenda days start hour

Campaign parameter behavior and execution relationships

ID: 22 Type: select TR: tüm ajanda günleri başlangıç saati EN: all agenda days start hour

Description

Boundary value of the common day-and-hour range. Code compares start and end inclusively and converts the stored option to hour 1 through 24 by adding one; when start is greater than end, the condition may not pass because no special overnight-range handling was found.

Options

Value Turkish English Behavior
0 1 1 Includes hour 1 in the related agenda rule.
1 2 2 Includes hour 2 in the related agenda rule.
2 3 3 Includes hour 3 in the related agenda rule.
3 4 4 Includes hour 4 in the related agenda rule.
4 5 5 Includes hour 5 in the related agenda rule.
5 6 6 Includes hour 6 in the related agenda rule.
6 7 7 Includes hour 7 in the related agenda rule.
7 8 8 Includes hour 8 in the related agenda rule.
8 9 9 Includes hour 9 in the related agenda rule.
9 10 10 Includes hour 10 in the related agenda rule.
10 11 11 Includes hour 11 in the related agenda rule.
11 12 12 Includes hour 12 in the related agenda rule.
12 13 13 Includes hour 13 in the related agenda rule.
13 14 14 Includes hour 14 in the related agenda rule.
14 15 15 Includes hour 15 in the related agenda rule.
15 16 16 Includes hour 16 in the related agenda rule.
16 17 17 Includes hour 17 in the related agenda rule.
17 18 18 Includes hour 18 in the related agenda rule.
18 19 19 Includes hour 19 in the related agenda rule.
19 20 20 Includes hour 20 in the related agenda rule.
20 21 21 Includes hour 21 in the related agenda rule.
21 22 22 Includes hour 22 in the related agenda rule.
22 23 23 Includes hour 23 in the related agenda rule.
23 24 24 Includes hour 24 in the related agenda rule.

Example

8
23. all agenda days end hour
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

23. all agenda days end hour

Campaign parameter behavior and execution relationships

ID: 23 Type: select TR: tüm ajanda günleri bitiş saati EN: all agenda days end hour

Description

Boundary value of the common day-and-hour range. Code compares start and end inclusively and converts the stored option to hour 1 through 24 by adding one; when start is greater than end, the condition may not pass because no special overnight-range handling was found.

Options

Value Turkish English Behavior
0 1 1 Includes hour 1 in the related agenda rule.
1 2 2 Includes hour 2 in the related agenda rule.
2 3 3 Includes hour 3 in the related agenda rule.
3 4 4 Includes hour 4 in the related agenda rule.
4 5 5 Includes hour 5 in the related agenda rule.
5 6 6 Includes hour 6 in the related agenda rule.
6 7 7 Includes hour 7 in the related agenda rule.
7 8 8 Includes hour 8 in the related agenda rule.
8 9 9 Includes hour 9 in the related agenda rule.
9 10 10 Includes hour 10 in the related agenda rule.
10 11 11 Includes hour 11 in the related agenda rule.
11 12 12 Includes hour 12 in the related agenda rule.
12 13 13 Includes hour 13 in the related agenda rule.
13 14 14 Includes hour 14 in the related agenda rule.
14 15 15 Includes hour 15 in the related agenda rule.
15 16 16 Includes hour 16 in the related agenda rule.
16 17 17 Includes hour 17 in the related agenda rule.
17 18 18 Includes hour 18 in the related agenda rule.
18 19 19 Includes hour 19 in the related agenda rule.
19 20 20 Includes hour 20 in the related agenda rule.
20 21 21 Includes hour 21 in the related agenda rule.
21 22 22 Includes hour 22 in the related agenda rule.
22 23 23 Includes hour 23 in the related agenda rule.
23 24 24 Includes hour 24 in the related agenda rule.

Example

18
24. selected agenda days start hour
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

24. selected agenda days start hour

Campaign parameter behavior and execution relationships

ID: 24 Type: select TR: seçilen ajanda günleri başlangıç saati EN: selected agenda days start hour

Description

Boundary value of the common day-and-hour range. Code compares start and end inclusively and converts the stored option to hour 1 through 24 by adding one; when start is greater than end, the condition may not pass because no special overnight-range handling was found.

Options

Value Turkish English Behavior
0 1 1 Includes hour 1 in the related agenda rule.
1 2 2 Includes hour 2 in the related agenda rule.
2 3 3 Includes hour 3 in the related agenda rule.
3 4 4 Includes hour 4 in the related agenda rule.
4 5 5 Includes hour 5 in the related agenda rule.
5 6 6 Includes hour 6 in the related agenda rule.
6 7 7 Includes hour 7 in the related agenda rule.
7 8 8 Includes hour 8 in the related agenda rule.
8 9 9 Includes hour 9 in the related agenda rule.
9 10 10 Includes hour 10 in the related agenda rule.
10 11 11 Includes hour 11 in the related agenda rule.
11 12 12 Includes hour 12 in the related agenda rule.
12 13 13 Includes hour 13 in the related agenda rule.
13 14 14 Includes hour 14 in the related agenda rule.
14 15 15 Includes hour 15 in the related agenda rule.
15 16 16 Includes hour 16 in the related agenda rule.
16 17 17 Includes hour 17 in the related agenda rule.
17 18 18 Includes hour 18 in the related agenda rule.
18 19 19 Includes hour 19 in the related agenda rule.
19 20 20 Includes hour 20 in the related agenda rule.
20 21 21 Includes hour 21 in the related agenda rule.
21 22 22 Includes hour 22 in the related agenda rule.
22 23 23 Includes hour 23 in the related agenda rule.
23 24 24 Includes hour 24 in the related agenda rule.

Example

9
25. selected agenda days end hour
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

25. selected agenda days end hour

Campaign parameter behavior and execution relationships

ID: 25 Type: select TR: seçilen ajanda günleri bitiş saati EN: selected agenda days end hour

Description

Boundary value of the common day-and-hour range. Code compares start and end inclusively and converts the stored option to hour 1 through 24 by adding one; when start is greater than end, the condition may not pass because no special overnight-range handling was found.

Options

Value Turkish English Behavior
0 1 1 Includes hour 1 in the related agenda rule.
1 2 2 Includes hour 2 in the related agenda rule.
2 3 3 Includes hour 3 in the related agenda rule.
3 4 4 Includes hour 4 in the related agenda rule.
4 5 5 Includes hour 5 in the related agenda rule.
5 6 6 Includes hour 6 in the related agenda rule.
6 7 7 Includes hour 7 in the related agenda rule.
7 8 8 Includes hour 8 in the related agenda rule.
8 9 9 Includes hour 9 in the related agenda rule.
9 10 10 Includes hour 10 in the related agenda rule.
10 11 11 Includes hour 11 in the related agenda rule.
11 12 12 Includes hour 12 in the related agenda rule.
12 13 13 Includes hour 13 in the related agenda rule.
13 14 14 Includes hour 14 in the related agenda rule.
14 15 15 Includes hour 15 in the related agenda rule.
15 16 16 Includes hour 16 in the related agenda rule.
16 17 17 Includes hour 17 in the related agenda rule.
17 18 18 Includes hour 18 in the related agenda rule.
18 19 19 Includes hour 19 in the related agenda rule.
19 20 20 Includes hour 20 in the related agenda rule.
20 21 21 Includes hour 21 in the related agenda rule.
21 22 22 Includes hour 22 in the related agenda rule.
22 23 23 Includes hour 23 in the related agenda rule.
23 24 24 Includes hour 24 in the related agenda rule.

Example

17
26. agenda days selection
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

26. agenda days selection

Campaign parameter behavior and execution relationships

ID: 26 Type: list_parameter TR: ajanda günleri seçimi EN: agenda days selection

Description

List defining separate hour behavior for each weekday. Each item carries the day, all-hours, selected-hours, or hour-range type and related hour values; when the same day is defined in multiple items, all items participate in evaluation.

Example

Pazartesi 09:00–17:00
27. selected agenda day
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

27. selected agenda day

Campaign parameter behavior and execution relationships

ID: 27 Type: select TR: seçilen ajanda günü EN: selected agenda day

Description

Weekday to which an agenda-day item applies. When the current Coordinated Universal Time weekday matches this value, the item’s hour-type check is performed; otherwise the item produces no eligibility for that day.

Options

Value Turkish English Behavior
0 pazartesi monday Includes monday in the related agenda rule.
1 salı tuesday Includes tuesday in the related agenda rule.
2 çarşamba wednesday Includes wednesday in the related agenda rule.
3 perşembe thursday Includes thursday in the related agenda rule.
4 cuma friday Includes friday in the related agenda rule.
5 cumartesi saturday Includes saturday in the related agenda rule.
6 pazar sunday Includes sunday in the related agenda rule.

Example

0 — pazartesi / monday
28. agenda hour type
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

28. agenda hour type

Campaign parameter behavior and execution relationships

ID: 28 Type: select TR: ajanda saat tipi EN: agenda hour type

Description

Determines whether all hours, individually selected hours, or a start-to-end range is used for the selected day. Selected-hours mode uses parameter 29, hour-range mode uses 30 and 31, and all-hours mode requires no additional hour boundary.

Options

Value Turkish English Behavior
0 tüm saatler all hours Selects the all hours behavior.
1 seçilen saatler selected hours Selects the selected hours behavior.
2 saat aralığı hour range Selects the hour range behavior.

Example

2 — saat aralığı / hour range
29. selected agenda hours
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

29. selected agenda hours

Campaign parameter behavior and execution relationships

ID: 29 Type: checkbox TR: seçilen ajanda saatleri EN: selected agenda hours

Description

Carries individually allowed hours in an agenda-day item. When hour type is selected hours, the item is eligible if the current hour appears in the list; values are evaluated in 1-through-24 form after adding one in code.

Options

Value Turkish English Behavior
0 1 1 Includes hour 1 in the related agenda rule.
1 2 2 Includes hour 2 in the related agenda rule.
2 3 3 Includes hour 3 in the related agenda rule.
3 4 4 Includes hour 4 in the related agenda rule.
4 5 5 Includes hour 5 in the related agenda rule.
5 6 6 Includes hour 6 in the related agenda rule.
6 7 7 Includes hour 7 in the related agenda rule.
7 8 8 Includes hour 8 in the related agenda rule.
8 9 9 Includes hour 9 in the related agenda rule.
9 10 10 Includes hour 10 in the related agenda rule.
10 11 11 Includes hour 11 in the related agenda rule.
11 12 12 Includes hour 12 in the related agenda rule.
12 13 13 Includes hour 13 in the related agenda rule.
13 14 14 Includes hour 14 in the related agenda rule.
14 15 15 Includes hour 15 in the related agenda rule.
15 16 16 Includes hour 16 in the related agenda rule.
16 17 17 Includes hour 17 in the related agenda rule.
17 18 18 Includes hour 18 in the related agenda rule.
18 19 19 Includes hour 19 in the related agenda rule.
19 20 20 Includes hour 20 in the related agenda rule.
20 21 21 Includes hour 21 in the related agenda rule.
21 22 22 Includes hour 22 in the related agenda rule.
22 23 23 Includes hour 23 in the related agenda rule.
23 24 24 Includes hour 24 in the related agenda rule.

Example

9, 10, 11
30. day start hour
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

30. day start hour

Campaign parameter behavior and execution relationships

ID: 30 Type: select TR: gün başlangıç saati EN: day start hour

Description

Start boundary of the hour range in an agenda-day item. When hour type is hour range, both boundaries are compared inclusively; the stored value is converted to its actual hour by adding one in code.

Options

Value Turkish English Behavior
0 1 1 Includes hour 1 in the related agenda rule.
1 2 2 Includes hour 2 in the related agenda rule.
2 3 3 Includes hour 3 in the related agenda rule.
3 4 4 Includes hour 4 in the related agenda rule.
4 5 5 Includes hour 5 in the related agenda rule.
5 6 6 Includes hour 6 in the related agenda rule.
6 7 7 Includes hour 7 in the related agenda rule.
7 8 8 Includes hour 8 in the related agenda rule.
8 9 9 Includes hour 9 in the related agenda rule.
9 10 10 Includes hour 10 in the related agenda rule.
10 11 11 Includes hour 11 in the related agenda rule.
11 12 12 Includes hour 12 in the related agenda rule.
12 13 13 Includes hour 13 in the related agenda rule.
13 14 14 Includes hour 14 in the related agenda rule.
14 15 15 Includes hour 15 in the related agenda rule.
15 16 16 Includes hour 16 in the related agenda rule.
16 17 17 Includes hour 17 in the related agenda rule.
17 18 18 Includes hour 18 in the related agenda rule.
18 19 19 Includes hour 19 in the related agenda rule.
19 20 20 Includes hour 20 in the related agenda rule.
20 21 21 Includes hour 21 in the related agenda rule.
21 22 22 Includes hour 22 in the related agenda rule.
22 23 23 Includes hour 23 in the related agenda rule.
23 24 24 Includes hour 24 in the related agenda rule.

Example

9
31. day end hour
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

31. day end hour

Campaign parameter behavior and execution relationships

ID: 31 Type: select TR: gün bitiş saati EN: day end hour

Description

End boundary of the hour range in an agenda-day item. When hour type is hour range, both boundaries are compared inclusively; the stored value is converted to its actual hour by adding one in code.

Options

Value Turkish English Behavior
0 1 1 Includes hour 1 in the related agenda rule.
1 2 2 Includes hour 2 in the related agenda rule.
2 3 3 Includes hour 3 in the related agenda rule.
3 4 4 Includes hour 4 in the related agenda rule.
4 5 5 Includes hour 5 in the related agenda rule.
5 6 6 Includes hour 6 in the related agenda rule.
6 7 7 Includes hour 7 in the related agenda rule.
7 8 8 Includes hour 8 in the related agenda rule.
8 9 9 Includes hour 9 in the related agenda rule.
9 10 10 Includes hour 10 in the related agenda rule.
10 11 11 Includes hour 11 in the related agenda rule.
11 12 12 Includes hour 12 in the related agenda rule.
12 13 13 Includes hour 13 in the related agenda rule.
13 14 14 Includes hour 14 in the related agenda rule.
14 15 15 Includes hour 15 in the related agenda rule.
15 16 16 Includes hour 16 in the related agenda rule.
16 17 17 Includes hour 17 in the related agenda rule.
17 18 18 Includes hour 18 in the related agenda rule.
18 19 19 Includes hour 19 in the related agenda rule.
19 20 20 Includes hour 20 in the related agenda rule.
20 21 21 Includes hour 21 in the related agenda rule.
21 22 22 Includes hour 22 in the related agenda rule.
22 23 23 Includes hour 23 in the related agenda rule.
23 24 24 Includes hour 24 in the related agenda rule.

Example

17
32. wanalyzer project client id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

32. wanalyzer project client id

Campaign parameter behavior and execution relationships

ID: 32 Type: text TR: wanalyzer proje client id EN: wanalyzer project client id

Description

Client identifier connecting the campaign to a Wanalyzer project. The field is read into configuration; however, no active algorithm call directly using this identifier was found in the inspected Wdigitalchannel campaign-execution code, so it must not be assumed to start analysis by itself.

Example

wanalyzer-project-uuid
33. algorithm id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

33. algorithm id

Campaign parameter behavior and execution relationships

ID: 33 Type: text TR: algoritma id EN: algorithm id

Description

Algorithm identifier stored for association with the campaign. Although record and CampaignConfig code carry the field, the frontend get model has it commented out and no other use was found in inspected execution code; its current operational effect is unverified.

Example

algorithm-uuid
34. create date
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

34. create date

Campaign parameter behavior and execution relationships

ID: 34 Type: datetime TR: oluşturma tarihi EN: create date

Description

Creation time information of the campaign record. The record service stores the value supplied by the client; inspected code does not forcibly set it to current server time, so accuracy depends on the value sent by the caller.

Example

2026-10-25T09:30:00
35. update date
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

35. update date

Campaign parameter behavior and execution relationships

ID: 35 Type: datetime TR: güncelleme tarihi EN: update date

Description

Update time information of the campaign record. The record service stores the value supplied by the client; inspected code does not forcibly set it to current server time, so accuracy depends on the value sent by the caller.

Example

2026-10-25T10:15:00
36. wtransfer select api
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

36. wtransfer select api

Campaign parameter behavior and execution relationships

ID: 36 Type: text TR: wtransfer api seçimi EN: wtransfer select api

Description

Selects the Wtransfer user application programming interface record used for campaign data transfer. The configurator loads the API record by identifier and attempts to obtain an access token; however, the layer type is text while record and get code expect a selection object, creating a schema-to-application format mismatch that requires end-to-end testing.

Example

wtransfer-api-client-id
37. powerbi api campaign record id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

37. powerbi api campaign record id

Campaign parameter behavior and execution relationships

ID: 37 Type: text TR: powerbi api kampanya kaydı id EN: powerbi api campaign record id

Description

Client identifier of the user application programming interface record executed for the Power BI campaign record. When populated, the configurator loads the API code and uses it to create an external record for the related event; when the identifier cannot be found, configuration may enter an error state.

Example

powerbi-campaign-api-id
38. survey link create type
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

38. survey link create type

Campaign parameter behavior and execution relationships

ID: 38 Type: select TR: anket linki oluşturma tipi EN: survey link create type

Description

Determines whether the survey link is generated by Wdigitalchannel or an external user application programming interface. With Wdigitalchannel, an internal survey link is prepared; with other survey link, the API code in parameter 39 is executed.

Options

Value Turkish English Behavior
0 wdc anket linki wdc survey link Selects the wdc survey link behavior.
1 diğer anket linki other survey link Selects the other survey link behavior.

Example

0 — wdc anket linki / wdc survey link
39. other survey link api
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

39. other survey link api

Campaign parameter behavior and execution relationships

ID: 39 Type: text TR: diğer anket linki api EN: other survey link api

Description

User application programming interface record used to generate an external survey link. The field is visible only when parameter 38 is other survey link and its code is executed during customer addition when available; when empty, an external link cannot be generated.

Example

external-survey-api-id
40. success analyze with integration
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

40. success analyze with integration

Campaign parameter behavior and execution relationships

ID: 40 Type: select TR: entegrasyon ile başarı analizi EN: success analyze with integration

Description

Determines whether campaign success is analyzed with integration data. Yes enters scheduler analysis only when follow-up days, departments, persisted customer, eligible campaign type, and production conditions are also satisfied. The current frontend visibility rule displays parameter 47 API field for no, creating a reversed-condition risk between this field and the user interface.

Options

Value Turkish English Behavior
0 hayır no Disables the related behavior.
1 evet yes Enables the related behavior.

Example

1 — evet / yes
41. username
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

41. username

Campaign parameter behavior and execution relationships

ID: 41 Type: text TR: kullanıcı adı EN: username

Description

Username associated with campaign operations. The field is stored in configuration and is not a direct decision condition in the inspected core eligibility and agenda algorithms, so it should be entered consistently for identity and reporting purposes.

Example

campaign.operator
42. survey validity period hours
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

42. survey validity period hours

Campaign parameter behavior and execution relationships

ID: 42 Type: integer TR: anket geçerlilik süresi saat EN: survey validity period hours

Description

Determines how many hours a generated survey link remains valid. When populated, it is added to the internal survey-link route as expire_hours and used by scheduler duration calculation; when empty, no hour-based duration is supplied from this campaign field.

Example

72
43. powerbi api channel operastion record id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

43. powerbi api channel operastion record id

Campaign parameter behavior and execution relationships

ID: 43 Type: text TR: powerbi api kanal operasyon kaydı id EN: powerbi api channel operastion record id

Description

Client identifier of the user application programming interface record executed for the Power BI channel-operation record. When populated, the configurator loads the API code and uses it to create an external record for the related event; when the identifier cannot be found, configuration may enter an error state.

Example

powerbi-channel-operation-api-id
44. powerbi api journey record id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

44. powerbi api journey record id

Campaign parameter behavior and execution relationships

ID: 44 Type: text TR: powerbi api journey kaydı id EN: powerbi api journey record id

Description

Client identifier of the user application programming interface record executed for the Power BI journey record. When populated, the configurator loads the API code and uses it to create an external record for the related event; when the identifier cannot be found, configuration may enter an error state.

Example

powerbi-journey-api-id
45. success analyze completed journeys
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

45. success analyze completed journeys

Campaign parameter behavior and execution relationships

ID: 45 Type: select TR: sonlanmış yolculukların başarı analizi EN: success analyze completed journeys

Description

Field storing the request to include completed journeys in success analysis. New and edit services save parameter 45; however, inspected CampaignConfig and campaign get service do not read it and execution code does not use it, so its behavioral effect is unverified in the current version.

Options

Value Turkish English Behavior
0 hayır no Disables the related behavior.
1 evet yes Enables the related behavior.

Example

1 — evet / yes
46. contact details api id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

46. contact details api id

Campaign parameter behavior and execution relationships

ID: 46 Type: text TR: iletişim detay api id EN: contact details api id

Description

Client identifier of the campaign-specific user application programming interface record used to retrieve contact details. When populated, CampaignConfig loads the API code and the code is executed when the related condition is active. If the identifier or code is missing, the integration branch cannot produce data.

Example

contact-details-api-id
47. success analyze api id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

47. success analyze api id

Campaign parameter behavior and execution relationships

ID: 47 Type: text TR: başarı analiz api id EN: success analyze api id

Description

Client identifier of the campaign-specific user application programming interface record used to execute success analysis. When populated, CampaignConfig loads the API code and the code is executed when the related condition is active. If the identifier or code is missing, the integration branch cannot produce data.

Example

success-analysis-api-id
48. powerbi api journey success record id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN

48. powerbi api journey success record id

Campaign parameter behavior and execution relationships

ID: 48 Type: text TR: powerbi api journey başarı kaydı id EN: powerbi api journey success record id

Description

Identifier field designated for the Power BI journey-success record. Parameter 48 is not wired in inspected campaign new, edit, get, CampaignConfig, or execution code; therefore it must not be presented as saved or executed and must not be treated as operational until implementation is completed.

Example

powerbi-journey-success-api-id
About WDC Campaign / Customer
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Customer

Tracks the persistent campaign record and re-acceptance time of a customer.

Customer flow

A new customer is stored as active. When the same customer arrives again, the campaign waiting period is added to the last process start; after expiry, the record is updated and a new journey is created.

Layer separation: Customer status and journey status are different. No automatic write behavior for passived date was found in inspected customer code.
0. status
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN / CUSTOMER

0. status

Campaign-customer record behavior and re-acceptance relationships

ID: 0 Type: select TR: durum EN: status

Description

Activation status of the campaign-customer record. The field is created as active when a new customer is accepted, and the prepared record also carries active when an existing customer is accepted again. Because the inspected customer-list service applies no status filter, a passive record is not automatically hidden from the list; this status must be evaluated separately from statuses of child journeys.

Options

Value Turkish English Behavior
0 pasif passive Marks the customer record as passive; the list service does not automatically filter by this value.
1 aktif active Active value used for newly accepted and re-accepted customer records.

Example

1 — aktif / active
1. campaign id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN / CUSTOMER

1. campaign id

Campaign-customer record behavior and re-acceptance relationships

ID: 1 Type: text TR: kampanya id EN: campaign id

Description

Client identifier connecting the customer record to its owning Wdigitalchannel campaign. Because the record client identifier is produced by combining campaign and customer identifiers and its layer path is created under the campaign, the correct campaign identifier determines both uniqueness and listing context.

Example

campaign-uuid
2. customer id
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN / CUSTOMER

2. customer id

Campaign-customer record behavior and re-acceptance relationships

ID: 2 Type: text TR: müşteri id EN: customer id

Description

Source-system identifier distinguishing the customer from other customers in the campaign. Code combines this value with the campaign identifier to create the persistent customer client identifier; when the same customer identifier arrives again in the same campaign, the existing record is found and its re-acceptance period is checked instead of creating another customer record.

Example

CUSTOMER-10428
3. last customer process start date
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN / CUSTOMER

3. last customer process start date

Campaign-customer record behavior and re-acceptance relationships

ID: 3 Type: datetime TR: son müşteri işlem başlama tarihi EN: last customer process start date

Description

Most recent accepted process or journey start time of the customer in the campaign. It is written with current Coordinated Universal Time for both new and re-accepted records. The campaign minimum re-acceptance days are added to this date; when the calculated eligibility date is earlier than current time, the customer is accepted again and a new journey is created.

Example

2026-10-25T09:30:00
4. create date
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN / CUSTOMER

4. create date

Campaign-customer record behavior and re-acceptance relationships

ID: 4 Type: datetime TR: oluşturma tarihi EN: create date

Description

Time when the campaign-customer record is first created. Code fills this field with current Coordinated Universal Time only for a new record; for an existing customer accepted again, creation time is not rewritten and parameter 5 update date is added instead.

Example

2026-10-01T08:15:00
5. update date
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN / CUSTOMER

5. update date

Campaign-customer record behavior and re-acceptance relationships

ID: 5 Type: datetime TR: güncelleme tarihi EN: update date

Description

Time when an existing customer record is renewed after satisfying the re-acceptance condition. This field is not written while creating a new customer; when the campaign waiting period added to the previous process start has expired, it is filled with current time and parameter 3 last start is renewed in the same operation.

Example

2026-10-25T09:30:00
6. passived date
WISDOMERA / WDIGITALCHANNEL / WDC CAMPAIGN / CUSTOMER

6. passived date

Campaign-customer record behavior and re-acceptance relationships

ID: 6 Type: datetime TR: pasife alınma tarihi EN: passived date

Description

Field defined to store the time when the customer record is made passive. No operation writing this parameter or using it in a behavioral decision was found in the inspected campaign-customer record, get, and list code. Journey deactivation caused by duration expiry occurs in a separate child layer, so this field must not be assumed to be filled automatically.

Example

2026-11-10T12:00:00
About WDC Campaign / Customer / Journey
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Customer / Journey

Tracks channel progression, agenda, successes, clicks, and communication context for one customer campaign journey.

Journey flow

A new record starts as active with success status set to continue. The campaign agenda produces eligible times, channel selection evaluates contact information and permissions, and click and success details are added as operations progress. The record may be made passive when no eligible channel or required contact information is available, or when the journey ends.

Code finding: Customer-acceptance code writes country name to parameter 63 instead of 64 and can overwrite country code. The current behavior is stated separately in the descriptions of parameters 63 and 64.
0. status

0. status

Parameter identifier: 0 Data type: select
Turkish name durum
English name status

Description

Specifies whether the journey record participates in the processing cycle. A new journey is created as active. If no eligible channel is found, the customer is deceased, contact information is unavailable, or the channel flow ends the journey, the code makes the record passive and writes the passived date; a passive record does not enter the active channel-processing query.

Options

Value Turkish English Behavior
0 pasif passive Removes the journey from active channel processing.
1 aktif active Includes the journey in active processing.

Example

0 — passive
1. customer id

1. customer id

Parameter identifier: 1 Data type: text
Turkish name müşteri id
English name customer id

Description

The source-system identifier of the customer who owns the journey. The code carries this value into the journey configuration and associates operation, report, and success-analysis records with the same customer; an incorrect value causes results to be associated with another customer.

Example

1-example
2. passived date

2. passived date

Parameter identifier: 2 Data type: datetime
Turkish name pasife alınma tarihi
English name passived date

Description

The Coordinated Universal Time at which the journey was removed from active status. When the passivation method sets status to `0`, it writes the current time to this field; therefore, filling only the date does not make the journey passive, because the status field is decisive.

Example

2026-10-25T09:30:00
3. success status

3. success status

Parameter identifier: 3 Data type: select
Turkish name başarı durumu
English name success status

Description

Tracks the overall success result of the journey. The record starts as `continue`; after success analysis evaluates the campaign’s primary and secondary success rules, it changes the result to `success` or `unsuccess`. This field is separate from channel step status: campaign success is analyzed independently even if channel delivery has completed.

Options

Value Turkish English Behavior
0 devam ediyor continue Interprets the field as “continue”; business rules are evaluated according to this selected state.
1 başarılı success Interprets the field as “success”; business rules are evaluated according to this selected state.
2 başarısız unsuccess Interprets the field as “unsuccess”; business rules are evaluated according to this selected state.

Example

0 — continue
4. success channel type

4. success channel type

Parameter identifier: 4 Data type: select
Turkish name başarı kanal tipi
English name success channel type

Description

Stores the communication channel associated with success. The code interprets the values as SMS, push notification, IVR, email, and phone call so the success report can distinguish which channel produced the result. The field may remain empty until success occurs.

Options

Value Turkish English Behavior
0 sms sms Associates success with the “sms” channel.
1 mobil bildirim push notification Associates success with the “push notification” channel.
2 ivr ivr Associates success with the “ivr” channel.
3 mail mail Associates success with the “mail” channel.
4 telefon ile arama phone call Associates success with the “phone call” channel.

Example

0 — sms
5. channel step status

5. channel step status

Parameter identifier: 5 Data type: select
Turkish name kanal adım durumu
English name channel step status

Description

The progress result of the journey through campaign channel steps. `continue` means the next eligible step may be searched, `complete` means the step chain has completed, and `not complete` means the chain could not be completed; channel selection and the next processing decision are evaluated together with this status.

Options

Value Turkish English Behavior
0 devam ediyor continue Interprets the field as “continue”; business rules are evaluated according to this selected state.
1 tamamlandı complete Interprets the field as “complete”; business rules are evaluated according to this selected state.
2 tamamlanmadı not complete Interprets the field as “not complete”; business rules are evaluated according to this selected state.

Example

0 — continue
6. selected campaign channel setting id

6. selected campaign channel setting id

Parameter identifier: 6 Data type: text
Turkish name seçilen kampanya kanal ayarı id
English name selected campaign channel setting id

Description

The client identifier of the campaign channel-setting record selected for the journey. Eligible-channel selection writes this identifier and the step index into the configuration; the subsequent channel operation resolves message, provider, and scheduling settings from that record. If no eligible setting is found, the journey may be made passive.

Example

6-example
7. start date

7. start date

Parameter identifier: 7 Data type: datetime
Turkish name başlama tarihi
English name start date

Description

The Coordinated Universal Time at which the journey starts, written with the current time during customer acceptance. Channel and success processes track the journey’s time context from this start; although it is close to the create date, its business meaning is the journey start.

Example

2026-10-25T09:30:00
8. firstname

8. firstname

Parameter identifier: 8 Data type: text
Turkish name adı
English name firstname

Description

The customer’s first name received from source data. It is carried into the journey configuration for channel-message personalization and reporting; if the source value is absent, the code does not add the field.

Example

8-example
9. lastname

9. lastname

Parameter identifier: 9 Data type: text
Turkish name soyad
English name lastname

Description

The customer’s last name received from source data. Together with the first name it provides personalization and reporting context; if the source value is empty, it is not written when the journey is created.

Example

9-example
10. institution name

10. institution name

Parameter identifier: 10 Data type: text
Turkish name kurum adı
English name institution name

Description

The name of the institution associated with the customer. It provides context especially for institution-based channel-provider and reporting distinctions; it is copied into the journey when present in customer input.

Example

10-example
11. institution code

11. institution code

Parameter identifier: 11 Data type: text
Turkish name kurum kodu
English name institution code

Description

The institution’s source-system code. Because channel processing can distinguish institution-based configurations with this code, it is a machine-used matching value rather than the display name.

Example

11-example
12. institution department name

12. institution department name

Parameter identifier: 12 Data type: text
Turkish name kurum departman adı
English name institution department name

Description

The customer’s department information within the institution. It is received from source customer data and carried into channel and reporting context; no department is derived automatically when it is empty.

Example

12-example
13. nation language

13. nation language

Parameter identifier: 13 Data type: select
Turkish name uyruk dili
English name nation language

Description

The language code to use when sending content to the customer. The source `NationLanguage` value is written here; when a channel template is selected by language, the correct code allows the appropriate content to be found, while an empty or incompatible code may prevent language matching.

Options

Value Turkish English Behavior
0 TR TR Stores the record with the “TR” classification and uses this value in matching and reporting.
1 AZ AZ Stores the record with the “AZ” classification and uses this value in matching and reporting.
2 EN EN Stores the record with the “EN” classification and uses this value in matching and reporting.
3 FA FA Stores the record with the “FA” classification and uses this value in matching and reporting.
4 DE DE Stores the record with the “DE” classification and uses this value in matching and reporting.
5 CA CA Stores the record with the “CA” classification and uses this value in matching and reporting.
6 PT PT Stores the record with the “PT” classification and uses this value in matching and reporting.
7 ES ES Stores the record with the “ES” classification and uses this value in matching and reporting.
8 SQ SQ Stores the record with the “SQ” classification and uses this value in matching and reporting.
9 NL NL Stores the record with the “NL” classification and uses this value in matching and reporting.
10 TKL TKL Stores the record with the “TKL” classification and uses this value in matching and reporting.
11 AR AR Stores the record with the “AR” classification and uses this value in matching and reporting.
12 BN BN Stores the record with the “BN” classification and uses this value in matching and reporting.
13 BE BE Stores the record with the “BE” classification and uses this value in matching and reporting.
14 FR FR Stores the record with the “FR” classification and uses this value in matching and reporting.
15 BS BS Stores the record with the “BS” classification and uses this value in matching and reporting.
16 MS MS Stores the record with the “MS” classification and uses this value in matching and reporting.
17 BG BG Stores the record with the “BG” classification and uses this value in matching and reporting.
18 DZ DZ Stores the record with the “DZ” classification and uses this value in matching and reporting.
19 CS CS Stores the record with the “CS” classification and uses this value in matching and reporting.
20 ZH ZH Stores the record with the “ZH” classification and uses this value in matching and reporting.
21 DA DA Stores the record with the “DA” classification and uses this value in matching and reporting.
22 ID ID Stores the record with the “ID” classification and uses this value in matching and reporting.
23 TI TI Stores the record with the “TI” classification and uses this value in matching and reporting.
24 HY HY Stores the record with the “HY” classification and uses this value in matching and reporting.
25 ET ET Stores the record with the “ET” classification and uses this value in matching and reporting.
26 AM AM Stores the record with the “AM” classification and uses this value in matching and reporting.
27 FO FO Stores the record with the “FO” classification and uses this value in matching and reporting.
28 FI FI Stores the record with the “FI” classification and uses this value in matching and reporting.
29 KL KL Stores the record with the “KL” classification and uses this value in matching and reporting.
30 KO KO Stores the record with the “KO” classification and uses this value in matching and reporting.
31 KA KA Stores the record with the “KA” classification and uses this value in matching and reporting.
32 HR HR Stores the record with the “HR” classification and uses this value in matching and reporting.
33 HI HI Stores the record with the “HI” classification and uses this value in matching and reporting.
34 HE HE Stores the record with the “HE” classification and uses this value in matching and reporting.
35 SV SV Stores the record with the “SV” classification and uses this value in matching and reporting.
36 IT IT Stores the record with the “IT” classification and uses this value in matching and reporting.
37 IS IS Stores the record with the “IS” classification and uses this value in matching and reporting.
38 JA JA Stores the record with the “JA” classification and uses this value in matching and reporting.
39 KM KM Stores the record with the “KM” classification and uses this value in matching and reporting.
40 KK KK Stores the record with the “KK” classification and uses this value in matching and reporting.
41 EL EL Stores the record with the “EL” classification and uses this value in matching and reporting.
42 KY KY Stores the record with the “KY” classification and uses this value in matching and reporting.
43 LO LO Stores the record with the “LO” classification and uses this value in matching and reporting.
44 LV LV Stores the record with the “LV” classification and uses this value in matching and reporting.
45 LT LT Stores the record with the “LT” classification and uses this value in matching and reporting.
46 LB LB Stores the record with the “LB” classification and uses this value in matching and reporting.
47 HU HU Stores the record with the “HU” classification and uses this value in matching and reporting.
48 MG MG Stores the record with the “MG” classification and uses this value in matching and reporting.
49 MK MK Stores the record with the “MK” classification and uses this value in matching and reporting.
50 DV DV Stores the record with the “DV” classification and uses this value in matching and reporting.
51 MT MT Stores the record with the “MT” classification and uses this value in matching and reporting.
52 MN MN Stores the record with the “MN” classification and uses this value in matching and reporting.
53 RO RO Stores the record with the “RO” classification and uses this value in matching and reporting.
54 NE NE Stores the record with the “NE” classification and uses this value in matching and reporting.
55 NO NO Stores the record with the “NO” classification and uses this value in matching and reporting.
56 UZ UZ Stores the record with the “UZ” classification and uses this value in matching and reporting.
57 UR UR Stores the record with the “UR” classification and uses this value in matching and reporting.
58 PL PL Stores the record with the “PL” classification and uses this value in matching and reporting.
59 RW RW Stores the record with the “RW” classification and uses this value in matching and reporting.
60 RU RU Stores the record with the “RU” classification and uses this value in matching and reporting.
61 SR SR Stores the record with the “SR” classification and uses this value in matching and reporting.
62 SK SK Stores the record with the “SK” classification and uses this value in matching and reporting.
63 SL SL Stores the record with the “SL” classification and uses this value in matching and reporting.
64 SI SI Stores the record with the “SI” classification and uses this value in matching and reporting.
65 SW SW Stores the record with the “SW” classification and uses this value in matching and reporting.
66 TH TH Stores the record with the “TH” classification and uses this value in matching and reporting.
67 TO TO Stores the record with the “TO” classification and uses this value in matching and reporting.
68 TVL TVL Stores the record with the “TVL” classification and uses this value in matching and reporting.
69 TK TK Stores the record with the “TK” classification and uses this value in matching and reporting.
70 UK UK Stores the record with the “UK” classification and uses this value in matching and reporting.
71 BI BI Stores the record with the “BI” classification and uses this value in matching and reporting.
72 VI VI Stores the record with the “VI” classification and uses this value in matching and reporting.
73 TG TG Stores the record with the “TG” classification and uses this value in matching and reporting.
74 SO SO Stores the record with the “SO” classification and uses this value in matching and reporting.
75 MY MY Stores the record with the “MY” classification and uses this value in matching and reporting.
76 Stores the record with the “” classification and uses this value in matching and reporting.
77 NIU NIU Stores the record with the “NIU” classification and uses this value in matching and reporting.
78 SM SM Stores the record with the “SM” classification and uses this value in matching and reporting.

Example

0 — TR
14. country phone code + gsm

14. country phone code + gsm

Parameter identifier: 14 Data type: text
Turkish name ülke telefon kodu + gsm
English name country phone code + gsm

Description

The combined contact value containing the country calling code and GSM number. Customer-acceptance code writes the source `PhoneNumber` field here; phone-based channels can use it when they require the full number, while the separate parts are also stored in parameters 15 and 16.

Example

14-example
15. country phone code

15. country phone code

Parameter identifier: 15 Data type: text
Turkish name ülke telefon kodu
English name country phone code

Description

The country calling code of the phone number, received from source `PhoneCountryCode`. It enables construction of the correct international address with the GSM number; by itself it is not the complete number to contact.

Example

15-example
16. gsm number

16. gsm number

Parameter identifier: 16 Data type: text
Turkish name gsm no
English name gsm number

Description

The GSM number stored separately from the country code, received from source `PhoneGsm`. It is used in contact-information checks when SMS, IVR, or phone call is selected; the journey may be made passive if required phone information is unavailable.

Example

16-example
17. email

17. email

Parameter identifier: 17 Data type: text
Turkish name mail
English name email

Description

The customer’s email address, received from source `Mail`. It supplies the delivery address when the email channel is selected; if a valid contact value is unavailable, channel processing cannot be performed and the journey may be ended.

Example

17-example
18. mobile notification id

18. mobile notification id

Parameter identifier: 18 Data type: text
Turkish name mobil bildirim id
English name mobile notification id

Description

The customer’s device- or subscription-based push-notification identifier. It identifies the target for the mobile-notification channel; when it is absent from direct customer data, channel processing may attempt to complete it from the wtransfer-based contact-detail source.

Example

18-example
19. mobile notification group id

19. mobile notification group id

Parameter identifier: 19 Data type: text
Turkish name mobil bildirim grubu id
English name mobile notification group id

Description

The identifier of the mobile-notification group associated with the customer. It is used when the push-notification provider requires group-based targeting and is carried into the journey from source `PushNotificationGroup`.

Example

19-example
20. api variables

20. api variables

Parameter identifier: 20 Data type: textarea
Turkish name api değişkenleri
English name api variables

Description

The JSON text of the customer object received in the customer-acceptance API request. The code stores the object with `json.dumps` and converts it back with `json.loads` when reading the configuration; invalid JSON therefore causes parsing to fail, while original extra variables are preserved for channel-message and integration context.

Example

{"CustomerId":"CUSTOMER-10428"}
21. visit id

21. visit id

Parameter identifier: 21 Data type: text
Turkish name başvuru id
English name visit id

Description

The customer’s application or visit identifier in the source system. It is used in success analysis and reporting to associate the campaign journey with the related healthcare-service record.

Example

21-example
22. survey link

22. survey link

Parameter identifier: 22 Data type: text
Turkish name anket linki
English name survey link

Description

The survey address generated for the journey or received from an external system. The survey operation writes it here after creating the link; because a channel message can deliver this value to the customer, an empty link prevents survey redirection.

Example

22-example
23. survey system id

23. survey system id

Parameter identifier: 23 Data type: text
Turkish name anket sistemi id
English name survey system id

Description

The identifier of the survey record in the relevant survey system. Stored together with the survey link, it allows response and operation records to be associated with the correct survey.

Example

23-example
24. agenda time

24. agenda time

Parameter identifier: 24 Data type: list_parameter
Turkish name ajanda zamanı
English name agenda time

Description

A repeating list that stores one or more agenda times calculated for the journey. Each list row contains parameter 25, agenda date; therefore, if the selected campaign agenda rule produces multiple eligible delivery times, all of them are stored under the same journey.

Example

[{ ... }]
25. agenda date

25. agenda date

Parameter identifier: 25 Data type: datetime
Turkish name ajanda tarihi
English name agenda date

Description

A single scheduled date and time in the agenda-time list. Agenda-calculation code produces the eligible time according to campaign day and hour rules and adds it to the list; channel operations use this schedule so processing can occur only when the time is due.

Example

2026-10-25T09:30:00
26. create date

26. create date

Parameter identifier: 26 Data type: datetime
Turkish name oluşturma tarihi
English name create date

Description

The Coordinated Universal Time at which the journey record was first created. It is written with the current time during new acceptance and provides the technical record-creation time; although written in the same operation as parameter 7, start date, it is a separate audit field.

Example

2026-10-25T09:30:00
27. update date

27. update date

Parameter identifier: 27 Data type: datetime
Turkish name güncelleme tarihi
English name update date

Description

Defined to store the time at which journey data was last updated. The inspected configuration code reads the field but does not automatically write it during initial customer acceptance; integrations that update the record must send this field separately.

Example

2026-10-25T09:30:00
28. campaign client id

28. campaign client id

Parameter identifier: 28 Data type: text
Turkish name kampanya client id
English name campaign client id

Description

The client identifier of the campaign record that owns the journey. When a new journey is created, the campaign identifier in request scope is written here; channel settings and success analysis find the correct campaign configuration through this association.

Example

28-example
29. primary click status

29. primary click status

Parameter identifier: 29 Data type: select
Turkish name birincil tıklama durumu
English name primary click status

Description

A summary of whether at least one click related to the primary target was detected. `yes` summarizes the presence of events in the primary-click list; because detail identifier and date are stored in parameters 45–47, this field alone is not the event history.

Options

Value Turkish English Behavior
0 hayır no Interprets the field as “no”; business rules are evaluated according to this selected state.
1 evet yes Interprets the field as “yes”; business rules are evaluated according to this selected state.

Example

0 — no
30. primary success status

30. primary success status

Parameter identifier: 30 Data type: select
Turkish name birincil başarı durumu
English name primary success status

Description

Specifies whether the campaign’s primary success condition was met. Success analysis evaluates relevant integration results; if the condition occurs, it produces `yes` together with date and total-income fields, otherwise it remains `no`.

Options

Value Turkish English Behavior
0 hayır no Interprets the field as “no”; business rules are evaluated according to this selected state.
1 evet yes Interprets the field as “yes”; business rules are evaluated according to this selected state.

Example

0 — no
31. primary success date

31. primary success date

Parameter identifier: 31 Data type: datetime
Turkish name birincil başarı tarihi
English name primary success date

Description

The date on which primary success occurred or the date used by analysis. It is reported with the summary success status; when multiple details exist, detail dates remain in the list while this field carries the top-level date.

Example

2026-10-25T09:30:00
32. primary success total income

32. primary success total income

Parameter identifier: 32 Data type: float
Turkish name birincil başarı toplam gelir
English name primary success total income

Description

The numeric total of revenues associated with primary success. Revenue values in success details may be totaled in the result context for reporting; when there is no success, the field may remain empty or zero, and currency is not defined separately in this layer.

Example

1250.50
33. secondary click status

33. secondary click status

Parameter identifier: 33 Data type: select
Turkish name ikincil tıklama durumu
English name secondary click status

Description

A summary of whether at least one click related to the secondary target was detected. Detailed events are stored in the repeating list at parameters 48–50; this field provides a quick yes/no distinction for reports and filters.

Options

Value Turkish English Behavior
0 hayır no Interprets the field as “no”; business rules are evaluated according to this selected state.
1 evet yes Interprets the field as “yes”; business rules are evaluated according to this selected state.

Example

0 — no
34. secondary success status

34. secondary success status

Parameter identifier: 34 Data type: select
Turkish name ikincil başarı durumu
English name secondary success status

Description

Specifies whether the campaign’s secondary success condition was met. Success analysis evaluates secondary-rule results separately; therefore, it can be yes or no independently of primary success.

Options

Value Turkish English Behavior
0 hayır no Interprets the field as “no”; business rules are evaluated according to this selected state.
1 evet yes Interprets the field as “yes”; business rules are evaluated according to this selected state.

Example

0 — no
35. secondary success date

35. secondary success date

Parameter identifier: 35 Data type: datetime
Turkish name ikincil başarı tarihi
English name secondary success date

Description

The date on which secondary success occurred or the date used by analysis. When there are multiple secondary-success details, list dates are preserved while this field provides the top-level reporting date.

Example

2026-10-25T09:30:00
36. secondary success total income

36. secondary success total income

Parameter identifier: 36 Data type: float
Turkish name ikincil başarı toplam gelir
English name secondary success total income

Description

The numeric total of revenues associated with secondary success. It is reported together with secondary-success details; when no revenue is found it may be empty or zero, and this field does not store currency information.

Example

1250.50
37. primary success detail

37. primary success detail

Parameter identifier: 37 Data type: list_parameter
Turkish name birincil başarı detayı
English name primary success detail

Description

A repeating list that stores all matches found by primary-success analysis. Because each row contains an identifier, date, and revenue, multiple success records in one journey are preserved without loss; top-level parameters 30–32 provide their summary.

Example

[{ ... }]
38. primary success detail id

38. primary success detail id

Parameter identifier: 38 Data type: text
Turkish name birincil başarı detayı id
English name primary success detail id

Description

The source or integration-record identifier of a primary-success detail. It distinguishes the list row to prevent the same success event from being added again and to keep the report traceable to its source record.

Example

38-example
39. primary success detail date

39. primary success detail date

Parameter identifier: 39 Data type: datetime
Turkish name birincil başarı detayı tarihi
English name primary success detail date

Description

The event date in a primary-success detail. When multiple successes exist, each event time is stored separately, preserving chronological detail beyond the single top-level date.

Example

2026-10-25T09:30:00
40. primary success detail total income

40. primary success detail total income

Parameter identifier: 40 Data type: float
Turkish name birincil başarı detayı toplam gelir
English name primary success detail total income

Description

The revenue value of one event in a primary-success detail. Because top-level total revenue is associated with these details, the contribution of each source record can be examined separately.

Example

1250.50
41. secondary success detail

41. secondary success detail

Parameter identifier: 41 Data type: list_parameter
Turkish name ikincil başarı detayı
English name secondary success detail

Description

A repeating list that stores all matches found by secondary-success analysis. Each row contains identifier, date, and revenue parameters 42–44; top-level secondary-success fields provide a summary while the list preserves source events.

Example

[{ ... }]
42. secondary success detail id

42. secondary success detail id

Parameter identifier: 42 Data type: text
Turkish name ikincil başarı detayı id
English name secondary success detail id

Description

The source or integration-record identifier of a secondary-success detail. It is used to trace the success event uniquely within the list and distinguish duplicate results.

Example

42-example
43. secondary success detail date

43. secondary success detail date

Parameter identifier: 43 Data type: datetime
Turkish name ikincil başarı detayı tarihi
English name secondary success detail date

Description

The event date in a secondary-success detail. Because the time of each match is stored separately, the chronology of secondary successes can be reconstructed in reporting.

Example

2026-10-25T09:30:00
44. secondary success detail total income

44. secondary success detail total income

Parameter identifier: 44 Data type: float
Turkish name ikincil başarı detayı toplam gelir
English name secondary success detail total income

Description

The revenue value of one event in a secondary-success detail. It allows inspection of which source events make up the total-revenue summary in parameter 36.

Example

1250.50
45. primary click

45. primary click

Parameter identifier: 45 Data type: list_parameter
Turkish name birincil tıklama
English name primary click

Description

A repeating list that stores click events for the primary target. Each row contains a click identifier and date; parameter 29 only summarizes whether an event exists.

Example

[{ ... }]
46. primary click id

46. primary click id

Parameter identifier: 46 Data type: text
Turkish name birincil tıklama id
English name primary click id

Description

The source identifier of a primary-click event. It makes the same event traceable and distinguishes repeated clicks from one another.

Example

46-example
47. primary click date

47. primary click date

Parameter identifier: 47 Data type: datetime
Turkish name birincil tıklama tarihi
English name primary click date

Description

The date on which a primary-click event occurred. When there are multiple clicks, each time is preserved separately in its list row.

Example

2026-10-25T09:30:00
48. secondary click

48. secondary click

Parameter identifier: 48 Data type: list_parameter
Turkish name ikincil tıklama
English name secondary click

Description

A repeating list that stores click events for the secondary target. Each row contains identifier and date parameters 49 and 50; parameter 33 is the yes/no summary of the list.

Example

[{ ... }]
49. secondary click id

49. secondary click id

Parameter identifier: 49 Data type: text
Turkish name ikincil tıklama id
English name secondary click id

Description

The source identifier of a secondary-click event. It allows the event to be traced to its source and multiple clicks to be recorded separately.

Example

49-example
50. secondary click date

50. secondary click date

Parameter identifier: 50 Data type: datetime
Turkish name ikincil tıklama tarihi
English name secondary click date

Description

The date on which a secondary-click event occurred. It preserves the chronological order of interactions with the secondary target.

Example

2026-10-25T09:30:00
51. doctor id

51. doctor id

Parameter identifier: 51 Data type: text
Turkish name doktor id
English name doctor id

Description

The source-system identifier of the doctor associated with the visit or success record. It is received from the `DoctorId` field in customer-acceptance input and used for doctor-based reporting and matching.

Example

51-example
52. doctor name

52. doctor name

Parameter identifier: 52 Data type: text
Turkish name doktor adı
English name doctor name

Description

The display name of the doctor associated with the visit or success record. It comes from source `DoctorName`; it complements the identifier with human-readable context but does not replace the doctor identifier for matching.

Example

52-example
53. visit type

53. visit type

Parameter identifier: 53 Data type: select
Turkish name başvuru tipi
English name visit type

Description

Classifies the operation type of the source visit. Customer-acceptance code stores incoming `VisitType` as the option value; success analysis and reports can distinguish emergency examination, surgery, control, and other types with this classification.

Options

Value Turkish English Behavior
0 acil muayene emergency examination Stores the record with the “emergency examination” classification and uses this value in matching and reporting.
1 ameliyat operation Stores the record with the “operation” classification and uses this value in matching and reporting.
2 check-up check up Stores the record with the “check up” classification and uses this value in matching and reporting.
3 çocuk yoğun bakım pediatric intensive care Stores the record with the “pediatric intensive care” classification and uses this value in matching and reporting.
4 test test Stores the record with the “test” classification and uses this value in matching and reporting.
5 diğer other Stores the record with the “other” classification and uses this value in matching and reporting.
6 donör donor Stores the record with the “donor” classification and uses this value in matching and reporting.
7 endoskopi kolonoskopi endoscopy colonoscopy Stores the record with the “endoscopy colonoscopy” classification and uses this value in matching and reporting.
8 enjeksiyon injection Stores the record with the “injection” classification and uses this value in matching and reporting.
9 evde bakım home care Stores the record with the “home care” classification and uses this value in matching and reporting.
10 fizik tedavi seans physical therapy session Stores the record with the “physical therapy session” classification and uses this value in matching and reporting.
11 genel muayane general examination Stores the record with the “general examination” classification and uses this value in matching and reporting.
12 genel yoğun bakım general intensive care Stores the record with the “general intensive care” classification and uses this value in matching and reporting.
13 girişimsel işlemler interventional procedures Stores the record with the “interventional procedures” classification and uses this value in matching and reporting.
14 hekim ön görüşme physician preliminary interview Stores the record with the “physician preliminary interview” classification and uses this value in matching and reporting.
15 ikinci görüş second opinion Stores the record with the “second opinion” classification and uses this value in matching and reporting.
16 reçete prescriptions Stores the record with the “prescriptions” classification and uses this value in matching and reporting.
17 işyeri hekimliği workplace medicine Stores the record with the “workplace medicine” classification and uses this value in matching and reporting.
18 tüp bebek test tube baby Stores the record with the “test tube baby” classification and uses this value in matching and reporting.
19 kemik iliği bone marrow Stores the record with the “bone marrow” classification and uses this value in matching and reporting.
20 kemoterapi chemotherapy Stores the record with the “chemotherapy” classification and uses this value in matching and reporting.
21 kök hücre donörü stem cell donor Stores the record with the “stem cell donor” classification and uses this value in matching and reporting.
22 konsey council Stores the record with the “council” classification and uses this value in matching and reporting.
23 kontrol muyenesi control inspection Stores the record with the “control inspection” classification and uses this value in matching and reporting.
24 laboratuar laboratory Stores the record with the “laboratory” classification and uses this value in matching and reporting.
25 medikal tedavi medical treatment Stores the record with the “medical treatment” classification and uses this value in matching and reporting.
26 müdahele intervention Stores the record with the “intervention” classification and uses this value in matching and reporting.
27 onkoloji oncology Stores the record with the “oncology” classification and uses this value in matching and reporting.
28 online muayene Online examination Stores the record with the “Online examination” classification and uses this value in matching and reporting.
29 organ nakli transplantation Stores the record with the “transplantation” classification and uses this value in matching and reporting.
30 ortodonti orthodontics Stores the record with the “orthodontics” classification and uses this value in matching and reporting.
31 pansuman dressing Stores the record with the “dressing” classification and uses this value in matching and reporting.
32 yatış öncesi ayaktan before going to bed Stores the record with the “before going to bed” classification and uses this value in matching and reporting.
33 radyoloji radiological Stores the record with the “radiological” classification and uses this value in matching and reporting.
34 radyoterapi radiotherapy Stores the record with the “radiotherapy” classification and uses this value in matching and reporting.
35 reçete prescriptions Stores the record with the “prescriptions” classification and uses this value in matching and reporting.
36 saç ekimi hair transplantation Stores the record with the “hair transplantation” classification and uses this value in matching and reporting.
37 tarama scanning Stores the record with the “scanning” classification and uses this value in matching and reporting.
38 tetkik kaydı examination record Stores the record with the “examination record” classification and uses this value in matching and reporting.
39 yenidoğan muayenesi newborn examination Stores the record with the “newborn examination” classification and uses this value in matching and reporting.
40 yenidoğan yoğun bakım neonatal intensive care Stores the record with the “neonatal intensive care” classification and uses this value in matching and reporting.
41 yoğun bakım intensive care Stores the record with the “intensive care” classification and uses this value in matching and reporting.

Example

0 — emergency examination
54. hospitalization type

54. hospitalization type

Parameter identifier: 54 Data type: select
Turkish name yatış tipi
English name hospitalization type

Description

Specifies whether the hospitalization-related service is classified as surgery, medical treatment, or intensive care. Source `HospitalizationType` is carried into the journey and is meaningful only when a hospitalization context exists.

Options

Value Turkish English Behavior
0 ameliyat surgery Stores the record with the “surgery” classification and uses this value in matching and reporting.
1 medikal tedavi medical treatment Stores the record with the “medical treatment” classification and uses this value in matching and reporting.
2 yogun bakim intensive care Stores the record with the “intensive care” classification and uses this value in matching and reporting.

Example

0 — surgery
55. arrive type

55. arrive type

Parameter identifier: 55 Data type: select
Turkish name geliş tipi
English name arrive type

Description

Specifies whether the visit occurs as outpatient, inpatient, or day case. Because source `ArriveType` is stored as an option, reports and success rules can distinguish the service-delivery mode.

Options

Value Turkish English Behavior
0 ayakta standing Stores the record with the “standing” classification and uses this value in matching and reporting.
1 yatarak lying Stores the record with the “lying” classification and uses this value in matching and reporting.
2 günübirlik daily Stores the record with the “daily” classification and uses this value in matching and reporting.

Example

0 — standing
56. db map id

56. db map id

Parameter identifier: 56 Data type: text
Turkish name db harita id
English name db map id

Description

The client identifier of the database map that produced the customer data. Source `DbMapId` preserves data lineage and makes it possible to trace which mapping supplied the success or contact-detail integration.

Example

56-example
57. db server id

57. db server id

Parameter identifier: 57 Data type: text
Turkish name db sunucu id
English name db server id

Description

The client identifier of the database server that produced the customer data. Together with `DbMapId` it defines the source connection; using a map that belongs to another server can cause queries against the wrong source.

Example

57-example
58. legal data processing permission

58. legal data processing permission

Parameter identifier: 58 Data type: select
Turkish name legal veri işleme izni
English name legal data processing permission

Description

The permission status for processing the customer’s personal data. When the source has no value, the configuration defaults to `missing`; rejected or awaiting-approval values must not be treated as approved in channel and integration decisions that require permission.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 onaylandı approved Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 kayıt yok missing Interprets the field as “missing”; business rules are evaluated according to this selected state.

Example

0 — rejected
59. legal communication permission

59. legal communication permission

Parameter identifier: 59 Data type: select
Turkish name legal iletişim izni
English name legal communication permission

Description

The permission status for general communication with the customer. It may be used together with channel-specific permissions when evaluating channel eligibility; values other than `approved` do not represent explicit approval.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 onaylandı approved Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 kayıt yok missing Interprets the field as “missing”; business rules are evaluated according to this selected state.

Example

0 — rejected
60. sms permission

60. sms permission

Parameter identifier: 60 Data type: select
Turkish name sms izni
English name sms permission

Description

The permission to send SMS messages to the customer. If the SMS channel is to be selected, an approved value permits communication; rejected, awaiting approval, or missing values must not be interpreted as approved SMS permission.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 onaylandı approved Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 kayıt yok missing Interprets the field as “missing”; business rules are evaluated according to this selected state.

Example

0 — rejected
61. email permission

61. email permission

Parameter identifier: 61 Data type: select
Turkish name mail izni
English name email permission

Description

The permission to send email to the customer. It is used when evaluating eligibility of the email channel; only `approved` expresses explicit permission, and other states are not approval for delivery.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 onaylandı approved Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 kayıt yok missing Interprets the field as “missing”; business rules are evaluated according to this selected state.

Example

0 — rejected
62. phone call permission

62. phone call permission

Parameter identifier: 62 Data type: select
Turkish name telefon ile arama izni
English name phone call permission

Description

The permission to call the customer by phone. It carries the approval state for the phone-call channel; rejected, pending, or missing permission must not produce the same behavior as approved call permission.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 onaylandı approved Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 kayıt yok missing Interprets the field as “missing”; business rules are evaluated according to this selected state.

Example

0 — rejected
63. nation code

63. nation code

Parameter identifier: 63 Data type: select
Turkish name uyruk kodu
English name nation code

Description

The option that represents the customer’s country by code. Source `NationCode` is normally written here and is machine-readable for country-based matching. However, in the two inspected customer-acceptance paths, `NationName` is also mistakenly written to parameter 63 instead of 64, so the name can overwrite the code; until this is fixed, verify that the value in this field is actually a country code.

Options

Value Turkish English Behavior
0 US US Stores the record with the “US” classification and uses this value in matching and reporting.
1 AF AF Stores the record with the “AF” classification and uses this value in matching and reporting.
2 DE DE Stores the record with the “DE” classification and uses this value in matching and reporting.
3 AS AS Stores the record with the “AS” classification and uses this value in matching and reporting.
4 AD AD Stores the record with the “AD” classification and uses this value in matching and reporting.
5 AO AO Stores the record with the “AO” classification and uses this value in matching and reporting.
6 AI AI Stores the record with the “AI” classification and uses this value in matching and reporting.
7 AR AR Stores the record with the “AR” classification and uses this value in matching and reporting.
8 AL AL Stores the record with the “AL” classification and uses this value in matching and reporting.
9 AW AW Stores the record with the “AW” classification and uses this value in matching and reporting.
10 AU AU Stores the record with the “AU” classification and uses this value in matching and reporting.
11 AT AT Stores the record with the “AT” classification and uses this value in matching and reporting.
12 AZ AZ Stores the record with the “AZ” classification and uses this value in matching and reporting.
13 BS BS Stores the record with the “BS” classification and uses this value in matching and reporting.
14 BH BH Stores the record with the “BH” classification and uses this value in matching and reporting.
15 BD BD Stores the record with the “BD” classification and uses this value in matching and reporting.
16 BB BB Stores the record with the “BB” classification and uses this value in matching and reporting.
17 AG AG Stores the record with the “AG” classification and uses this value in matching and reporting.
18 BY BY Stores the record with the “BY” classification and uses this value in matching and reporting.
19 BE BE Stores the record with the “BE” classification and uses this value in matching and reporting.
20 BZ BZ Stores the record with the “BZ” classification and uses this value in matching and reporting.
21 BJ BJ Stores the record with the “BJ” classification and uses this value in matching and reporting.
22 BM BM Stores the record with the “BM” classification and uses this value in matching and reporting.
23 AE AE Stores the record with the “AE” classification and uses this value in matching and reporting.
24 BO BO Stores the record with the “BO” classification and uses this value in matching and reporting.
25 BA BA Stores the record with the “BA” classification and uses this value in matching and reporting.
26 BW BW Stores the record with the “BW” classification and uses this value in matching and reporting.
27 BR BR Stores the record with the “BR” classification and uses this value in matching and reporting.
28 VG VG Stores the record with the “VG” classification and uses this value in matching and reporting.
29 BN BN Stores the record with the “BN” classification and uses this value in matching and reporting.
30 BG BG Stores the record with the “BG” classification and uses this value in matching and reporting.
31 BF BF Stores the record with the “BF” classification and uses this value in matching and reporting.
32 BI BI Stores the record with the “BI” classification and uses this value in matching and reporting.
33 BT BT Stores the record with the “BT” classification and uses this value in matching and reporting.
34 CV CV Stores the record with the “CV” classification and uses this value in matching and reporting.
35 KY KY Stores the record with the “KY” classification and uses this value in matching and reporting.
36 GI GI Stores the record with the “GI” classification and uses this value in matching and reporting.
37 CK CK Stores the record with the “CK” classification and uses this value in matching and reporting.
38 TD TD Stores the record with the “TD” classification and uses this value in matching and reporting.
39 CZ CZ Stores the record with the “CZ” classification and uses this value in matching and reporting.
40 CN CN Stores the record with the “CN” classification and uses this value in matching and reporting.
41 DK DK Stores the record with the “DK” classification and uses this value in matching and reporting.
42 DJ DJ Stores the record with the “DJ” classification and uses this value in matching and reporting.
43 TL TL Stores the record with the “TL” classification and uses this value in matching and reporting.
44 DO DO Stores the record with the “DO” classification and uses this value in matching and reporting.
45 DM DM Stores the record with the “DM” classification and uses this value in matching and reporting.
46 EC EC Stores the record with the “EC” classification and uses this value in matching and reporting.
47 GQ GQ Stores the record with the “GQ” classification and uses this value in matching and reporting.
48 SV SV Stores the record with the “SV” classification and uses this value in matching and reporting.
49 ID ID Stores the record with the “ID” classification and uses this value in matching and reporting.
50 ER ER Stores the record with the “ER” classification and uses this value in matching and reporting.
51 AM AM Stores the record with the “AM” classification and uses this value in matching and reporting.
52 EE EE Stores the record with the “EE” classification and uses this value in matching and reporting.
53 ET ET Stores the record with the “ET” classification and uses this value in matching and reporting.
54 FO FO Stores the record with the “FO” classification and uses this value in matching and reporting.
55 MA MA Stores the record with the “MA” classification and uses this value in matching and reporting.
56 FJ FJ Stores the record with the “FJ” classification and uses this value in matching and reporting.
57 CI CI Stores the record with the “CI” classification and uses this value in matching and reporting.
58 PH PH Stores the record with the “PH” classification and uses this value in matching and reporting.
59 PS PS Stores the record with the “PS” classification and uses this value in matching and reporting.
60 FI FI Stores the record with the “FI” classification and uses this value in matching and reporting.
61 FR FR Stores the record with the “FR” classification and uses this value in matching and reporting.
62 GF GF Stores the record with the “GF” classification and uses this value in matching and reporting.
63 PF PF Stores the record with the “PF” classification and uses this value in matching and reporting.
64 GA GA Stores the record with the “GA” classification and uses this value in matching and reporting.
65 GM GM Stores the record with the “GM” classification and uses this value in matching and reporting.
66 GH GH Stores the record with the “GH” classification and uses this value in matching and reporting.
67 GN GN Stores the record with the “GN” classification and uses this value in matching and reporting.
68 GD GD Stores the record with the “GD” classification and uses this value in matching and reporting.
69 GL GL Stores the record with the “GL” classification and uses this value in matching and reporting.
70 GP GP Stores the record with the “GP” classification and uses this value in matching and reporting.
71 GU GU Stores the record with the “GU” classification and uses this value in matching and reporting.
72 GT GT Stores the record with the “GT” classification and uses this value in matching and reporting.
73 GY GY Stores the record with the “GY” classification and uses this value in matching and reporting.
74 ZA ZA Stores the record with the “ZA” classification and uses this value in matching and reporting.
75 KR KR Stores the record with the “KR” classification and uses this value in matching and reporting.
76 GE GE Stores the record with the “GE” classification and uses this value in matching and reporting.
77 HT HT Stores the record with the “HT” classification and uses this value in matching and reporting.
78 HR HR Stores the record with the “HR” classification and uses this value in matching and reporting.
79 IN IN Stores the record with the “IN” classification and uses this value in matching and reporting.
80 NLD NLD Stores the record with the “NLD” classification and uses this value in matching and reporting.
81 AN AN Stores the record with the “AN” classification and uses this value in matching and reporting.
82 HN HN Stores the record with the “HN” classification and uses this value in matching and reporting.
83 HK HK Stores the record with the “HK” classification and uses this value in matching and reporting.
84 IQ IQ Stores the record with the “IQ” classification and uses this value in matching and reporting.
85 IE IE Stores the record with the “IE” classification and uses this value in matching and reporting.
86 ES ES Stores the record with the “ES” classification and uses this value in matching and reporting.
87 IL IL Stores the record with the “IL” classification and uses this value in matching and reporting.
88 SE SE Stores the record with the “SE” classification and uses this value in matching and reporting.
89 CH CH Stores the record with the “CH” classification and uses this value in matching and reporting.
90 IT IT Stores the record with the “IT” classification and uses this value in matching and reporting.
91 IS IS Stores the record with the “IS” classification and uses this value in matching and reporting.
92 JM JM Stores the record with the “JM” classification and uses this value in matching and reporting.
93 JP JP Stores the record with the “JP” classification and uses this value in matching and reporting.
94 KH KH Stores the record with the “KH” classification and uses this value in matching and reporting.
95 CM CM Stores the record with the “CM” classification and uses this value in matching and reporting.
96 CA CA Stores the record with the “CA” classification and uses this value in matching and reporting.
97 QA QA Stores the record with the “QA” classification and uses this value in matching and reporting.
98 KZ KZ Stores the record with the “KZ” classification and uses this value in matching and reporting.
99 KE KE Stores the record with the “KE” classification and uses this value in matching and reporting.
100 CY CY Stores the record with the “CY” classification and uses this value in matching and reporting.
101 KG KG Stores the record with the “KG” classification and uses this value in matching and reporting.
102 CO CO Stores the record with the “CO” classification and uses this value in matching and reporting.
103 CD CD Stores the record with the “CD” classification and uses this value in matching and reporting.
104 CG CG Stores the record with the “CG” classification and uses this value in matching and reporting.
105 CR CR Stores the record with the “CR” classification and uses this value in matching and reporting.
106 KW KW Stores the record with the “KW” classification and uses this value in matching and reporting.
107 LA LA Stores the record with the “LA” classification and uses this value in matching and reporting.
108 LV LV Stores the record with the “LV” classification and uses this value in matching and reporting.
109 LS LS Stores the record with the “LS” classification and uses this value in matching and reporting.
110 LR LR Stores the record with the “LR” classification and uses this value in matching and reporting.
111 LY LY Stores the record with the “LY” classification and uses this value in matching and reporting.
112 LI LI Stores the record with the “LI” classification and uses this value in matching and reporting.
113 LT LT Stores the record with the “LT” classification and uses this value in matching and reporting.
114 LB LB Stores the record with the “LB” classification and uses this value in matching and reporting.
115 LU LU Stores the record with the “LU” classification and uses this value in matching and reporting.
116 HU HU Stores the record with the “HU” classification and uses this value in matching and reporting.
117 MG MG Stores the record with the “MG” classification and uses this value in matching and reporting.
118 MO MO Stores the record with the “MO” classification and uses this value in matching and reporting.
119 MK MK Stores the record with the “MK” classification and uses this value in matching and reporting.
120 MW MW Stores the record with the “MW” classification and uses this value in matching and reporting.
121 MV MV Stores the record with the “MV” classification and uses this value in matching and reporting.
122 MY MY Stores the record with the “MY” classification and uses this value in matching and reporting.
123 ML ML Stores the record with the “ML” classification and uses this value in matching and reporting.
124 MT MT Stores the record with the “MT” classification and uses this value in matching and reporting.
125 MU MU Stores the record with the “MU” classification and uses this value in matching and reporting.
126 MH MH Stores the record with the “MH” classification and uses this value in matching and reporting.
127 MQ MQ Stores the record with the “MQ” classification and uses this value in matching and reporting.
128 MX MX Stores the record with the “MX” classification and uses this value in matching and reporting.
129 FM FM Stores the record with the “FM” classification and uses this value in matching and reporting.
130 EG EG Stores the record with the “EG” classification and uses this value in matching and reporting.
131 MN MN Stores the record with the “MN” classification and uses this value in matching and reporting.
132 MD MD Stores the record with the “MD” classification and uses this value in matching and reporting.
133 MC MC Stores the record with the “MC” classification and uses this value in matching and reporting.
134 MS MS Stores the record with the “MS” classification and uses this value in matching and reporting.
135 MR MR Stores the record with the “MR” classification and uses this value in matching and reporting.
136 MZ MZ Stores the record with the “MZ” classification and uses this value in matching and reporting.
137 Stores the record with the “” classification and uses this value in matching and reporting.
138 NP NP Stores the record with the “NP” classification and uses this value in matching and reporting.
139 NE NE Stores the record with the “NE” classification and uses this value in matching and reporting.
140 NG NG Stores the record with the “NG” classification and uses this value in matching and reporting.
141 NI NI Stores the record with the “NI” classification and uses this value in matching and reporting.
142 NO NO Stores the record with the “NO” classification and uses this value in matching and reporting.
143 UZ UZ Stores the record with the “UZ” classification and uses this value in matching and reporting.
144 PK PK Stores the record with the “PK” classification and uses this value in matching and reporting.
145 PW PW Stores the record with the “PW” classification and uses this value in matching and reporting.
146 PA PA Stores the record with the “PA” classification and uses this value in matching and reporting.
147 PG PG Stores the record with the “PG” classification and uses this value in matching and reporting.
148 PY PY Stores the record with the “PY” classification and uses this value in matching and reporting.
149 PE PE Stores the record with the “PE” classification and uses this value in matching and reporting.
150 PL PL Stores the record with the “PL” classification and uses this value in matching and reporting.
151 PT PT Stores the record with the “PT” classification and uses this value in matching and reporting.
152 PR PR Stores the record with the “PR” classification and uses this value in matching and reporting.
153 RE RE Stores the record with the “RE” classification and uses this value in matching and reporting.
154 RO RO Stores the record with the “RO” classification and uses this value in matching and reporting.
155 RW RW Stores the record with the “RW” classification and uses this value in matching and reporting.
156 RU RU Stores the record with the “RU” classification and uses this value in matching and reporting.
157 MP MP Stores the record with the “MP” classification and uses this value in matching and reporting.
158 SN SN Stores the record with the “SN” classification and uses this value in matching and reporting.
159 SC SC Stores the record with the “SC” classification and uses this value in matching and reporting.
160 CS CS Stores the record with the “CS” classification and uses this value in matching and reporting.
161 SG SG Stores the record with the “SG” classification and uses this value in matching and reporting.
162 SK SK Stores the record with the “SK” classification and uses this value in matching and reporting.
163 SI SI Stores the record with the “SI” classification and uses this value in matching and reporting.
164 LK LK Stores the record with the “LK” classification and uses this value in matching and reporting.
165 KN KN Stores the record with the “KN” classification and uses this value in matching and reporting.
166 LC LC Stores the record with the “LC” classification and uses this value in matching and reporting.
167 VC VC Stores the record with the “VC” classification and uses this value in matching and reporting.
168 SR SR Stores the record with the “SR” classification and uses this value in matching and reporting.
169 SY SY Stores the record with the “SY” classification and uses this value in matching and reporting.
170 SA SA Stores the record with the “SA” classification and uses this value in matching and reporting.
171 SZ SZ Stores the record with the “SZ” classification and uses this value in matching and reporting.
172 CL CL Stores the record with the “CL” classification and uses this value in matching and reporting.
173 TZ TZ Stores the record with the “TZ” classification and uses this value in matching and reporting.
174 TH TH Stores the record with the “TH” classification and uses this value in matching and reporting.
175 TW TW Stores the record with the “TW” classification and uses this value in matching and reporting.
176 TG TG Stores the record with the “TG” classification and uses this value in matching and reporting.
177 TO TO Stores the record with the “TO” classification and uses this value in matching and reporting.
178 TT TT Stores the record with the “TT” classification and uses this value in matching and reporting.
179 TN TN Stores the record with the “TN” classification and uses this value in matching and reporting.
180 TC TC Stores the record with the “TC” classification and uses this value in matching and reporting.
181 TR TR Stores the record with the “TR” classification and uses this value in matching and reporting.
182 TM TM Stores the record with the “TM” classification and uses this value in matching and reporting.
183 UG UG Stores the record with the “UG” classification and uses this value in matching and reporting.
184 UA UA Stores the record with the “UA” classification and uses this value in matching and reporting.
185 OM OM Stores the record with the “OM” classification and uses this value in matching and reporting.
186 UY UY Stores the record with the “UY” classification and uses this value in matching and reporting.
187 JO JO Stores the record with the “JO” classification and uses this value in matching and reporting.
188 VU VU Stores the record with the “VU” classification and uses this value in matching and reporting.
189 VE VE Stores the record with the “VE” classification and uses this value in matching and reporting.
190 VN VN Stores the record with the “VN” classification and uses this value in matching and reporting.
191 VI VI Stores the record with the “VI” classification and uses this value in matching and reporting.
192 WF WF Stores the record with the “WF” classification and uses this value in matching and reporting.
193 YE YE Stores the record with the “YE” classification and uses this value in matching and reporting.
194 NC NC Stores the record with the “NC” classification and uses this value in matching and reporting.
195 NZ NZ Stores the record with the “NZ” classification and uses this value in matching and reporting.
196 GR GR Stores the record with the “GR” classification and uses this value in matching and reporting.
197 ZM ZM Stores the record with the “ZM” classification and uses this value in matching and reporting.
198 ZW ZW Stores the record with the “ZW” classification and uses this value in matching and reporting.
199 IR IR Stores the record with the “IR” classification and uses this value in matching and reporting.
200 XK XK Stores the record with the “XK” classification and uses this value in matching and reporting.
201 UK UK Stores the record with the “UK” classification and uses this value in matching and reporting.
202 TJ TJ Stores the record with the “TJ” classification and uses this value in matching and reporting.
203 SO SO Stores the record with the “SO” classification and uses this value in matching and reporting.
204 DZ DZ Stores the record with the “DZ” classification and uses this value in matching and reporting.
205 AX AX Stores the record with the “AX” classification and uses this value in matching and reporting.
206 AQ AQ Stores the record with the “AQ” classification and uses this value in matching and reporting.
207 EH EH Stores the record with the “EH” classification and uses this value in matching and reporting.
208 UM UM Stores the record with the “UM” classification and uses this value in matching and reporting.
209 BV BV Stores the record with the “BV” classification and uses this value in matching and reporting.
210 CX CX Stores the record with the “CX” classification and uses this value in matching and reporting.
211 CC CC Stores the record with the “CC” classification and uses this value in matching and reporting.
212 TF TF Stores the record with the “TF” classification and uses this value in matching and reporting.
213 GW GW Stores the record with the “GW” classification and uses this value in matching and reporting.
214 GG GG Stores the record with the “GG” classification and uses this value in matching and reporting.
215 GS GS Stores the record with the “GS” classification and uses this value in matching and reporting.
216 HM HM Stores the record with the “HM” classification and uses this value in matching and reporting.
217 VA VA Stores the record with the “VA” classification and uses this value in matching and reporting.
218 IM IM Stores the record with the “IM” classification and uses this value in matching and reporting.
219 IO IO Stores the record with the “IO” classification and uses this value in matching and reporting.
220 JE JE Stores the record with the “JE” classification and uses this value in matching and reporting.
221 KI KI Stores the record with the “KI” classification and uses this value in matching and reporting.
222 KM KM Stores the record with the “KM” classification and uses this value in matching and reporting.
223 KP KP Stores the record with the “KP” classification and uses this value in matching and reporting.
224 YT YT Stores the record with the “YT” classification and uses this value in matching and reporting.
225 MM MM Stores the record with the “MM” classification and uses this value in matching and reporting.
226 NR NR Stores the record with the “NR” classification and uses this value in matching and reporting.
227 NU NU Stores the record with the “NU” classification and uses this value in matching and reporting.
228 NF NF Stores the record with the “NF” classification and uses this value in matching and reporting.
229 CF CF Stores the record with the “CF” classification and uses this value in matching and reporting.
230 PN PN Stores the record with the “PN” classification and uses this value in matching and reporting.
231 BL BL Stores the record with the “BL” classification and uses this value in matching and reporting.
232 MF MF Stores the record with the “MF” classification and uses this value in matching and reporting.
233 PM PM Stores the record with the “PM” classification and uses this value in matching and reporting.
234 WS WS Stores the record with the “WS” classification and uses this value in matching and reporting.
235 SM SM Stores the record with the “SM” classification and uses this value in matching and reporting.
236 SH SH Stores the record with the “SH” classification and uses this value in matching and reporting.
237 ST ST Stores the record with the “ST” classification and uses this value in matching and reporting.
238 RS RS Stores the record with the “RS” classification and uses this value in matching and reporting.
239 SL SL Stores the record with the “SL” classification and uses this value in matching and reporting.
240 SB SB Stores the record with the “SB” classification and uses this value in matching and reporting.
241 SJ SJ Stores the record with the “SJ” classification and uses this value in matching and reporting.
242 TK TK Stores the record with the “TK” classification and uses this value in matching and reporting.
243 TV TV Stores the record with the “TV” classification and uses this value in matching and reporting.
244 KK KK Stores the record with the “KK” classification and uses this value in matching and reporting.
245 ME ME Stores the record with the “ME” classification and uses this value in matching and reporting.
246 CU CU Stores the record with the “CU” classification and uses this value in matching and reporting.

Example

0 — US
64. nation name

64. nation name

Parameter identifier: 64 Data type: select
Turkish name uyruk adı
English name nation name

Description

The option defined to store the display name of the customer’s country. Although the WDM schema contains parameter 64 and country-name options, the inspected customer-acceptance code mistakenly writes `NationName` to parameter 63; therefore, this field may not be populated automatically in the current flow and may remain empty unless written manually or by another integration.

Options

Value Turkish English Behavior
0 batı sahra western sahara Stores the record with the “western sahara” classification and uses this value in matching and reporting.
1 birleşik devletler'e ait uzak küçük adalar united states outlying minor islands Stores the record with the “united states outlying minor islands” classification and uses this value in matching and reporting.
2 aland adaları aland islands Stores the record with the “aland islands” classification and uses this value in matching and reporting.
3 antarktika antarctica Stores the record with the “antarctica” classification and uses this value in matching and reporting.
4 somali somalia Stores the record with the “somalia” classification and uses this value in matching and reporting.
5 cezayir algeria Stores the record with the “algeria” classification and uses this value in matching and reporting.
6 tacikistan tajikistan Stores the record with the “tajikistan” classification and uses this value in matching and reporting.
7 sudan sudan Stores the record with the “sudan” classification and uses this value in matching and reporting.
8 seyşel adaları seychelles Stores the record with the “seychelles” classification and uses this value in matching and reporting.
9 bouvet adası bouvet island Stores the record with the “bouvet island” classification and uses this value in matching and reporting.
10 christmas adası christmas island Stores the record with the “christmas island” classification and uses this value in matching and reporting.
11 meksika mexico Stores the record with the “mexico” classification and uses this value in matching and reporting.
12 martinik martinique Stores the record with the “martinique” classification and uses this value in matching and reporting.
13 marşal adaları marshall islands Stores the record with the “marshall islands” classification and uses this value in matching and reporting.
14 mauritius adası mauritius island Stores the record with the “mauritius island” classification and uses this value in matching and reporting.
15 moldovya moldova Stores the record with the “moldova” classification and uses this value in matching and reporting.
16 moğolistan mongolia Stores the record with the “mongolia” classification and uses this value in matching and reporting.
17 mısır egypt Stores the record with the “egypt” classification and uses this value in matching and reporting.
18 mikronezya micronesia Stores the record with the “micronesia” classification and uses this value in matching and reporting.
19 montserrat montserrat Stores the record with the “montserrat” classification and uses this value in matching and reporting.
20 monako monaco Stores the record with the “monaco” classification and uses this value in matching and reporting.
21 sırbistan karadağ serbia montenegro Stores the record with the “serbia montenegro” classification and uses this value in matching and reporting.
22 birl. arap emirlikleri united united arab emirates Stores the record with the “united united arab emirates” classification and uses this value in matching and reporting.
23 bolivya bolivia Stores the record with the “bolivia” classification and uses this value in matching and reporting.
24 bosna hersek bosnia and herzegovina Stores the record with the “bosnia and herzegovina” classification and uses this value in matching and reporting.
25 botsvana botswana Stores the record with the “botswana” classification and uses this value in matching and reporting.
26 belçika belgium Stores the record with the “belgium” classification and uses this value in matching and reporting.
27 belize belize Stores the record with the “belize” classification and uses this value in matching and reporting.
28 benin benin Stores the record with the “benin” classification and uses this value in matching and reporting.
29 bermuda bermuda Stores the record with the “bermuda” classification and uses this value in matching and reporting.
30 ruanda rwanda Stores the record with the “rwanda” classification and uses this value in matching and reporting.
31 brezilya brazil Stores the record with the “brazil” classification and uses this value in matching and reporting.
32 britanya virjin adaları british virgin islands Stores the record with the “british virgin islands” classification and uses this value in matching and reporting.
33 rusya russia Stores the record with the “russia” classification and uses this value in matching and reporting.
34 amerikan samoa american samoa Stores the record with the “american samoa” classification and uses this value in matching and reporting.
35 arjantin argentina Stores the record with the “argentina” classification and uses this value in matching and reporting.
36 cocos (keeling) adaları cocos (keeling) islands Stores the record with the “cocos (keeling) islands” classification and uses this value in matching and reporting.
37 lübnan lebanon Stores the record with the “lebanon” classification and uses this value in matching and reporting.
38 lüksemburg luxembourg Stores the record with the “luxembourg” classification and uses this value in matching and reporting.
39 macaristan hungary Stores the record with the “hungary” classification and uses this value in matching and reporting.
40 madagaskar madagascar Stores the record with the “madagascar” classification and uses this value in matching and reporting.
41 makau macau Stores the record with the “macau” classification and uses this value in matching and reporting.
42 makedonya macedonia Stores the record with the “macedonia” classification and uses this value in matching and reporting.
43 malavi malawi Stores the record with the “malawi” classification and uses this value in matching and reporting.
44 maldivler maldives Stores the record with the “maldives” classification and uses this value in matching and reporting.
45 malezya malaysia Stores the record with the “malaysia” classification and uses this value in matching and reporting.
46 mali mali Stores the record with the “mali” classification and uses this value in matching and reporting.
47 malta malta Stores the record with the “malta” classification and uses this value in matching and reporting.
48 singapur singapore Stores the record with the “singapore” classification and uses this value in matching and reporting.
49 filipinler philippines Stores the record with the “philippines” classification and uses this value in matching and reporting.
50 fildişi sahilleri ivory coast Stores the record with the “ivory coast” classification and uses this value in matching and reporting.
51 faroe adaları faroe islands Stores the record with the “faroe islands” classification and uses this value in matching and reporting.
52 etiyopya ethiopia Stores the record with the “ethiopia” classification and uses this value in matching and reporting.
53 fiji fiji Stores the record with the “fiji” classification and uses this value in matching and reporting.
54 fas morocco Stores the record with the “morocco” classification and uses this value in matching and reporting.
55 eritre eritrea Stores the record with the “eritrea” classification and uses this value in matching and reporting.
56 endonezya indonesia Stores the record with the “indonesia” classification and uses this value in matching and reporting.
57 estonya estonia Stores the record with the “estonia” classification and uses this value in matching and reporting.
58 ermenistan armenia Stores the record with the “armenia” classification and uses this value in matching and reporting.
59 senegal senegal Stores the record with the “senegal” classification and uses this value in matching and reporting.
60 yeni kaledonya new caledonia Stores the record with the “new caledonia” classification and uses this value in matching and reporting.
61 wallis ve futuna adaları wallis and futuna islands Stores the record with the “wallis and futuna islands” classification and uses this value in matching and reporting.
62 tanzanya tanzania Stores the record with the “tanzania” classification and uses this value in matching and reporting.
63 yemen yemen Stores the record with the “yemen” classification and uses this value in matching and reporting.
64 vanuatu vanuatu Stores the record with the “vanuatu” classification and uses this value in matching and reporting.
65 vietnam vietnam Stores the record with the “vietnam” classification and uses this value in matching and reporting.
66 şili chile Stores the record with the “chile” classification and uses this value in matching and reporting.
67 umman oman Stores the record with the “oman” classification and uses this value in matching and reporting.
68 ukrayna ukraine Stores the record with the “ukraine” classification and uses this value in matching and reporting.
69 ürdün jordan Stores the record with the “jordan” classification and uses this value in matching and reporting.
70 uruguay uruguay Stores the record with the “uruguay” classification and uses this value in matching and reporting.
71 liberya liberia Stores the record with the “liberia” classification and uses this value in matching and reporting.
72 lesoto lesotho Stores the record with the “lesotho” classification and uses this value in matching and reporting.
73 irlanda ireland Stores the record with the “ireland” classification and uses this value in matching and reporting.
74 libya libya Stores the record with the “libya” classification and uses this value in matching and reporting.
75 kuveyt kuwait Stores the record with the “kuwait” classification and uses this value in matching and reporting.
76 latvia latvia Stores the record with the “latvia” classification and uses this value in matching and reporting.
77 laos laos Stores the record with the “laos” classification and uses this value in matching and reporting.
78 hollanda netherlands Stores the record with the “netherlands” classification and uses this value in matching and reporting.
79 hollanda antil adaları netherlands antilles Stores the record with the “netherlands antilles” classification and uses this value in matching and reporting.
80 hırvatistan croatia Stores the record with the “croatia” classification and uses this value in matching and reporting.
81 hindistan india Stores the record with the “india” classification and uses this value in matching and reporting.
82 irak iraq Stores the record with the “iraq” classification and uses this value in matching and reporting.
83 litvanya lithuania Stores the record with the “lithuania” classification and uses this value in matching and reporting.
84 honduras honduras Stores the record with the “honduras” classification and uses this value in matching and reporting.
85 hong kong hong kong Stores the record with the “hong kong” classification and uses this value in matching and reporting.
86 tokelau tokelau Stores the record with the “tokelau” classification and uses this value in matching and reporting.
87 virjin adaları (a.b.d.) virgin islands (u.s.) Stores the record with the “virgin islands (u.s.)” classification and uses this value in matching and reporting.
88 iran iran Stores the record with the “iran” classification and uses this value in matching and reporting.
89 holy see (vatikan şehir devleti) holy see (vatican city state) Stores the record with the “holy see (vatican city state)” classification and uses this value in matching and reporting.
90 almanya germany Stores the record with the “germany” classification and uses this value in matching and reporting.
91 svaziland swaziland Stores the record with the “swaziland” classification and uses this value in matching and reporting.
92 anguilla anguilla Stores the record with the “anguilla” classification and uses this value in matching and reporting.
93 sırbistan serbia Stores the record with the “serbia” classification and uses this value in matching and reporting.
94 küba cuba Stores the record with the “cuba” classification and uses this value in matching and reporting.
95 güney sudan south sudan Stores the record with the “south sudan” classification and uses this value in matching and reporting.
96 batum-gürcistan batumi-georgia Stores the record with the “batumi-georgia” classification and uses this value in matching and reporting.
97 heard adası ve mcdonald adaları heard island and mcdonald islands Stores the record with the “heard island and mcdonald islands” classification and uses this value in matching and reporting.
98 santa helena santa helena Stores the record with the “santa helena” classification and uses this value in matching and reporting.
99 san marino san marino Stores the record with the “san marino” classification and uses this value in matching and reporting.
100 kongo (brazavil) congo (brazzaville) Stores the record with the “congo (brazzaville)” classification and uses this value in matching and reporting.
101 kosta rika costa rica Stores the record with the “costa rica” classification and uses this value in matching and reporting.
102 saint martin (fransız tarafı) saint martin (french side) Stores the record with the “saint martin (french side)” classification and uses this value in matching and reporting.
103 saint barthelemy saint barthelemy Stores the record with the “saint barthelemy” classification and uses this value in matching and reporting.
104 samoa samoa Stores the record with the “samoa” classification and uses this value in matching and reporting.
105 saint pierre ve miquelon saint pierre and miquelon Stores the record with the “saint pierre and miquelon” classification and uses this value in matching and reporting.
106 kazakistan kazakhstan Stores the record with the “kazakhstan” classification and uses this value in matching and reporting.
107 kenya kenya Stores the record with the “kenya” classification and uses this value in matching and reporting.
108 kanada canada Stores the record with the “canada” classification and uses this value in matching and reporting.
109 katar qatar Stores the record with the “qatar” classification and uses this value in matching and reporting.
110 kolombiya colombia Stores the record with the “colombia” classification and uses this value in matching and reporting.
111 kongo cumhuriyeti republic of the congo Stores the record with the “republic of the congo” classification and uses this value in matching and reporting.
112 kıbrıs rum kesimi cyprus Stores the record with the “cyprus” classification and uses this value in matching and reporting.
113 kırgızistan kyrgyzstan Stores the record with the “kyrgyzstan” classification and uses this value in matching and reporting.
114 çad chad Stores the record with the “chad” classification and uses this value in matching and reporting.
115 cook adaları cook islands Stores the record with the “cook islands” classification and uses this value in matching and reporting.
116 burundi burundi Stores the record with the “burundi” classification and uses this value in matching and reporting.
117 burkina faso burkina faso Stores the record with the “burkina faso” classification and uses this value in matching and reporting.
118 bulgaristan bulgaria Stores the record with the “bulgaria” classification and uses this value in matching and reporting.
119 brunei brunei Stores the record with the “brunei” classification and uses this value in matching and reporting.
120 cebelitarık gibraltar Stores the record with the “gibraltar” classification and uses this value in matching and reporting.
121 keymen adaları keymen islands Stores the record with the “keymen islands” classification and uses this value in matching and reporting.
122 verde burnu cape verde Stores the record with the “cape verde” classification and uses this value in matching and reporting.
123 butan bhutan Stores the record with the “bhutan” classification and uses this value in matching and reporting.
124 sao tome ve principe sao tome and principe Stores the record with the “sao tome and principe” classification and uses this value in matching and reporting.
125 tuvalu tuvalu Stores the record with the “tuvalu” classification and uses this value in matching and reporting.
126 zimbabve zimbabwe Stores the record with the “zimbabwe” classification and uses this value in matching and reporting.
127 guernsey guernsey Stores the record with the “guernsey” classification and uses this value in matching and reporting.
128 suudi arabistan saudi arabia Stores the record with the “saudi arabia” classification and uses this value in matching and reporting.
129 filistin özerk bölgesi self-governing state of palestine Stores the record with the “self-governing state of palestine” classification and uses this value in matching and reporting.
130 finlandiya finland Stores the record with the “finland” classification and uses this value in matching and reporting.
131 fransa france Stores the record with the “france” classification and uses this value in matching and reporting.
132 fransız guyanası french guiana Stores the record with the “french guiana” classification and uses this value in matching and reporting.
133 fransız polonezyası french polynesia Stores the record with the “french polynesia” classification and uses this value in matching and reporting.
134 gabon gabon Stores the record with the “gabon” classification and uses this value in matching and reporting.
135 galler (birleşik krallık) wales (uk) Stores the record with the “wales (uk)” classification and uses this value in matching and reporting.
136 gambiya gambia Stores the record with the “gambia” classification and uses this value in matching and reporting.
137 gana ghana Stores the record with the “ghana” classification and uses this value in matching and reporting.
138 gine guinea Stores the record with the “guinea” classification and uses this value in matching and reporting.
139 suriye syria Stores the record with the “syria” classification and uses this value in matching and reporting.
140 surinam suriname Stores the record with the “suriname” classification and uses this value in matching and reporting.
141 saint vincent saint vincent Stores the record with the “saint vincent” classification and uses this value in matching and reporting.
142 saint lucia saint lucia Stores the record with the “saint lucia” classification and uses this value in matching and reporting.
143 saint kitts ve nevis saint kitts and nevis Stores the record with the “saint kitts and nevis” classification and uses this value in matching and reporting.
144 sri lanka sri lanka Stores the record with the “sri lanka” classification and uses this value in matching and reporting.
145 yunanistan greece Stores the record with the “greece” classification and uses this value in matching and reporting.
146 gine-bissau guinea-bissau Stores the record with the “guinea-bissau” classification and uses this value in matching and reporting.
147 tayvan taiwan Stores the record with the “taiwan” classification and uses this value in matching and reporting.
148 sierra leone sierra leone Stores the record with the “sierra leone” classification and uses this value in matching and reporting.
149 togo togo Stores the record with the “togo” classification and uses this value in matching and reporting.
150 tongo tongo Stores the record with the “tongo” classification and uses this value in matching and reporting.
151 tayland thailand Stores the record with the “thailand” classification and uses this value in matching and reporting.
152 afganistan afghanistan Stores the record with the “afghanistan” classification and uses this value in matching and reporting.
153 saipan saipan Stores the record with the “saipan” classification and uses this value in matching and reporting.
154 türkiye turkey Stores the record with the “turkey” classification and uses this value in matching and reporting.
155 trinidat ve tobago trinidad and tobago tobago Stores the record with the “trinidad and tobago tobago” classification and uses this value in matching and reporting.
156 angola angola Stores the record with the “angola” classification and uses this value in matching and reporting.
157 türk ve kaikos adaları turks and caicos islands Stores the record with the “turks and caicos islands” classification and uses this value in matching and reporting.
158 türkmenistan turkmenistan Stores the record with the “turkmenistan” classification and uses this value in matching and reporting.
159 uganda uganda Stores the record with the “uganda” classification and uses this value in matching and reporting.
160 yeni zelanda new zealand Stores the record with the “new zealand” classification and uses this value in matching and reporting.
161 venezuella venezuella Stores the record with the “venezuella” classification and uses this value in matching and reporting.
162 fransa güney bölgeleri french southern territories Stores the record with the “french southern territories” classification and uses this value in matching and reporting.
163 tunus tunisia Stores the record with the “tunisia” classification and uses this value in matching and reporting.
164 kamerun cameroon Stores the record with the “cameroon” classification and uses this value in matching and reporting.
165 kamboçya cambodia Stores the record with the “cambodia” classification and uses this value in matching and reporting.
166 slovak cumhuriyeti slovak republic Stores the record with the “slovak republic” classification and uses this value in matching and reporting.
167 slovenya slovenia Stores the record with the “slovenia” classification and uses this value in matching and reporting.
168 jersey jersey Stores the record with the “jersey” classification and uses this value in matching and reporting.
169 ingiliz hint okyanusu bölgesi british indian ocean territory Stores the record with the “british indian ocean territory” classification and uses this value in matching and reporting.
170 israil israel Stores the record with the “israel” classification and uses this value in matching and reporting.
171 ispanya spain Stores the record with the “spain” classification and uses this value in matching and reporting.
172 isviçre switzerland Stores the record with the “switzerland” classification and uses this value in matching and reporting.
173 isveç sweden Stores the record with the “sweden” classification and uses this value in matching and reporting.
174 izlanda iceland Stores the record with the “iceland” classification and uses this value in matching and reporting.
175 italya italy Stores the record with the “italy” classification and uses this value in matching and reporting.
176 japonya japan Stores the record with the “japan” classification and uses this value in matching and reporting.
177 jameyka jameika Stores the record with the “jameika” classification and uses this value in matching and reporting.
178 avusturalya australia Stores the record with the “australia” classification and uses this value in matching and reporting.
179 aruba aruba Stores the record with the “aruba” classification and uses this value in matching and reporting.
180 azerbaycan azerbaijan Stores the record with the “azerbaijan” classification and uses this value in matching and reporting.
181 avusturya austria Stores the record with the “austria” classification and uses this value in matching and reporting.
182 bahreyn bahrain Stores the record with the “bahrain” classification and uses this value in matching and reporting.
183 bahamalar bahamas Stores the record with the “bahamas” classification and uses this value in matching and reporting.
184 barbados barbados Stores the record with the “barbados” classification and uses this value in matching and reporting.
185 bangladeş bangladesh Stores the record with the “bangladesh” classification and uses this value in matching and reporting.
186 belarus (beyaz rusya) belarus (belarus) Stores the record with the “belarus (belarus)” classification and uses this value in matching and reporting.
187 barbuda / antigua barbuda/antigua Stores the record with the “barbuda/antigua” classification and uses this value in matching and reporting.
188 lihtenştayn liechtenstein Stores the record with the “liechtenstein” classification and uses this value in matching and reporting.
189 svalbard svalbard Stores the record with the “svalbard” classification and uses this value in matching and reporting.
190 zambiya zambia Stores the record with the “zambia” classification and uses this value in matching and reporting.
191 panama panama Stores the record with the “panama” classification and uses this value in matching and reporting.
192 palau palau Stores the record with the “palau” classification and uses this value in matching and reporting.
193 paraguay paraguay Stores the record with the “paraguay” classification and uses this value in matching and reporting.
194 papua yeni gine papua new guinea Stores the record with the “papua new guinea” classification and uses this value in matching and reporting.
195 polonya poland Stores the record with the “poland” classification and uses this value in matching and reporting.
196 peru peru Stores the record with the “peru” classification and uses this value in matching and reporting.
197 porto riko puerto rico Stores the record with the “puerto rico” classification and uses this value in matching and reporting.
198 portekiz portugal Stores the record with the “portugal” classification and uses this value in matching and reporting.
199 romanya romania Stores the record with the “romania” classification and uses this value in matching and reporting.
200 reunion adası reunion island Stores the record with the “reunion island” classification and uses this value in matching and reporting.
201 orta afrika cumhuriyeti central africa republic of Stores the record with the “central africa republic of” classification and uses this value in matching and reporting.
202 pitcairn pitcairn Stores the record with the “pitcairn” classification and uses this value in matching and reporting.
203 myanmar myanmar Stores the record with the “myanmar” classification and uses this value in matching and reporting.
204 nauru nauru Stores the record with the “nauru” classification and uses this value in matching and reporting.
205 niu niu Stores the record with the “niu” classification and uses this value in matching and reporting.
206 norfolk adası norfolk island Stores the record with the “norfolk island” classification and uses this value in matching and reporting.
207 kiribati kiribati Stores the record with the “kiribati” classification and uses this value in matching and reporting.
208 komor comoros Stores the record with the “comoros” classification and uses this value in matching and reporting.
209 kore demokratik halk cumhuriyeti democratic people's republic of korea Stores the record with the “democratic people's republic of korea” classification and uses this value in matching and reporting.
210 mayotte mayotte Stores the record with the “mayotte” classification and uses this value in matching and reporting.
211 güney gürcistan ve güney sandwich adaları south georgia and the south sandwich islands Stores the record with the “south georgia and the south sandwich islands” classification and uses this value in matching and reporting.
212 ekvator ginesi equatorial guinea Stores the record with the “equatorial guinea” classification and uses this value in matching and reporting.
213 el salvador el salvador Stores the record with the “el salvador” classification and uses this value in matching and reporting.
214 dominika dominica Stores the record with the “dominica” classification and uses this value in matching and reporting.
215 ekvator ecuador Stores the record with the “ecuador” classification and uses this value in matching and reporting.
216 doğu timor east timor Stores the record with the “east timor” classification and uses this value in matching and reporting.
217 dominik cumhuriyeti dominican republic Stores the record with the “dominican republic” classification and uses this value in matching and reporting.
218 danimarka denmark Stores the record with the “denmark” classification and uses this value in matching and reporting.
219 djibouti djibouti Stores the record with the “djibouti” classification and uses this value in matching and reporting.
220 çek cumhuriyeti czech republic Stores the record with the “czech republic” classification and uses this value in matching and reporting.
221 çin china Stores the record with the “china” classification and uses this value in matching and reporting.
222 a.b.d. united states of america Stores the record with the “united states of america” classification and uses this value in matching and reporting.
223 andorra andorra Stores the record with the “andorra” classification and uses this value in matching and reporting.
224 arnavutluk albania Stores the record with the “albania” classification and uses this value in matching and reporting.
225 nikaragua nicaragua Stores the record with the “nicaragua” classification and uses this value in matching and reporting.
226 norveç norway Stores the record with the “norway” classification and uses this value in matching and reporting.
227 nijer niger Stores the record with the “niger” classification and uses this value in matching and reporting.
228 nijerya nigeria Stores the record with the “nigeria” classification and uses this value in matching and reporting.
229 namibya namibia Stores the record with the “namibia” classification and uses this value in matching and reporting.
230 nepal nepal Stores the record with the “nepal” classification and uses this value in matching and reporting.
231 moritanya mauritania Stores the record with the “mauritania” classification and uses this value in matching and reporting.
232 mozambik mozambique Stores the record with the “mozambique” classification and uses this value in matching and reporting.
233 ingiltere united kingdom Stores the record with the “united kingdom” classification and uses this value in matching and reporting.
234 kosova kosovo Stores the record with the “kosovo” classification and uses this value in matching and reporting.
235 özbekistan uzbekistan Stores the record with the “uzbekistan” classification and uses this value in matching and reporting.
236 pakistan pakistan Stores the record with the “pakistan” classification and uses this value in matching and reporting.
237 güney kore south korea Stores the record with the “south korea” classification and uses this value in matching and reporting.
238 güney afrika south africa Stores the record with the “south africa” classification and uses this value in matching and reporting.
239 guyana guyana Stores the record with the “guyana” classification and uses this value in matching and reporting.
240 guatemala guatemala Stores the record with the “guatemala” classification and uses this value in matching and reporting.
241 guam guam Stores the record with the “guam” classification and uses this value in matching and reporting.
242 guadelup guadelup Stores the record with the “guadelup” classification and uses this value in matching and reporting.
243 grönland greenland Stores the record with the “greenland” classification and uses this value in matching and reporting.
244 grenada grenada Stores the record with the “grenada” classification and uses this value in matching and reporting.
245 haiti haiti Stores the record with the “haiti” classification and uses this value in matching and reporting.
246 gürcistan georgia Stores the record with the “georgia” classification and uses this value in matching and reporting.
247 solomon adaları solomon islands Stores the record with the “solomon islands” classification and uses this value in matching and reporting.
248 isle of man isle of man Stores the record with the “isle of man” classification and uses this value in matching and reporting.
249 karadağ montenegro Stores the record with the “montenegro” classification and uses this value in matching and reporting.
250 kuzey kıbrıs türk cumhuriyeti turkish republic of northern cyprus Stores the record with the “turkish republic of northern cyprus” classification and uses this value in matching and reporting.

Example

0 — western sahara
About WDC Campaign / Customer / Journey / Operation
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Customer / Journey / Operation

Tracks one channel delivery, its provider response, and subsequent delivery checks in a single operation record.

Operation flow

If send-API code returns success, the operation is created as active with delivery and customer-success statuses waiting. When the provider returns a delivery identifier, the timer queries the record again; date, counter, duration, response, and status are updated on each check. When follow-up time expires, an indeterminate result is changed to unsuccessful and checking ends.

Code compatibility: Current WDM options must be treated as authoritative. Status mappings for parameter 30 in CampaignConfig are legacy, the channel reader for parameter 38 mistakenly reads parameter 4, and parameter 41 callback status is not used by the standard backend flow.
0. status

0. status

Parameter identifier: 0 Data type: select
Turkish name durum
English name status

Description

The activity state of the operation record. After a successful provider call, the record is created as active; activity is a record-lifecycle field separate from delivery result and delivery-check result. Although the inspected delivery-check query does not directly filter this field, passive indicates that the operation is out of use.

Options

Value Turkish English Behavior
0 pasif passive Classifies the field as “passive”; processes and reports use the selected value.
1 aktif active Classifies the field as “active”; processes and reports use the selected value.

Example

0 — passive
1. campaign name

1. campaign name

Parameter identifier: 1 Data type: text
Turkish name kampanya adı
English name campaign name

Description

The display name of the campaign associated with the operation. Channel processing copies the name from campaign configuration when creating the operation, preserving the context in which the operation was produced even if the campaign record later changes.

Example

campaign name-example
2. customer id

2. customer id

Parameter identifier: 2 Data type: text
Turkish name müşteri id
English name customer id

Description

The source identifier of the customer to whom the message was sent. It is copied from the journey into the operation record and associates delivery, success analysis, and report output with the same customer.

Example

customer id-example
3. provider send api id

3. provider send api id

Parameter identifier: 3 Data type: text
Turkish name sağlayıcı gönderim api id
English name provider send api id

Description

The client identifier of the user API record that sends the message to the provider. It is received from the send-API setting in the channel step; because the code loads API configuration and executes provider code with this identifier, an incorrect or missing identifier prevents delivery.

Example

provider send api id-example
4. campaign type

4. campaign type

Parameter identifier: 4 Data type: select
Turkish name kampanya tipi
English name campaign type

Description

The business type of the campaign that produced the operation. Digital marketing, survey, or digital advertising is copied into the operation; reporting and type-specific processing use this classification.

Options

Value Turkish English Behavior
0 dijital pazarlama digital marketing Classifies the field as “digital marketing”; processes and reports use the selected value.
1 anket survey Classifies the field as “survey”; processes and reports use the selected value.
2 dijital reklam digital advertising Classifies the field as “digital advertising”; processes and reports use the selected value.

Example

0 — digital marketing
5. customer source

5. customer source

Parameter identifier: 5 Data type: select
Turkish name müşteri kaynağı
English name customer source

Description

Specifies whether the customer came from Wisdomera or the website source. Because it is copied from campaign settings at operation time, operation reports can distinguish acquisition source without rereading the campaign record.

Options

Value Turkish English Behavior
0 wisdomera wisdomera Classifies the field as “wisdomera”; processes and reports use the selected value.
1 website website Classifies the field as “website”; processes and reports use the selected value.

Example

0 — wisdomera
6. advertisement type

6. advertisement type

Parameter identifier: 6 Data type: select
Turkish name reklam tipi
English name advertisement type

Description

Classifies whether a digital-advertising customer came from a lead form or an appointment source. It is meaningful only in the relevant advertising flow, and the campaign-configuration value is copied into the operation.

Options

Value Turkish English Behavior
0 lead form lead form Classifies the field as “lead form”; processes and reports use the selected value.
1 randevu appointment Classifies the field as “appointment”; processes and reports use the selected value.

Example

0 — lead form
7. delivery status

7. delivery status

Parameter identifier: 7 Data type: select
Turkish name ileti durumu
English name delivery status

Description

Tracks the result of provider delivery. A new operation is created as `wait`; success analysis or subsequent processing can update it to success, unsuccess, or skip. It is different from parameter 30, which is used for the delivery-check service.

Options

Value Turkish English Behavior
0 beklemede wait Sets delivery result to “wait”; delivery checking selects only records that are waiting and have a delivery identifier.
1 başarılı success Sets delivery result to “success”; delivery checking selects only records that are waiting and have a delivery identifier.
2 başarısız unsuccess Sets delivery result to “unsuccess”; delivery checking selects only records that are waiting and have a delivery identifier.
3 atlandı skip Sets delivery result to “skip”; delivery checking selects only records that are waiting and have a delivery identifier.

Example

0 — wait
8. customer success status

8. customer success status

Parameter identifier: 8 Data type: select
Turkish name müşteri başarı durumu
English name customer success status

Description

The customer’s campaign-success result associated with the operation. A new operation starts as `wait`; customer-success analysis later changes it to success or unsuccess. This field represents achievement of the business objective, not technical message delivery.

Options

Value Turkish English Behavior
0 beklemede wait Classifies the field as “wait”; processes and reports use the selected value.
1 başarılı success Classifies the field as “success”; processes and reports use the selected value.
2 başarısız unsuccess Classifies the field as “unsuccess”; processes and reports use the selected value.

Example

0 — wait
9. last customer process start date

9. last customer process start date

Parameter identifier: 9 Data type: datetime
Turkish name son müşteri işlem başlama tarihi
English name last customer process start date

Description

The customer-process start time copied from the journey create date when the operation is created. This allows the communication operation to be compared with the time the customer entered the campaign; despite the word “last,” the inspected creation code uses the journey `create_date` value.

Example

2026-10-25T09:45:55
10. create date

10. create date

Parameter identifier: 10 Data type: datetime
Turkish name oluşturma tarihi
English name create date

Description

The Coordinated Universal Time at which the operation record is created after provider delivery is considered successful. It indicates technical record creation and is written at the same time as operation date.

Example

2026-10-25T09:45:55
11. update date

11. update date

Parameter identifier: 11 Data type: datetime
Turkish name güncelleme tarihi
English name update date

Description

Defined to store the last update time of the operation record. The inspected creation and delivery-check code does not write this field automatically; therefore, parameter 29 must be used for check time and this field must not be assumed to populate itself.

Example

2026-10-25T09:45:55
12. webservice response

12. webservice response

Parameter identifier: 12 Data type: textarea
Turkish name webservis yanıtı
English name webservice response

Description

The raw response returned by the delivery provider for the initial API call. If the response is a dictionary it is converted to JSON text; otherwise it is stored as received. It supports error investigation and provider traceability, but its display must be controlled because it may contain sensitive data.

Example

{"status":"accepted"}
13. webservice time (seconds)

13. webservice time (seconds)

Parameter identifier: 13 Data type: integer
Turkish name webservis süresi (saniye)
English name webservice time (seconds)

Description

The whole-second difference between the start and end of the initial provider-delivery call. Because the code calculates the duration and converts it to an integer, calls shorter than one second may appear as `0`; the value is not the time required for delivery to reach the customer.

Example

3
14. operation date

14. operation date

Parameter identifier: 14 Data type: datetime
Turkish name operasyon tarihi
English name operation date

Description

The Coordinated Universal Time at which the channel operation was created and delivery occurred. Delivery follow-up duration is calculated from the hour difference between the current time and this date; an incorrect date causes checking to end too early or too late.

Example

2026-10-25T09:45:55
15. sent message

15. sent message

Parameter identifier: 15 Data type: textarea
Turkish name gönderilen mesaj
English name sent message

Description

The final message content prepared during channel selection and sent to the provider. The operation record copies it from the eligible channel message in the journey, allowing the actual delivered text to be audited even if the template later changes.

Example

sent message-example
16. campaign client id

16. campaign client id

Parameter identifier: 16 Data type: text
Turkish name kampanya client id
English name campaign client id

Description

The client identifier of the campaign record associated with the operation. Channel processing writes it from campaign configuration; Power BI transfer, delivery-check summary, and reporting use it to group operations under the campaign.

Example

campaign client id-example
17. campaign wdmr id

17. campaign wdmr id

Parameter identifier: 17 Data type: text
Turkish name kampanya wdmr id
English name campaign wdmr id

Description

The Wisdom data model record identifier of the campaign record. Unlike the client identifier, it points to the record in the storage layer and is copied from campaign configuration when the operation is created.

Example

campaign wdmr id-example
18. institution name

18. institution name

Parameter identifier: 18 Data type: text
Turkish name kurum adı
English name institution name

Description

A copy, at operation time, of the institution name associated with the customer. It provides human-readable context for institution-based providers, reporting, or distribution analysis.

Example

institution name-example
19. institution code

19. institution code

Parameter identifier: 19 Data type: text
Turkish name kurum kodu
English name institution code

Description

The source code of the institution associated with the customer. Channel processing copies it from the journey; this code can be used instead of the display name for technical institution-based matching.

Example

institution code-example
20. utm source

20. utm source

Parameter identifier: 20 Data type: text
Turkish name utm kaynağı
English name utm source

Description

The UTM source value defined to identify the digital traffic source. The inspected standard channel-operation creation code does not write this field; it can be used in reporting only if another integration or update flow supplies it.

Example

utm source-example
21. integrated system id

21. integrated system id

Parameter identifier: 21 Data type: text
Turkish name entegre sistem id
English name integrated system id

Description

The identifier of the external or integrated-system record associated with the operation. Because no automatic write was found in the inspected standard delivery and delivery-check flow, population of this field depends on the relevant integration.

Example

integrated system id-example
22. survey link

22. survey link

Parameter identifier: 22 Data type: text
Turkish name anket linki
English name survey link

Description

A copy, at operation time, of the survey link generated in the journey. Because a survey-campaign message can contain this link, the operation record preserves which address was used in the delivery context.

Example

survey link-example
23. survey system id

23. survey system id

Parameter identifier: 23 Data type: text
Turkish name anket sistemi id
English name survey system id

Description

A copy, at operation time, of the survey-system identifier in the journey. It helps associate the delivered link and subsequent survey operations with the correct survey record.

Example

survey system id-example
24. phone number

24. phone number

Parameter identifier: 24 Data type: text
Turkish name telefon no
English name phone number

Description

A copy, at operation time, of the customer number used for a phone-based channel. The code writes the GSM value from the journey here, making it possible to trace which target received SMS, IVR, or phone-call operations.

Example

phone number-example
25. mail

25. mail

Parameter identifier: 25 Data type: text
Turkish name mail
English name mail

Description

A copy, at operation time, of the customer email address used for the email channel. It is transferred from the journey and associates the delivery result with the target address.

Example

mail-example
26. mobile notification id

26. mobile notification id

Parameter identifier: 26 Data type: text
Turkish name mobil bildirim id
English name mobile notification id

Description

The device or subscription identifier targeted by push-notification delivery. It is copied from the journey into the operation and identifies the mobile target for which the provider response was produced.

Example

mobile notification id-example
27. mobile notification group id

27. mobile notification group id

Parameter identifier: 27 Data type: text
Turkish name mobil bildirim grubu id
English name mobile notification group id

Description

The group identifier associated with the push-notification target. It is copied from the journey into the operation to preserve targeting context for group-based mobile delivery.

Example

mobile notification group id-example
28. delivery check id

28. delivery check id

Parameter identifier: 28 Data type: text
Turkish name ileti kontrol id
English name delivery check id

Description

The message identifier returned by the initial delivery provider and used in later delivery queries. The timer checks only operations whose delivery status is wait and whose field is populated; without this identifier, the operation does not enter the automatic delivery-check query.

Example

delivery check id-example
29. delivery last check date

29. delivery last check date

Parameter identifier: 29 Data type: datetime
Turkish name ileti son kontrol tarihi
English name delivery last check date

Description

The Coordinated Universal Time at which the delivery-check service last ran. It is refreshed with the current time on every result write, making the latest query time visible together with the check count.

Example

2026-10-25T09:45:55
30. delivery check status

30. delivery check status

Parameter identifier: 30 Data type: select
Turkish name ileti kontrol durumu
English name delivery check status

Description

The current result of the delivery-check service; the value returned by provider check code is written directly as a WDM option. In the current schema it represents unsuccessful, success, authentication error, delivery identifier not found, checking continues, or no service response. Because legacy `CampaignConfig` mappings use different meanings, WDM values must be treated as authoritative when reading this field.

Options

Value Turkish English Behavior
0 başarısız unsuccess Records the latest delivery-check result as “unsuccess”.
1 başarılı success Records the latest delivery-check result as “success”.
2 hatalı kullanıcı adı veya şifre incorrect username or password Records the latest delivery-check result as “incorrect username or password”.
3 ileti id bulunamadı delivery id not found Records the latest delivery-check result as “delivery id not found”.
4 ileti takip ediliyor delivery check continue Records the latest delivery-check result as “delivery check continue”.
5 servisten yanıt alınamadı no response from service Records the latest delivery-check result as “no response from service”.

Example

0 — unsuccess
31. undelivered reason

31. undelivered reason

Parameter identifier: 31 Data type: select
Turkish name iletilmeme nedeni
English name undelivered reason

Description

Classifies why the message could not be delivered. The field is updated when provider check code returns a failure reason; the detailed provider explanation is stored separately in parameter 32.

Options

Value Turkish English Behavior
0 hatalı faulty Classifies the field as “faulty”; processes and reports use the selected value.
1 zaman aşımı veya iys red timeout or mms rejected Classifies the field as “timeout or mms rejected”; processes and reports use the selected value.
2 zaman aşımı timeout Classifies the field as “timeout”; processes and reports use the selected value.
3 iys red mms rejected Classifies the field as “mms rejected”; processes and reports use the selected value.
4 kara listede blacklisted Classifies the field as “blacklisted”; processes and reports use the selected value.
5 iys red veya iys onay kodu yok mms rejected or no mms approval code Classifies the field as “mms rejected or no mms approval code”; processes and reports use the selected value.

Example

0 — faulty
32. undelivered reason information

32. undelivered reason information

Parameter identifier: 32 Data type: textarea
Turkish name iletilmeme nedeni açıklama
English name undelivered reason information

Description

The detailed text for the non-delivery reason returned by the provider or check code. It complements the category in parameter 31 with a technical message; display permission must be restricted because it may contain raw error information or personal data.

Example

undelivered reason information-example
33. delivery check count

33. delivery check count

Parameter identifier: 33 Data type: integer
Turkish name ileti kontrol adedi
English name delivery check count

Description

Shows how many times the delivery-check service has run for the operation. It is written as `1` on the first check and incremented after each subsequent result; the counter advances only when a check result is produced and the record is updated.

Example

3
34. delivery check follow-up time (hour)

34. delivery check follow-up time (hour)

Parameter identifier: 34 Data type: integer
Turkish name ileti kontrol takip süresi (saat)
English name delivery check follow-up time (hour)

Description

The maximum follow-up duration returned by provider check code. The code treats the value as hours and sets parameter 37, time-ended status, to `yes` when whole hours elapsed since operation date exceed this limit; zero or empty does not enable expiration calculation.

Example

3
35. delivery check webservice time (seconds)

35. delivery check webservice time (seconds)

Parameter identifier: 35 Data type: integer
Turkish name ileti kontrol webservis süresi (saniye)
English name delivery check webservice time (seconds)

Description

The duration, in seconds, of one delivery-check webservice call. The difference between its start and end times is recorded; this field is separate from parameter 13, the initial delivery duration.

Example

3
36. delivery check webservice response

36. delivery check webservice response

Parameter identifier: 36 Data type: textarea
Turkish name ileti kontrol webservis yanıtı
English name delivery check webservice response

Description

The raw response returned by the delivery-check provider for the latest query. When check code returns a value, the record is updated and the latest response is preserved for technical investigation; this field is separate from parameter 12, the initial-delivery response.

Example

delivery check webservice response-example
37. delivery check time end status

37. delivery check time end status

Parameter identifier: 37 Data type: select
Turkish name ileti takip süresi dolma durumu
English name delivery check time end status

Description

Specifies whether the configured follow-up period for the message has expired. It is set to `yes` when elapsed hours exceed the follow-up duration; if the check result is neither success nor unsuccess at that point, the code changes parameter 30 to unsuccessful to end indefinite checking.

Options

Value Turkish English Behavior
0 hayır no Indicates that follow-up time has not yet expired.
1 evet yes Indicates that follow-up time has expired and continuing indeterminate checks will end.

Example

0 — no
38. channel type

38. channel type

Parameter identifier: 38 Data type: select
Turkish name kanal tipi
English name channel type

Description

Specifies whether the operation was produced through SMS, push notification, IVR, email, or phone call. The type from the channel step is copied into the operation and determines how target contact fields and provider behavior are interpreted. The `CampaignConfig` reader mistakenly reads parameter 4, campaign type, instead of this field; the direct WDM value is the reliable source.

Options

Value Turkish English Behavior
0 sms sms Classifies the field as “sms”; processes and reports use the selected value.
1 mobil bildirim push notification Classifies the field as “push notification”; processes and reports use the selected value.
2 ivr ivr Classifies the field as “ivr”; processes and reports use the selected value.
3 mail mail Classifies the field as “mail”; processes and reports use the selected value.
4 telefon ile arama phone call Classifies the field as “phone call”; processes and reports use the selected value.

Example

0 — sms
39. provider delivery check api id

39. provider delivery check api id

Parameter identifier: 39 Data type: text
Turkish name sağlayıcı ileti kontrol api id
English name provider delivery check api id

Description

The client identifier of the user API record that queries delivery result with the message identifier. It is copied from the channel step into the operation; check code runs only when both the identifier and API code exist, and no automatic check result can be produced if either is missing.

Example

provider delivery check api id-example
40. channel design id

40. channel design id

Parameter identifier: 40 Data type: text
Turkish name kanal dizayn id
English name channel design id

Description

The client identifier of the campaign channel-design record that produced the operation. It is copied from the selected eligible channel setting and makes the source of message, provider, and step configuration traceable.

Example

channel design id-example
41. delivery callback status

41. delivery callback status

Parameter identifier: 41 Data type: select
Turkish name ileti callback durumu
English name delivery callback status

Description

A field present in the WDM schema to classify the business result of phone or call-center feedback. However, an inspected backend comment marks the field as “no longer present,” the operation configuration reader does not read parameter 41, and standard creation and checking flows do not write it; therefore, it must not be assumed to update automatically.

Options

Value Turkish English Behavior
0 bilgi verildi information provided Classifies the field as “information provided”; processes and reports use the selected value.
1 checkup verildi check-up given Classifies the field as “check-up given”; processes and reports use the selected value.
2 checkup satışı yapıldı check-up sale made Classifies the field as “check-up sale made”; processes and reports use the selected value.
3 şikayet istek öneri complaint, request, suggestion Classifies the field as “complaint, request, suggestion”; processes and reports use the selected value.
4 randevu verildi appointment given Classifies the field as “appointment given”; processes and reports use the selected value.
5 ulaşılamadı unreachable Classifies the field as “unreachable”; processes and reports use the selected value.
6 cevapsız unanswered Classifies the field as “unanswered”; processes and reports use the selected value.
7 hatalı numara incorrect number Classifies the field as “incorrect number”; processes and reports use the selected value.
8 daha sonra aranacak will be called later Classifies the field as “will be called later”; processes and reports use the selected value.

Example

0 — information provided
About WDC Campaign / Survey Settings
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Survey Settings

Defines predefined and manual questions, answers, and ordering for a campaign survey generated by WDC.

Survey-generation flow

The first active settings record is selected. Predefined questions are prepared with fixed five-point satisfaction answers, while active manual questions are prepared with their type and active answers. Order JSON arranges questions; when general opinion is enabled, a fixed textarea question is appended last.

Code finding: WDM values and backend mapping for question type disagree for values 5 and 6. In addition, create date is rewritten on every save while update date is not written.
0. status

0. status

Parameter identifier: 0 Data type: select
Turkish name durum
English name status

Description

The availability state of the survey-settings record. When a WDC survey link is created, settings under the campaign are inspected in sequence; questions are prepared from the first active record and the loop then stops, while a passive record contributes nothing to the survey payload.

Options

Value Turkish English Behavior
0 pasif passive Excludes this setting from survey generation.
1 aktif active Makes this setting eligible for survey generation; the first active record is selected.

Example

0 — passive
1. question list

1. question list

Parameter identifier: 1 Data type: checkbox
Turkish name soru listesi
English name question list

Description

The multiple selection of questions to include from the predefined question catalog. Each selected option uses its value as the question identifier and its translated text as the question label, and the backend adds the same five answers, identified 1–5 from “very dissatisfied” to “very satisfied,” to every predefined question; therefore, predefined questions are produced as select questions.

Options

Value Turkish English Behavior
0 hizmetimizi başkalarına tavsiye etme olasılığınız nedir? how likely are you to recommend our service to others? Adds the predefined “how likely are you to recommend our service to others?” question to the survey with the fixed five-point satisfaction answers.
1 genel olarak aldığınız hizmeti nasıl değerlendirirsiniz? how would you rate the service you received overall? Adds the predefined “how would you rate the service you received overall?” question to the survey with the fixed five-point satisfaction answers.
2 hekimin sunduğu hizmetten ne kadar memnun kaldınız? how satisfied were you with the doctor's service? Adds the predefined “how satisfied were you with the doctor's service?” question to the survey with the fixed five-point satisfaction answers.
3 banko ve kayıt işlemleri sürecini nasıl değerlendirirsiniz? how would you rate the reception and registration process? Adds the predefined “how would you rate the reception and registration process?” question to the survey with the fixed five-point satisfaction answers.
4 hemşirelik hizmetlerinden ne düzeyde memnun kaldınız? how satisfied were you with the nursing services? Adds the predefined “how satisfied were you with the nursing services?” question to the survey with the fixed five-point satisfaction answers.
5 estetisyen hizmetini nasıl değerlendirirsiniz? how would you rate the beautician's service? Adds the predefined “how would you rate the beautician's service?” question to the survey with the fixed five-point satisfaction answers.
6 podolog hizmetinden memnun kaldınız mı? were you satisfied with the podologist's service? Adds the predefined “were you satisfied with the podologist's service?” question to the survey with the fixed five-point satisfaction answers.
7 temizlik hizmetlerini nasıl değerlendirirsiniz? how would you rate the cleaning services? Adds the predefined “how would you rate the cleaning services?” question to the survey with the fixed five-point satisfaction answers.
8 yemek hizmetlerinden ne kadar memnun kaldınız? how satisfied were you with the food services? Adds the predefined “how satisfied were you with the food services?” question to the survey with the fixed five-point satisfaction answers.
9 yatış ve taburculuk sürecini nasıl değerlendirirsiniz? how would you rate the admission and discharge process? Adds the predefined “how would you rate the admission and discharge process?” question to the survey with the fixed five-point satisfaction answers.
10 otopark hizmetlerinden memnun kaldınız mı? were you satisfied with the parking services? Adds the predefined “were you satisfied with the parking services?” question to the survey with the fixed five-point satisfaction answers.
11 vale otopark hizmetini nasıl değerlendirirsiniz? how would you rate the valet parking service? Adds the predefined “how would you rate the valet parking service?” question to the survey with the fixed five-point satisfaction answers.
12 uyku teknikerinin hizmetinden ne ölçüde memnun kaldınız? how satisfied were you with the sleep technician's service? Adds the predefined “how satisfied were you with the sleep technician's service?” question to the survey with the fixed five-point satisfaction answers.
13 embriyolog tarafından sunulan hizmeti nasıl değerlendirirsiniz? how would you rate the service provided by the embryologist? Adds the predefined “how would you rate the service provided by the embryologist?” question to the survey with the fixed five-point satisfaction answers.
14 fizyoterapist hizmetinden ne kadar memnun kaldınız? how satisfied were you with the physiotherapist's service? Adds the predefined “how satisfied were you with the physiotherapist's service?” question to the survey with the fixed five-point satisfaction answers.
15 emzirme odasının olanaklarını nasıl değerlendirirsiniz? how would you rate the facilities of the breastfeeding room? Adds the predefined “how would you rate the facilities of the breastfeeding room?” question to the survey with the fixed five-point satisfaction answers.
16 göz teknikeri tarafından sunulan hizmetten memnun kaldınız mı? were you satisfied with the service provided by the eye technician? Adds the predefined “were you satisfied with the service provided by the eye technician?” question to the survey with the fixed five-point satisfaction answers.
17 kan alma sürecini nasıl değerlendirirsiniz? how would you rate the blood sampling process? Adds the predefined “how would you rate the blood sampling process?” question to the survey with the fixed five-point satisfaction answers.
18 kafeterya hizmetlerini nasıl değerlendirirsiniz? how would you rate the cafeteria services? Adds the predefined “how would you rate the cafeteria services?” question to the survey with the fixed five-point satisfaction answers.
19 anestezi sürecini nasıl değerlendirirsiniz? how would you rate the anesthesia process? Adds the predefined “how would you rate the anesthesia process?” question to the survey with the fixed five-point satisfaction answers.
20 diş teknikerinin sunduğu hizmetten memnun kaldınız mı? were you satisfied with the service provided by the dental technician? Adds the predefined “were you satisfied with the service provided by the dental technician?” question to the survey with the fixed five-point satisfaction answers.
21 klinik içi koordinasyon ve yönlendirmeyi nasıl değerlendirirsiniz? how would you rate the in-clinic coordination and guidance? Adds the predefined “how would you rate the in-clinic coordination and guidance?” question to the survey with the fixed five-point satisfaction answers.
22 mobil uygulama deneyiminiz nasıldı? what was your experience with the mobile application? Adds the predefined “what was your experience with the mobile application?” question to the survey with the fixed five-point satisfaction answers.
23 radyoterapi ekibinin hizmetinden ne kadar memnun kaldınız? how satisfied were you with the service of the radiotherapy team? Adds the predefined “how satisfied were you with the service of the radiotherapy team?” question to the survey with the fixed five-point satisfaction answers.
24 sonuçların paylaşımı ve sonuç görüşmesi sürecini nasıl değerlendirirsiniz? how would you rate the process of sharing results and discussing results? Adds the predefined “how would you rate the process of sharing results and discussing results?” question to the survey with the fixed five-point satisfaction answers.
25 şikâyetlerinizin çözüm sürecinden ne ölçüde memnun kaldınız? to what extent were you satisfied with the resolution process of your complaints? Adds the predefined “to what extent were you satisfied with the resolution process of your complaints?” question to the survey with the fixed five-point satisfaction answers.
26 web sitesini kullanma deneyiminizi nasıl değerlendirirsiniz? how would you rate your experience using the website? Adds the predefined “how would you rate your experience using the website?” question to the survey with the fixed five-point satisfaction answers.
27 şikâyetlerinizi iletme ve geri dönüş sürecini nasıl buldunuz? how did you find the process of submitting your complaints and receiving feedback? Adds the predefined “how did you find the process of submitting your complaints and receiving feedback?” question to the survey with the fixed five-point satisfaction answers.
28 hastane içi yönlendirme ve aktarım sürecini nasıl değerlendirirsiniz? how would you rate the in-hospital guidance and transfer process? Adds the predefined “how would you rate the in-hospital guidance and transfer process?” question to the survey with the fixed five-point satisfaction answers.
29 video klinik (uzaktan görüşme) hizmetinden memnun kaldınız mı? were you satisfied with the video clinic (remote consultation) service? Adds the predefined “were you satisfied with the video clinic (remote consultation) service?” question to the survey with the fixed five-point satisfaction answers.
30 check-up içeriği ve kapsamını nasıl değerlendirirsiniz? how would you rate the content and scope of the check-up? Adds the predefined “how would you rate the content and scope of the check-up?” question to the survey with the fixed five-point satisfaction answers.
31 çağrı merkezi ile iletişim deneyiminiz nasıldı? what was your experience communicating with the call center? Adds the predefined “what was your experience communicating with the call center?” question to the survey with the fixed five-point satisfaction answers.
32 randevu ve hizmet zamanlamasını nasıl değerlendirirsiniz? how would you rate the appointment and service scheduling? Adds the predefined “how would you rate the appointment and service scheduling?” question to the survey with the fixed five-point satisfaction answers.
33 radyoloji teknikerinin hizmetinden ne düzeyde memnun kaldınız? to what extent were you satisfied with the service of the radiology technician? Adds the predefined “to what extent were you satisfied with the service of the radiology technician?” question to the survey with the fixed five-point satisfaction answers.

Example

0 — how likely are you to recommend our service to others?
2. create date

2. create date

Parameter identifier: 2 Data type: datetime
Turkish name oluşturma tarihi
English name create date

Description

The Coordinated Universal Time at which the settings record is saved. The record service rewrites this field with the current time for both creation and update requests; therefore, in the current implementation it behaves like the latest save time rather than an immutable original creation time.

Example

2026-10-25T09:45:55
3. update date

3. update date

Parameter identifier: 3 Data type: datetime
Turkish name güncelleme tarihi
English name update date

Description

Defined to store the last update time of the settings record. The line that would write this field is commented out in record code, and the field is not used by the read or survey-generation flow; therefore, it must not be assumed to populate automatically in the current standard flow.

Example

2026-10-25T09:45:55
4. manuel question list

4. manuel question list

Parameter identifier: 4 Data type: list_parameter
Turkish name manuel soru listesi
English name manuel question list

Description

A repeating list that stores questions defined outside the predefined catalog. Each row contains status, identifier, type, multilingual label, and an answer list when required; only active rows enter the payload during survey creation, and if an identifier conflicts with another predefined or manual question, the later entry can replace the earlier one in the question map.

Example

[{ ... }]
5. question status

5. question status

Parameter identifier: 5 Data type: select
Turkish name soru durum
English name question status

Description

Determines whether a manual-question row is included in the survey. An `active` row is processed; for other values the code skips the row directly, so the question and its answers do not appear in the generated survey even if they and order information remain in the settings record.

Options

Value Turkish English Behavior
0 pasif passive Keeps the row in settings but excludes it from the generated survey.
1 aktif active Includes the row in the generated survey.

Example

0 — passive
6. question id

6. question id

Parameter identifier: 6 Data type: text
Turkish name soru id
English name question id

Description

The identifier of the manual question within the survey. Instead of retaining an incoming identifier, the record service regenerates it as `m_0`, `m_1`, and so on from the manual-question counter; survey-preparation code creates a fallback identifier with the same pattern if the field is empty. Because the order list also uses this identifier as its key, changing it affects ordering.

Example

question id-example
7. question type

7. question type

Parameter identifier: 7 Data type: select
Turkish name soru tipi
English name question type

Description

Determines the answer component of a manual question. Current WDM options provide select, int, float, text, textarea, date, and datetime from values 0–6; however, backend mapping interprets value 5 as checkbox, value 6 as date, and schema-absent value 7 as datetime. Therefore, with the current code, choosing WDM `date` produces a checkbox, choosing `datetime` produces a date field, and there is no selectable value that produces a true datetime field.

Options

Value Turkish English Behavior
0 seçenekli select The WDM option is “select”; for values 5 and 6, the backend offset produces the behavior described above.
1 tam sayı int The WDM option is “int”; for values 5 and 6, the backend offset produces the behavior described above.
2 ondalıklı sayı float The WDM option is “float”; for values 5 and 6, the backend offset produces the behavior described above.
3 text text The WDM option is “text”; for values 5 and 6, the backend offset produces the behavior described above.
4 textarea textarea The WDM option is “textarea”; for values 5 and 6, the backend offset produces the behavior described above.
5 tarih date The WDM option is “date”; for values 5 and 6, the backend offset produces the behavior described above.
6 tarih ve saat datetime The WDM option is “datetime”; for values 5 and 6, the backend offset produces the behavior described above.

Example

0 — select
8. question label

8. question label

Parameter identifier: 8 Data type: text
Turkish name soru label
English name question label

Description

The multilingual text of the manual question shown to the user. The record service writes the current interface-language value to the main `val` field and all translations to the `lang` object; because survey-generation code reads the label from `lang`, the question text can be missing in a language whose translation is absent.

Example

question label-example
9. answer list

9. answer list

Parameter identifier: 9 Data type: list_parameter
Turkish name yanıt listesi
English name answer list

Description

A repeating list that stores possible answers for a select-type manual question. The backend processes this list only when the question type resolves to `select`; even if the list contains data for int, float, text, textarea, date, or datetime types, answer options are not added to the payload.

Example

[{ ... }]
10. answer status

10. answer status

Parameter identifier: 10 Data type: select
Turkish name yanıt durum
English name answer status

Description

Determines availability of a manual answer option in the survey. Only `active` answers are added to the select question’s `answers` array; a passive answer may remain in the record but is not shown to the user as an option.

Options

Value Turkish English Behavior
0 pasif passive Keeps the row in settings but excludes it from the generated survey.
1 aktif active Includes the row in the generated survey.

Example

0 — passive
11. answer id

11. answer id

Parameter identifier: 11 Data type: text
Turkish name yanıt id
English name answer id

Description

The identifier of the manual answer within its question. The record service renumbers answers as `0`, `1`, `2`, and so on according to their zero-based list index; therefore, reordering answers can also change their identifiers and they must not be treated as persistent external business identifiers.

Example

answer id-example
12. answer label

12. answer label

Parameter identifier: 12 Data type: text
Turkish name yanıt label
English name answer label

Description

The multilingual text of a manual answer option shown to the user. The main value is saved from the active interface language and translations are saved in the `lang` object; because the survey payload uses the `lang` object, a value should be supplied for every target language.

Example

answer label-example
13. add general opinion text

13. add general opinion text

Parameter identifier: 13 Data type: select
Turkish name genel düşünce metni eklensin mi
English name add general opinion text

Description

Determines whether a free-text general-opinion question is appended to the survey. When `yes` is selected, the backend appends a fixed Turkish and English question with identifier `35` and type `textarea` to the end of the payload; because it is added after ordering rather than through the order list, it always appears last.

Options

Value Turkish English Behavior
0 hayır no Does not add a general-opinion question.
1 evet yes Appends the fixed general-opinion textarea question to the end of the survey.

Example

0 — no
14. order list

14. order list

Parameter identifier: 14 Data type: text
Turkish name sıra listesi
English name order list

Description

A JSON object that maps predefined and manual question identifiers to their display order, for example `{"0":"1","m_0":"2"}`. The record service builds this object from each question’s `order` value, survey-generation code converts values to integers, sorts ascending, and includes only identifiers present in the question map. If JSON is invalid, the order list is treated as empty and questions are used in their insertion order.

Example

{"0":"1","m_0":"2"}
About WDC Campaign / Lead Form
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Lead Form

Tracks resolution of a digital-advertising lead through phone or customer identifier and its conversion into a customer journey.

Lead-tracking flow

When a direct customer identifier exists, customer, journey, and operation creation starts. With only a phone number, the campaign’s phone-lookup API code runs; if no identifier is found the record waits, and if one is found or follow-up time expires the record completes.

Code findings: The method call in daily rechecking does not match the current signature. In addition, the multiple-phone-match loop passes the old customer identifier to the central method instead of the newly found identifier. These two paths must be fixed before automatic follow-up is used in production.
0. status

0. status

Parameter identifier: 0 Data type: select
Turkish name durum
English name status

Description

The activity state of the lead-tracking record. A tracking record created through the phone flow is written as active; the timer is intended to reevaluate only records whose status is `active` and customer status is `wait`. If passive is selected, the record does not satisfy this processing condition.

Options

Value Turkish English Behavior
0 pasif passive Excludes the record from the active tracking condition.
1 aktif active Makes the record eligible for the active tracking condition.

Example

0 — passive
1. campaign name

1. campaign name

Parameter identifier: 1 Data type: text
Turkish name kampanya adı
English name campaign name

Description

Defined to store the display name of the campaign associated with the lead. The inspected lead tracking create/update method does not write this field, and the timer does not read the campaign name from it; therefore, it must not be assumed to populate automatically in the standard phone-tracking flow.

Example

campaign name-example
2. customer status

2. customer status

Parameter identifier: 2 Data type: select
Turkish name müşteri durum
English name customer status

Description

Specifies whether a source customer identifier has been found from the phone number and whether follow-up should continue. `wait` is written when no identifier is found; `completed` is written when one or more identifiers are found, processing completes with a direct customer identifier, or the final check of the maximum follow-up period is reached. A completed record must not be checked again.

Options

Value Turkish English Behavior
0 beklemede wait Indicates that the customer was not found and daily follow-up should continue.
1 tamamlandı completed Indicates that the customer was found or the final check occurred and follow-up should end.

Example

0 — wait
3. campaign client id

3. campaign client id

Parameter identifier: 3 Data type: text
Turkish name kampanya client id
English name campaign client id

Description

The client identifier of the campaign that owns the lead. The tracking record is stored under the campaign with this identifier, and the timer query selects only records with the same campaign identifier; an incorrect value can cause the lead to be processed with another campaign’s settings or not found.

Example

campaign client id-example
4. operation date

4. operation date

Parameter identifier: 4 Data type: datetime
Turkish name işlem tarihi
English name operation date

Description

The date and time at which the lead event occurred. If the API request supplies an operation date it is used; otherwise, current Coordinated Universal Time is written. The correct date is important because reacceptance eligibility and the end of the maximum customer-success follow-up period are calculated from this time context.

Example

2026-10-25T09:45:55
5. last check date

5. last check date

Parameter identifier: 5 Data type: datetime
Turkish name son kontrol tarihi
English name last check date

Description

The Coordinated Universal Time at which phone-to-customer matching was last attempted. It is refreshed with the current time whenever the tracking record is written; the timer is intended to add one day to this date and check the record again after the current time passes that threshold. The current timer call does not match the current method signature, so automatic retry requires a code fix.

Example

2026-10-25T09:45:55
6. institution code

6. institution code

Parameter identifier: 6 Data type: text
Turkish name kurum kodu
English name institution code

Description

The source code of the institution associated with the lead. It is carried from the request to the tracking record, then to the institution code of the customer journey and the created channel operation; therefore, the same context is preserved for institution-based reporting and success matching.

Example

institution code-example
7. website link

7. website link

Parameter identifier: 7 Data type: text
Turkish name website linki
English name website link

Description

The direct link of the web page from which the lead originated. According to the code comment it is stored as a URL and preserved during tracking; however, the line that would write it into the customer journey operation is commented out, so it is not transferred to the operation layer in the standard flow.

Example

website link-example
8. utm source

8. utm source

Parameter identifier: 8 Data type: text
Turkish name utm kaynağı
English name utm source

Description

The UTM source value that identifies the acquisition source of the lead, such as Google, Facebook, or Instagram. It is preserved in the tracking record and copied to the operation’s UTM source field when a customer identifier is resolved and a channel operation is created, allowing digital-advertising success to be distinguished by source.

Example

utm source-example
9. phone number

9. phone number

Parameter identifier: 9 Data type: text
Turkish name telefon no
English name phone number

Description

The phone number used to search for the customer in the source system. When the request does not contain a customer identifier, this field becomes the required alternative; the campaign’s customer-list-by-phone API code can use it to return one or more customer identifiers. The tracking-record client identifier is also based on a combination of campaign identifier and phone number.

Example

+905321234567
10. integrated system customer id

10. integrated system customer id

Parameter identifier: 10 Data type: text
Turkish name entegre sistem müşteri id
English name integrated system customer id

Description

The customer or record identifier of the lead in an external or integrated system. It is received from the request query, stored in the tracking record, and transferred to the channel operation’s integrated-system identifier when the customer identifier is resolved; it is different from parameter 14, the platform customer identifier.

Example

integrated system customer id-example
11. create date

11. create date

Parameter identifier: 11 Data type: datetime
Turkish name oluşturma tarihi
English name create date

Description

Defined to store the time at which the lead-tracking record was first created. The inspected `f_updateProjectLeadFormLogWdmr` method does not write this field or use it for follow-up scheduling; because it may remain empty in the standard flow, it must not be used instead of operation date or last check date.

Example

2026-10-25T09:45:55
12. update date

12. update date

Parameter identifier: 12 Data type: datetime
Turkish name güncelleme tarihi
English name update date

Description

Defined to store the last data-update time of the lead-tracking record. The inspected record and timer code does not write this field; because actual check updates are tracked through parameter 5, last check date, this field must not be assumed to populate automatically.

Example

2026-10-25T09:45:55
13. country phone code

13. country phone code

Parameter identifier: 13 Data type: text
Turkish name ülke telefon kodu
English name country phone code

Description

The country calling code of the phone number. It is received from the lead request and preserved when the tracking record is rewritten; customer lookup API code can use it to normalize the number by country or query the correct source, but it is not a complete phone number by itself.

Example

country phone code-example
14. customer id

14. customer id

Parameter identifier: 14 Data type: text
Turkish name müşteri id
English name customer id

Description

The platform customer identifier found by phone matching or supplied directly in the API request. When a direct value exists, customer, journey, and operation creation starts immediately; if no value is found in the phone flow, the record remains waiting. The inspected multiple-phone-result loop passes the old `customer_id` variable to the central method instead of the found `new_customer_id`, so this path must be verified to carry the correct identifier and the code must be fixed.

Example

customer id-example
About WDC Campaign / Channel Design
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Channel Design

Defines the permission, institution, and nationality conditions under which a journey proceeds through ordered channel steps.

Selection and step flow

Only active designs are evaluated. When all required permissions, institution filter, and nationality filter are eligible together, the channel step corresponding to the number of previous operations is selected. Next-step time is calculated by adding an hour or day period to the previous operation date.

Code findings: Excluded institution/nationality lists are lost during save, HTML message type cannot be selected because of a value mismatch, and WhatsApp/language fields are not processed in the current step save/read flow. Timestamps are also mistakenly written to top-level fields 26/27 instead of 23/24.
0. status

0. status

Parameter identifier: 0 Data type: select
Turkish name durum
English name status

Description

The availability state of the channel design. Eligible-channel selection evaluates only active designs; a passive design is not selected for a journey even when permissions, institution, nationality, and channel steps are configured.

Options

Value Turkish English Behavior
0 pasif passive Excludes the design from eligible-channel selection.
1 aktif active Makes the design available to eligible-channel selection.

Example

0 — passive
1. channel permission type

1. channel permission type

Parameter identifier: 1 Data type: select
Turkish name kanal izin tipi
English name channel permission type

Description

Determines whether customer permissions are checked for channel eligibility. When checking is disabled, the permission condition is accepted directly and dependent permission fields are removed during save; when enabled, every permission selected in parameter 2 must match its own list of accepted states.

Options

Value Turkish English Behavior
0 izinleri konrol etme dont check permissions Interprets the field as “dont check permissions”; the related filter or step operates according to this value.
1 izinleri konrol et check permissions Interprets the field as “check permissions”; the related filter or step operates according to this value.

Example

0 — dont check permissions
2. required permissions

2. required permissions

Parameter identifier: 2 Data type: checkbox
Turkish name zorunlu izinler
English name required permissions

Description

The permission categories that must be satisfied together before the channel can be used. The algorithm checks selected permissions in sequence and rejects the design when any permission is not present in its corresponding accepted-state list in parameters 3–7; therefore, the logic is “all selected,” not “any selected.”

Options

Value Turkish English Behavior
0 kanuni veri işleme legal data processing Makes the “legal data processing” category required; the channel is rejected if its accepted-state list does not match.
1 kanuni iletişim legal contact Makes the “legal contact” category required; the channel is rejected if its accepted-state list does not match.
2 sms sms Makes the “sms” category required; the channel is rejected if its accepted-state list does not match.
3 mail mail Makes the “mail” category required; the channel is rejected if its accepted-state list does not match.
4 telefon ile arama phone call Makes the “phone call” category required; the channel is rejected if its accepted-state list does not match.

Example

0 — legal data processing
3. legal data processing permission

3. legal data processing permission

Parameter identifier: 3 Data type: checkbox
Turkish name legal veri işleme izni
English name legal data processing permission

Description

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “legal data processing permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; the related filter or step operates according to this value.
1 onaylandı approved Interprets the field as “approved”; the related filter or step operates according to this value.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 kayıt yok missing Interprets the field as “missing”; the related filter or step operates according to this value.

Example

0 — rejected
4. legal communication permission

4. legal communication permission

Parameter identifier: 4 Data type: checkbox
Turkish name legal iletişim izni
English name legal communication permission

Description

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “legal communication permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; the related filter or step operates according to this value.
1 onaylandı approved Interprets the field as “approved”; the related filter or step operates according to this value.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 kayıt yok missing Interprets the field as “missing”; the related filter or step operates according to this value.

Example

0 — rejected
5. sms permission

5. sms permission

Parameter identifier: 5 Data type: checkbox
Turkish name sms izni
English name sms permission

Description

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “sms permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; the related filter or step operates according to this value.
1 onaylandı approved Interprets the field as “approved”; the related filter or step operates according to this value.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 kayıt yok missing Interprets the field as “missing”; the related filter or step operates according to this value.

Example

0 — rejected
6. email permission

6. email permission

Parameter identifier: 6 Data type: checkbox
Turkish name mail izni
English name email permission

Description

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “email permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; the related filter or step operates according to this value.
1 onaylandı approved Interprets the field as “approved”; the related filter or step operates according to this value.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 kayıt yok missing Interprets the field as “missing”; the related filter or step operates according to this value.

Example

0 — rejected
7. phone call permission

7. phone call permission

Parameter identifier: 7 Data type: checkbox
Turkish name telefon ile arama izni
English name phone call permission

Description

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “phone call permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

Options

Value Turkish English Behavior
0 reddedildi rejected Interprets the field as “rejected”; the related filter or step operates according to this value.
1 onaylandı approved Interprets the field as “approved”; the related filter or step operates according to this value.
2 onay bekliyor awaiting approval Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 kayıt yok missing Interprets the field as “missing”; the related filter or step operates according to this value.

Example

0 — rejected
8. channel institution type

8. channel institution type

Parameter identifier: 8 Data type: select
Turkish name kanal kurum tipi
English name channel institution type

Description

Determines the scope of the institution filter. No code comparison is made for all institutions; for only selected institutions the customer institution code must be in the list, while in exclude mode it must not be in the list. However, the record service persists parameter 9 only for value 1, so exclude mode loses its selections in the current form save and can effectively accept all institutions with an empty exclusion list.

Options

Value Turkish English Behavior
0 tüm kurumlar all institutions Interprets the field as “all institutions”; the related filter or step operates according to this value.
1 sadece seçili kurumlar only selected institutions Interprets the field as “only selected institutions”; the related filter or step operates according to this value.
2 seçili kurumlar hariç except selected institutions Interprets the field as “except selected institutions”; the related filter or step operates according to this value.

Example

0 — all institutions
9. institution code list

9. institution code list

Parameter identifier: 9 Data type: textarea
Turkish name kurum kodu listesi
English name institution code list

Description

The comma-separated institution codes used by the institution filter. The reader splits text on commas, trims whitespace, and performs exact matching against customer `institution_code`; source codes rather than names must be entered. The current record endpoint attempts to persist this field in checkbox form and only for “only selected institutions,” so textarea schema behavior and exclude mode must be verified together.

Example

institution code list-example
10. channel nationality type

10. channel nationality type

Parameter identifier: 10 Data type: select
Turkish name kanal uyruk tipi
English name channel nationality type

Description

Determines the scope of the nationality filter. No match is required for all nations; in only-selected mode the journey’s normalized country name must be in the list, while in exclude mode it must not be in the list. The record service persists parameter 11 only for value 1, so exclude mode loses its selections in the current form flow.

Options

Value Turkish English Behavior
0 tüm uyruklar all nations Interprets the field as “all nations”; the related filter or step operates according to this value.
1 sadece seçili uyruklar only selected nations Interprets the field as “only selected nations”; the related filter or step operates according to this value.
2 seçili uyruklar hariç except selected nations Interprets the field as “except selected nations”; the related filter or step operates according to this value.

Example

0 — all nations
11. nationality selection

11. nationality selection

Parameter identifier: 11 Data type: checkbox
Turkish name uyruk seçimi
English name nationality selection

Description

The multiple selection of country names used by the nationality filter. The backend converts each WDM option value into an underscore-normalized English country name and compares it with journey `nation_name`. Because journey creation currently has a country-name field bug that can leave this value empty, an only-selected nationality filter can unexpectedly reject the channel.

Options

Value Turkish English Behavior
0 batı sahra western sahara Adds “western sahara” to the nationality-filter list.
1 birleşik devletler'e ait uzak küçük adalar united states outlying minor islands Adds “united states outlying minor islands” to the nationality-filter list.
2 aland adaları aland islands Adds “aland islands” to the nationality-filter list.
3 antarktika antarctica Adds “antarctica” to the nationality-filter list.
4 somali somalia Adds “somalia” to the nationality-filter list.
5 cezayir algeria Adds “algeria” to the nationality-filter list.
6 tacikistan tajikistan Adds “tajikistan” to the nationality-filter list.
7 sudan sudan Adds “sudan” to the nationality-filter list.
8 seyşel adaları seychelles Adds “seychelles” to the nationality-filter list.
9 bouvet adası bouvet island Adds “bouvet island” to the nationality-filter list.
10 christmas adası christmas island Adds “christmas island” to the nationality-filter list.
11 meksika mexico Adds “mexico” to the nationality-filter list.
12 martinik martinique Adds “martinique” to the nationality-filter list.
13 marşal adaları marshall islands Adds “marshall islands” to the nationality-filter list.
14 mauritius adası mauritius island Adds “mauritius island” to the nationality-filter list.
15 moldovya moldova Adds “moldova” to the nationality-filter list.
16 moğolistan mongolia Adds “mongolia” to the nationality-filter list.
17 mısır egypt Adds “egypt” to the nationality-filter list.
18 mikronezya micronesia Adds “micronesia” to the nationality-filter list.
19 montserrat montserrat Adds “montserrat” to the nationality-filter list.
20 monako monaco Adds “monaco” to the nationality-filter list.
21 sırbistan karadağ serbia montenegro Adds “serbia montenegro” to the nationality-filter list.
22 birl. arap emirlikleri united united arab emirates Adds “united united arab emirates” to the nationality-filter list.
23 bolivya bolivia Adds “bolivia” to the nationality-filter list.
24 bosna hersek bosnia and herzegovina Adds “bosnia and herzegovina” to the nationality-filter list.
25 botsvana botswana Adds “botswana” to the nationality-filter list.
26 belçika belgium Adds “belgium” to the nationality-filter list.
27 belize belize Adds “belize” to the nationality-filter list.
28 benin benin Adds “benin” to the nationality-filter list.
29 bermuda bermuda Adds “bermuda” to the nationality-filter list.
30 ruanda rwanda Adds “rwanda” to the nationality-filter list.
31 brezilya brazil Adds “brazil” to the nationality-filter list.
32 britanya virjin adaları british virgin islands Adds “british virgin islands” to the nationality-filter list.
33 rusya russia Adds “russia” to the nationality-filter list.
34 amerikan samoa american samoa Adds “american samoa” to the nationality-filter list.
35 arjantin argentina Adds “argentina” to the nationality-filter list.
36 cocos (keeling) adaları cocos (keeling) islands Adds “cocos (keeling) islands” to the nationality-filter list.
37 lübnan lebanon Adds “lebanon” to the nationality-filter list.
38 lüksemburg luxembourg Adds “luxembourg” to the nationality-filter list.
39 macaristan hungary Adds “hungary” to the nationality-filter list.
40 madagaskar madagascar Adds “madagascar” to the nationality-filter list.
41 makau macau Adds “macau” to the nationality-filter list.
42 makedonya macedonia Adds “macedonia” to the nationality-filter list.
43 malavi malawi Adds “malawi” to the nationality-filter list.
44 maldivler maldives Adds “maldives” to the nationality-filter list.
45 malezya malaysia Adds “malaysia” to the nationality-filter list.
46 mali mali Adds “mali” to the nationality-filter list.
47 malta malta Adds “malta” to the nationality-filter list.
48 singapur singapore Adds “singapore” to the nationality-filter list.
49 filipinler philippines Adds “philippines” to the nationality-filter list.
50 fildişi sahilleri ivory coast Adds “ivory coast” to the nationality-filter list.
51 faroe adaları faroe islands Adds “faroe islands” to the nationality-filter list.
52 etiyopya ethiopia Adds “ethiopia” to the nationality-filter list.
53 fiji fiji Adds “fiji” to the nationality-filter list.
54 fas morocco Adds “morocco” to the nationality-filter list.
55 eritre eritrea Adds “eritrea” to the nationality-filter list.
56 endonezya indonesia Adds “indonesia” to the nationality-filter list.
57 estonya estonia Adds “estonia” to the nationality-filter list.
58 ermenistan armenia Adds “armenia” to the nationality-filter list.
59 senegal senegal Adds “senegal” to the nationality-filter list.
60 yeni kaledonya new caledonia Adds “new caledonia” to the nationality-filter list.
61 wallis ve futuna adaları wallis and futuna islands Adds “wallis and futuna islands” to the nationality-filter list.
62 tanzanya tanzania Adds “tanzania” to the nationality-filter list.
63 yemen yemen Adds “yemen” to the nationality-filter list.
64 vanuatu vanuatu Adds “vanuatu” to the nationality-filter list.
65 vietnam vietnam Adds “vietnam” to the nationality-filter list.
66 şili chile Adds “chile” to the nationality-filter list.
67 umman oman Adds “oman” to the nationality-filter list.
68 ukrayna ukraine Adds “ukraine” to the nationality-filter list.
69 ürdün jordan Adds “jordan” to the nationality-filter list.
70 uruguay uruguay Adds “uruguay” to the nationality-filter list.
71 liberya liberia Adds “liberia” to the nationality-filter list.
72 lesoto lesotho Adds “lesotho” to the nationality-filter list.
73 irlanda ireland Adds “ireland” to the nationality-filter list.
74 libya libya Adds “libya” to the nationality-filter list.
75 kuveyt kuwait Adds “kuwait” to the nationality-filter list.
76 latvia latvia Adds “latvia” to the nationality-filter list.
77 laos laos Adds “laos” to the nationality-filter list.
78 hollanda netherlands Adds “netherlands” to the nationality-filter list.
79 hollanda antil adaları netherlands antilles Adds “netherlands antilles” to the nationality-filter list.
80 hırvatistan croatia Adds “croatia” to the nationality-filter list.
81 hindistan india Adds “india” to the nationality-filter list.
82 irak iraq Adds “iraq” to the nationality-filter list.
83 litvanya lithuania Adds “lithuania” to the nationality-filter list.
84 honduras honduras Adds “honduras” to the nationality-filter list.
85 hong kong hong kong Adds “hong kong” to the nationality-filter list.
86 tokelau tokelau Adds “tokelau” to the nationality-filter list.
87 virjin adaları (a.b.d.) virgin islands (u.s.) Adds “virgin islands (u.s.)” to the nationality-filter list.
88 iran iran Adds “iran” to the nationality-filter list.
89 holy see (vatikan şehir devleti) holy see (vatican city state) Adds “holy see (vatican city state)” to the nationality-filter list.
90 almanya germany Adds “germany” to the nationality-filter list.
91 svaziland swaziland Adds “swaziland” to the nationality-filter list.
92 anguilla anguilla Adds “anguilla” to the nationality-filter list.
93 sırbistan serbia Adds “serbia” to the nationality-filter list.
94 küba cuba Adds “cuba” to the nationality-filter list.
95 güney sudan south sudan Adds “south sudan” to the nationality-filter list.
96 batum-gürcistan batumi-georgia Adds “batumi-georgia” to the nationality-filter list.
97 heard adası ve mcdonald adaları heard island and mcdonald islands Adds “heard island and mcdonald islands” to the nationality-filter list.
98 santa helena santa helena Adds “santa helena” to the nationality-filter list.
99 san marino san marino Adds “san marino” to the nationality-filter list.
100 kongo (brazavil) congo (brazzaville) Adds “congo (brazzaville)” to the nationality-filter list.
101 kosta rika costa rica Adds “costa rica” to the nationality-filter list.
102 saint martin (fransız tarafı) saint martin (french side) Adds “saint martin (french side)” to the nationality-filter list.
103 saint barthelemy saint barthelemy Adds “saint barthelemy” to the nationality-filter list.
104 samoa samoa Adds “samoa” to the nationality-filter list.
105 saint pierre ve miquelon saint pierre and miquelon Adds “saint pierre and miquelon” to the nationality-filter list.
106 kazakistan kazakhstan Adds “kazakhstan” to the nationality-filter list.
107 kenya kenya Adds “kenya” to the nationality-filter list.
108 kanada canada Adds “canada” to the nationality-filter list.
109 katar qatar Adds “qatar” to the nationality-filter list.
110 kolombiya colombia Adds “colombia” to the nationality-filter list.
111 kongo cumhuriyeti republic of the congo Adds “republic of the congo” to the nationality-filter list.
112 kıbrıs rum kesimi cyprus Adds “cyprus” to the nationality-filter list.
113 kırgızistan kyrgyzstan Adds “kyrgyzstan” to the nationality-filter list.
114 çad chad Adds “chad” to the nationality-filter list.
115 cook adaları cook islands Adds “cook islands” to the nationality-filter list.
116 burundi burundi Adds “burundi” to the nationality-filter list.
117 burkina faso burkina faso Adds “burkina faso” to the nationality-filter list.
118 bulgaristan bulgaria Adds “bulgaria” to the nationality-filter list.
119 brunei brunei Adds “brunei” to the nationality-filter list.
120 cebelitarık gibraltar Adds “gibraltar” to the nationality-filter list.
121 keymen adaları keymen islands Adds “keymen islands” to the nationality-filter list.
122 verde burnu cape verde Adds “cape verde” to the nationality-filter list.
123 butan bhutan Adds “bhutan” to the nationality-filter list.
124 sao tome ve principe sao tome and principe Adds “sao tome and principe” to the nationality-filter list.
125 tuvalu tuvalu Adds “tuvalu” to the nationality-filter list.
126 zimbabve zimbabwe Adds “zimbabwe” to the nationality-filter list.
127 guernsey guernsey Adds “guernsey” to the nationality-filter list.
128 suudi arabistan saudi arabia Adds “saudi arabia” to the nationality-filter list.
129 filistin özerk bölgesi self-governing state of palestine Adds “self-governing state of palestine” to the nationality-filter list.
130 finlandiya finland Adds “finland” to the nationality-filter list.
131 fransa france Adds “france” to the nationality-filter list.
132 fransız guyanası french guiana Adds “french guiana” to the nationality-filter list.
133 fransız polonezyası french polynesia Adds “french polynesia” to the nationality-filter list.
134 gabon gabon Adds “gabon” to the nationality-filter list.
135 galler (birleşik krallık) wales (uk) Adds “wales (uk)” to the nationality-filter list.
136 gambiya gambia Adds “gambia” to the nationality-filter list.
137 gana ghana Adds “ghana” to the nationality-filter list.
138 gine guinea Adds “guinea” to the nationality-filter list.
139 suriye syria Adds “syria” to the nationality-filter list.
140 surinam suriname Adds “suriname” to the nationality-filter list.
141 saint vincent saint vincent Adds “saint vincent” to the nationality-filter list.
142 saint lucia saint lucia Adds “saint lucia” to the nationality-filter list.
143 saint kitts ve nevis saint kitts and nevis Adds “saint kitts and nevis” to the nationality-filter list.
144 sri lanka sri lanka Adds “sri lanka” to the nationality-filter list.
145 yunanistan greece Adds “greece” to the nationality-filter list.
146 gine-bissau guinea-bissau Adds “guinea-bissau” to the nationality-filter list.
147 tayvan taiwan Adds “taiwan” to the nationality-filter list.
148 sierra leone sierra leone Adds “sierra leone” to the nationality-filter list.
149 togo togo Adds “togo” to the nationality-filter list.
150 tongo tongo Adds “tongo” to the nationality-filter list.
151 tayland thailand Adds “thailand” to the nationality-filter list.
152 afganistan afghanistan Adds “afghanistan” to the nationality-filter list.
153 saipan saipan Adds “saipan” to the nationality-filter list.
154 türkiye turkey Adds “turkey” to the nationality-filter list.
155 trinidat ve tobago trinidad and tobago tobago Adds “trinidad and tobago tobago” to the nationality-filter list.
156 angola angola Adds “angola” to the nationality-filter list.
157 türk ve kaikos adaları turks and caicos islands Adds “turks and caicos islands” to the nationality-filter list.
158 türkmenistan turkmenistan Adds “turkmenistan” to the nationality-filter list.
159 uganda uganda Adds “uganda” to the nationality-filter list.
160 yeni zelanda new zealand Adds “new zealand” to the nationality-filter list.
161 venezuella venezuella Adds “venezuella” to the nationality-filter list.
162 fransa güney bölgeleri french southern territories Adds “french southern territories” to the nationality-filter list.
163 tunus tunisia Adds “tunisia” to the nationality-filter list.
164 kamerun cameroon Adds “cameroon” to the nationality-filter list.
165 kamboçya cambodia Adds “cambodia” to the nationality-filter list.
166 slovak cumhuriyeti slovak republic Adds “slovak republic” to the nationality-filter list.
167 slovenya slovenia Adds “slovenia” to the nationality-filter list.
168 jersey jersey Adds “jersey” to the nationality-filter list.
169 ingiliz hint okyanusu bölgesi british indian ocean territory Adds “british indian ocean territory” to the nationality-filter list.
170 israil israel Adds “israel” to the nationality-filter list.
171 ispanya spain Adds “spain” to the nationality-filter list.
172 isviçre switzerland Adds “switzerland” to the nationality-filter list.
173 isveç sweden Adds “sweden” to the nationality-filter list.
174 izlanda iceland Adds “iceland” to the nationality-filter list.
175 italya italy Adds “italy” to the nationality-filter list.
176 japonya japan Adds “japan” to the nationality-filter list.
177 jameyka jameika Adds “jameika” to the nationality-filter list.
178 avusturalya australia Adds “australia” to the nationality-filter list.
179 aruba aruba Adds “aruba” to the nationality-filter list.
180 azerbaycan azerbaijan Adds “azerbaijan” to the nationality-filter list.
181 avusturya austria Adds “austria” to the nationality-filter list.
182 bahreyn bahrain Adds “bahrain” to the nationality-filter list.
183 bahamalar bahamas Adds “bahamas” to the nationality-filter list.
184 barbados barbados Adds “barbados” to the nationality-filter list.
185 bangladeş bangladesh Adds “bangladesh” to the nationality-filter list.
186 belarus (beyaz rusya) belarus (belarus) Adds “belarus (belarus)” to the nationality-filter list.
187 barbuda / antigua barbuda/antigua Adds “barbuda/antigua” to the nationality-filter list.
188 lihtenştayn liechtenstein Adds “liechtenstein” to the nationality-filter list.
189 svalbard svalbard Adds “svalbard” to the nationality-filter list.
190 zambiya zambia Adds “zambia” to the nationality-filter list.
191 panama panama Adds “panama” to the nationality-filter list.
192 palau palau Adds “palau” to the nationality-filter list.
193 paraguay paraguay Adds “paraguay” to the nationality-filter list.
194 papua yeni gine papua new guinea Adds “papua new guinea” to the nationality-filter list.
195 polonya poland Adds “poland” to the nationality-filter list.
196 peru peru Adds “peru” to the nationality-filter list.
197 porto riko puerto rico Adds “puerto rico” to the nationality-filter list.
198 portekiz portugal Adds “portugal” to the nationality-filter list.
199 romanya romania Adds “romania” to the nationality-filter list.
200 reunion adası reunion island Adds “reunion island” to the nationality-filter list.
201 orta afrika cumhuriyeti central africa republic of Adds “central africa republic of” to the nationality-filter list.
202 pitcairn pitcairn Adds “pitcairn” to the nationality-filter list.
203 myanmar myanmar Adds “myanmar” to the nationality-filter list.
204 nauru nauru Adds “nauru” to the nationality-filter list.
205 niu niu Adds “niu” to the nationality-filter list.
206 norfolk adası norfolk island Adds “norfolk island” to the nationality-filter list.
207 kiribati kiribati Adds “kiribati” to the nationality-filter list.
208 komor comoros Adds “comoros” to the nationality-filter list.
209 kore demokratik halk cumhuriyeti democratic people's republic of korea Adds “democratic people's republic of korea” to the nationality-filter list.
210 mayotte mayotte Adds “mayotte” to the nationality-filter list.
211 güney gürcistan ve güney sandwich adaları south georgia and the south sandwich islands Adds “south georgia and the south sandwich islands” to the nationality-filter list.
212 ekvator ginesi equatorial guinea Adds “equatorial guinea” to the nationality-filter list.
213 el salvador el salvador Adds “el salvador” to the nationality-filter list.
214 dominika dominica Adds “dominica” to the nationality-filter list.
215 ekvator ecuador Adds “ecuador” to the nationality-filter list.
216 doğu timor east timor Adds “east timor” to the nationality-filter list.
217 dominik cumhuriyeti dominican republic Adds “dominican republic” to the nationality-filter list.
218 danimarka denmark Adds “denmark” to the nationality-filter list.
219 djibouti djibouti Adds “djibouti” to the nationality-filter list.
220 çek cumhuriyeti czech republic Adds “czech republic” to the nationality-filter list.
221 çin china Adds “china” to the nationality-filter list.
222 a.b.d. united states of america Adds “united states of america” to the nationality-filter list.
223 andorra andorra Adds “andorra” to the nationality-filter list.
224 arnavutluk albania Adds “albania” to the nationality-filter list.
225 nikaragua nicaragua Adds “nicaragua” to the nationality-filter list.
226 norveç norway Adds “norway” to the nationality-filter list.
227 nijer niger Adds “niger” to the nationality-filter list.
228 nijerya nigeria Adds “nigeria” to the nationality-filter list.
229 namibya namibia Adds “namibia” to the nationality-filter list.
230 nepal nepal Adds “nepal” to the nationality-filter list.
231 moritanya mauritania Adds “mauritania” to the nationality-filter list.
232 mozambik mozambique Adds “mozambique” to the nationality-filter list.
233 ingiltere united kingdom Adds “united kingdom” to the nationality-filter list.
234 kosova kosovo Adds “kosovo” to the nationality-filter list.
235 özbekistan uzbekistan Adds “uzbekistan” to the nationality-filter list.
236 pakistan pakistan Adds “pakistan” to the nationality-filter list.
237 güney kore south korea Adds “south korea” to the nationality-filter list.
238 güney afrika south africa Adds “south africa” to the nationality-filter list.
239 guyana guyana Adds “guyana” to the nationality-filter list.
240 guatemala guatemala Adds “guatemala” to the nationality-filter list.
241 guam guam Adds “guam” to the nationality-filter list.
242 guadelup guadelup Adds “guadelup” to the nationality-filter list.
243 grönland greenland Adds “greenland” to the nationality-filter list.
244 grenada grenada Adds “grenada” to the nationality-filter list.
245 haiti haiti Adds “haiti” to the nationality-filter list.
246 gürcistan georgia Adds “georgia” to the nationality-filter list.
247 solomon adaları solomon islands Adds “solomon islands” to the nationality-filter list.
248 isle of man isle of man Adds “isle of man” to the nationality-filter list.
249 karadağ montenegro Adds “montenegro” to the nationality-filter list.
250 kuzey kıbrıs türk cumhuriyeti turkish republic of northern cyprus Adds “turkish republic of northern cyprus” to the nationality-filter list.

Example

0 — western sahara
12. channel step

12. channel step

Parameter identifier: 12 Data type: list_parameter
Turkish name kanal adımı
English name channel step

Description

A repeating list that stores the ordered delivery steps of the channel design. The eligible step index is calculated as the number of operations already created in the journey; when all steps have been used, the design is no longer eligible. Each row carries channel type, waiting duration, message, and provider API settings together.

Example

[{ ... }]
13. channel type

13. channel type

Parameter identifier: 13 Data type: select
Turkish name kanal tipi
English name channel type

Description

Determines whether the step uses SMS, push notification, IVR, email, or phone call. The selection determines target contact information, context passed to provider code, and channel type written to the operation; the journey may be made passive if required contact information is unavailable.

Options

Value Turkish English Behavior
0 sms sms Interprets the field as “sms”; the related filter or step operates according to this value.
1 mobil bildirim push notification Interprets the field as “push notification”; the related filter or step operates according to this value.
2 ivr ivr Interprets the field as “ivr”; the related filter or step operates according to this value.
3 mail mail Interprets the field as “mail”; the related filter or step operates according to this value.
4 telefon ile arama phone call Interprets the field as “phone call”; the related filter or step operates according to this value.

Example

0 — sms
15. next channel step transition time type

15. next channel step transition time type

Parameter identifier: 15 Data type: select
Turkish name bir sonraki kanal adımı geçişi süre tipi
English name next channel step transition time type

Description

Specifies whether transition time after the previous step is measured in hours or days. Agenda calculation adds parameter 16 to the previous operation date using the selected unit; an incorrect unit schedules the next channel earlier or later than intended.

Options

Value Turkish English Behavior
0 saat hour Interprets the field as “hour”; the related filter or step operates according to this value.
1 gün day Interprets the field as “day”; the related filter or step operates according to this value.

Example

0 — hour
16. next channel step transition time period

16. next channel step transition time period

Parameter identifier: 16 Data type: integer
Turkish name bir sonraki kanal adımı geçişi süre peryodu
English name next channel step transition time period

Description

The integer duration to wait before moving to the next channel step. It is added to the previous operation date as hours or days according to parameter 15; if empty or not convertible to an integer, no usable transition period is available for calculation.

Example

24
17. message header (email subject)

17. message header (email subject)

Parameter identifier: 17 Data type: text
Turkish name mesaj başlığı (mail konusu)
English name message header (email subject)

Description

The message header defined primarily for use as the subject line of an email channel. It is read into channel-step configuration and provides context usable by provider API code; for other channel types its meaning depends on provider implementation.

Example

message header (email subject)-example
18. message content type

18. message content type

Parameter identifier: 18 Data type: select
Turkish name mesaj içerik tipi
English name message content type

Description

Selects whether the step message is plain text or HTML. The record service removes the unused content field according to the selection. The reader stores HTML selection as `html`, while channel selection expects `html_message`, so HTML content is not assigned as the eligible message in the current code; the plain-text path works.

Options

Value Turkish English Behavior
0 düz metin plain text Interprets the field as “plain text”; the related filter or step operates according to this value.
1 html html Interprets the field as “html”; the related filter or step operates according to this value.

Example

0 — plain text
19. html message

19. html message

Parameter identifier: 19 Data type: html_editor
Turkish name html mesajı
English name html message

Description

The rich content intended for delivery when HTML message is selected. The record service removes this field unless content type is HTML; however, it is not used as the final message during channel selection until the current `html` versus `html_message` value mismatch is fixed.

Example

html message-example
20. plain text

20. plain text

Parameter identifier: 20 Data type: textarea
Turkish name düz metin
English name plain text

Description

The message delivered when plain-text content type is selected. The record service keeps the field only when content type is 0; for plain text, channel selection copies this value into the journey’s eligible-channel message and the operation record stores the content actually sent.

Example

plain text-example
21. provider send api id

21. provider send api id

Parameter identifier: 21 Data type: text
Turkish name sağlayıcı gönderim api id
English name provider send api id

Description

The client identifier of the user API record that sends the message to the external provider. The API record is loaded while reading channel design; channel processing executes its code and expects `channel_success_status`, provider response, and delivery-check identifier, so a valid identifier and code are required for delivery.

Example

provider send api id-example
22. provider delivery check api id

22. provider delivery check api id

Parameter identifier: 22 Data type: text
Turkish name sağlayıcı ileti kontrol api id
English name provider delivery check api id

Description

The client identifier of the user API record that queries message status after delivery. It is copied into the operation record; when present together with a delivery-check identifier, the timer executes API code to update delivery status, failure reason, follow-up duration, and service response.

Example

provider delivery check api id-example
23. create date

23. create date

Parameter identifier: 23 Data type: datetime
Turkish name oluşturma tarihi
English name create date

Description

Defined in WDM to store the initial creation time of the channel design, and the configuration reader reads this field. However, the current record endpoint mistakenly writes the timestamp to top-level parameter 26, so this field may remain empty in the standard save path.

Example

2026-10-25T09:45:55
24. update date

24. update date

Parameter identifier: 24 Data type: datetime
Turkish name güncelleme tarihi
English name update date

Description

Defined in WDM to store the latest update time of the channel design, and the configuration reader reads this field. The current record endpoint mistakenly writes the timestamp to top-level parameter 27, so a current value may not be produced here.

Example

2026-10-25T09:45:55
25. name

25. name

Parameter identifier: 25 Data type: text
Turkish name adı
English name name

Description

The name that distinguishes the channel design for users. The record endpoint writes a form field named `description` into this parameter; because configuration selection does not read the name, it does not change algorithmic eligibility and is used for management screens and human readability.

Example

name-example
26. whatsapp sender id

26. whatsapp sender id

Parameter identifier: 26 Data type: text
Turkish name whatsapp gönderici id
English name whatsapp sender id

Description

Defined under a channel step to store the sender identifier used by a WhatsApp provider. WhatsApp is absent from current channel-type options and save/read code does not process step parameter 26; additionally, the record endpoint mistakenly writes a timestamp to top-level parameter 26. Therefore, it is not functional in the current standard flow.

Example

whatsapp sender id-example
27. whatsapp template id

27. whatsapp template id

Parameter identifier: 27 Data type: text
Turkish name whatsapp şablon id
English name whatsapp template id

Description

Defined under a channel step to store the message-template identifier used by a WhatsApp provider. Because current step save/read code does not carry this field and top-level parameter 27 is mistakenly used for a timestamp, it is not used in standard channel delivery.

Example

whatsapp template id-example
28. message language

28. message language

Parameter identifier: 28 Data type: select
Turkish name mesaj dili
English name message language

Description

The language code of the message in the channel step. WDM provides 79 language options; however, the current step-save method does not persist parameter 28 and the configuration reader does not read it. Therefore, it does not automatically affect template or message selection and must not be assumed to persist in the standard flow.

Options

Value Turkish English Behavior
0 TR TR Interprets the field as “TR”; the related filter or step operates according to this value.
1 AZ AZ Interprets the field as “AZ”; the related filter or step operates according to this value.
2 EN EN Interprets the field as “EN”; the related filter or step operates according to this value.
3 FA FA Interprets the field as “FA”; the related filter or step operates according to this value.
4 DE DE Interprets the field as “DE”; the related filter or step operates according to this value.
5 CA CA Interprets the field as “CA”; the related filter or step operates according to this value.
6 PT PT Interprets the field as “PT”; the related filter or step operates according to this value.
7 ES ES Interprets the field as “ES”; the related filter or step operates according to this value.
8 SQ SQ Interprets the field as “SQ”; the related filter or step operates according to this value.
9 NL NL Interprets the field as “NL”; the related filter or step operates according to this value.
10 TKL TKL Interprets the field as “TKL”; the related filter or step operates according to this value.
11 AR AR Interprets the field as “AR”; the related filter or step operates according to this value.
12 BN BN Interprets the field as “BN”; the related filter or step operates according to this value.
13 BE BE Interprets the field as “BE”; the related filter or step operates according to this value.
14 FR FR Interprets the field as “FR”; the related filter or step operates according to this value.
15 BS BS Interprets the field as “BS”; the related filter or step operates according to this value.
16 MS MS Interprets the field as “MS”; the related filter or step operates according to this value.
17 BG BG Interprets the field as “BG”; the related filter or step operates according to this value.
18 DZ DZ Interprets the field as “DZ”; the related filter or step operates according to this value.
19 CS CS Interprets the field as “CS”; the related filter or step operates according to this value.
20 ZH ZH Interprets the field as “ZH”; the related filter or step operates according to this value.
21 DA DA Interprets the field as “DA”; the related filter or step operates according to this value.
22 ID ID Interprets the field as “ID”; the related filter or step operates according to this value.
23 TI TI Interprets the field as “TI”; the related filter or step operates according to this value.
24 HY HY Interprets the field as “HY”; the related filter or step operates according to this value.
25 ET ET Interprets the field as “ET”; the related filter or step operates according to this value.
26 AM AM Interprets the field as “AM”; the related filter or step operates according to this value.
27 FO FO Interprets the field as “FO”; the related filter or step operates according to this value.
28 FI FI Interprets the field as “FI”; the related filter or step operates according to this value.
29 KL KL Interprets the field as “KL”; the related filter or step operates according to this value.
30 KO KO Interprets the field as “KO”; the related filter or step operates according to this value.
31 KA KA Interprets the field as “KA”; the related filter or step operates according to this value.
32 HR HR Interprets the field as “HR”; the related filter or step operates according to this value.
33 HI HI Interprets the field as “HI”; the related filter or step operates according to this value.
34 HE HE Interprets the field as “HE”; the related filter or step operates according to this value.
35 SV SV Interprets the field as “SV”; the related filter or step operates according to this value.
36 IT IT Interprets the field as “IT”; the related filter or step operates according to this value.
37 IS IS Interprets the field as “IS”; the related filter or step operates according to this value.
38 JA JA Interprets the field as “JA”; the related filter or step operates according to this value.
39 KM KM Interprets the field as “KM”; the related filter or step operates according to this value.
40 KK KK Interprets the field as “KK”; the related filter or step operates according to this value.
41 EL EL Interprets the field as “EL”; the related filter or step operates according to this value.
42 KY KY Interprets the field as “KY”; the related filter or step operates according to this value.
43 LO LO Interprets the field as “LO”; the related filter or step operates according to this value.
44 LV LV Interprets the field as “LV”; the related filter or step operates according to this value.
45 LT LT Interprets the field as “LT”; the related filter or step operates according to this value.
46 LB LB Interprets the field as “LB”; the related filter or step operates according to this value.
47 HU HU Interprets the field as “HU”; the related filter or step operates according to this value.
48 MG MG Interprets the field as “MG”; the related filter or step operates according to this value.
49 MK MK Interprets the field as “MK”; the related filter or step operates according to this value.
50 DV DV Interprets the field as “DV”; the related filter or step operates according to this value.
51 MT MT Interprets the field as “MT”; the related filter or step operates according to this value.
52 MN MN Interprets the field as “MN”; the related filter or step operates according to this value.
53 RO RO Interprets the field as “RO”; the related filter or step operates according to this value.
54 NE NE Interprets the field as “NE”; the related filter or step operates according to this value.
55 NO NO Interprets the field as “NO”; the related filter or step operates according to this value.
56 UZ UZ Interprets the field as “UZ”; the related filter or step operates according to this value.
57 UR UR Interprets the field as “UR”; the related filter or step operates according to this value.
58 UR PL Interprets the field as “PL”; the related filter or step operates according to this value.
59 RW RW Interprets the field as “RW”; the related filter or step operates according to this value.
60 RU RU Interprets the field as “RU”; the related filter or step operates according to this value.
61 SR SR Interprets the field as “SR”; the related filter or step operates according to this value.
62 SK SK Interprets the field as “SK”; the related filter or step operates according to this value.
63 SL SL Interprets the field as “SL”; the related filter or step operates according to this value.
64 SI SI Interprets the field as “SI”; the related filter or step operates according to this value.
65 SW SW Interprets the field as “SW”; the related filter or step operates according to this value.
66 TH TH Interprets the field as “TH”; the related filter or step operates according to this value.
67 TO TO Interprets the field as “TO”; the related filter or step operates according to this value.
68 TVL TVL Interprets the field as “TVL”; the related filter or step operates according to this value.
69 TK TK Interprets the field as “TK”; the related filter or step operates according to this value.
70 UK UK Interprets the field as “UK”; the related filter or step operates according to this value.
71 BI BI Interprets the field as “BI”; the related filter or step operates according to this value.
72 VI VI Interprets the field as “VI”; the related filter or step operates according to this value.
73 TG TG Interprets the field as “TG”; the related filter or step operates according to this value.
74 SO SO Interprets the field as “SO”; the related filter or step operates according to this value.
75 MY MY Interprets the field as “MY”; the related filter or step operates according to this value.
76 Interprets the field as “”; the related filter or step operates according to this value.
77 NIU NIU Interprets the field as “NIU”; the related filter or step operates according to this value.
78 SM SM Interprets the field as “SM”; the related filter or step operates according to this value.

Example

0 — TR
About WDC Campaign / Agenda
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Agenda

Packages campaign journeys for channel operation at a specific date and time and tracks their states.

Agenda flow

Journeys are added to a main document by campaign and hour. Large lists are split into additional parts and merged again before processing. Only active journeys run; successfully processed rows become completed, while rows requiring another schedule become replanned.

Code finding: Additional part documents are created with `_part_N` identifiers, but their status is not set to “additional document.” No operation writing “continue” or “complete” for the main agenda was found in the inspected code.
0. status

0. status

Parameter identifier: 0 Data type: select
Turkish name durum
English name status

Description

The processing lifecycle state of the agenda document. A new document is written as `wait` when it contains journeys and as `cancel` when its list is empty; when an agenda from the last 48 hours or earlier still contains active journeys and is regenerated, the old document is set to `replanned`. No automatic write of `continue`, `complete`, or `additional document` was found in the inspected code.

Options

Value Turkish English Behavior
0 iptal cancel Indicates an empty or cancelled agenda.
1 bekliyor wait Indicates an agenda waiting to be processed.
2 devam ediyor continue Represents an agenda in progress in the schema; inspected code does not write it automatically.
3 tamamlandı complete Represents a completed agenda in the schema; inspected code does not write it automatically.
4 yeniden planlandı replanned Indicates an old document whose active journeys were moved to a new agenda.
5 ek doküman additional document Represents an additional part in the schema; current partition code does not write this state automatically.

Example

0 — cancel
1. campaign name

1. campaign name

Parameter identifier: 1 Data type: text
Turkish name kampanya adı
English name campaign name

Description

The display name of the campaign associated with the agenda. It is copied from campaign configuration when a new main agenda document is created; additional part documents copy the main document data, so they carry the same name and make the date-based agenda readable in reports.

Example

campaign name-example
2. campaign client id

2. campaign client id

Parameter identifier: 2 Data type: text
Turkish name kampanya client id
English name campaign client id

Description

The client identifier of the campaign that owns the agenda. The main agenda client identifier is produced by combining this value with agenda date; querying, partitioning, merging, and replanning operations group agendas by campaign through this field.

Example

campaign client id-example
3. agenda date

3. agenda date

Parameter identifier: 3 Data type: datetime
Turkish name ajanda tarihi
English name agenda date

Description

The agenda date representing the hour boundary at which channel operations are scheduled. It is used with campaign identifier in the main client identifier, and main/additional part documents for the same date are merged through this value. When processing time arrives, only active journeys run after campaign day and hour eligibility is also verified.

Example

2026-10-25T10:00:00
4. additional part count

4. additional part count

Parameter identifier: 4 Data type: integer
Turkish name ek parça sayısı
English name additional part count

Description

Specifies how many `_part_N` documents exist in addition to the main agenda. When journey count exceeds configured document capacity, the first batch remains in the main document, remaining batches are stored as `_part_1`, `_part_2`, and so on, and the counter is updated to the new part count. During reading, that many parts are fetched and appended to the main journey list.

Example

2
5. journey list

5. journey list

Parameter identifier: 5 Data type: list_parameter
Turkish name yolculuk listesi
English name journey list

Description

A repeating list that stores journeys to process for the same campaign and agenda hour. A new journey identifier is added with active status only when it is not already present, while identifiers marked for removal are deleted. Large lists are split into main and additional documents according to the storage limit and merged back into one logical list before processing.

Example

[{ ... }]
6. journey id

6. journey id

Parameter identifier: 6 Data type: text
Turkish name yolculuk id
English name journey id

Description

The client identifier of the customer journey referenced by the agenda row. Channel processing fetches journey records in bulk with these identifiers; the same identifier is not added twice to one agenda and is carried into a new agenda document during replanning.

Example

journey id-example
7. journey status

7. journey status

Parameter identifier: 7 Data type: select
Turkish name yolculuk durum
English name journey status

Description

The processing state of one journey within this agenda. A newly added row starts as `active`; after channel processing it is set to `operation completed` on success or `replanned` when unsuccessful and requiring another agenda. Only active rows are executed or replanned from old agendas; no code path automatically writing `cancel` was found in the inspected file.

Options

Value Turkish English Behavior
0 iptal edildi cancel Excludes the row from processing; no automatic write path was found.
1 aktif active Makes the row eligible for channel processing and replanning.
2 operasyon tamamlandı operation completed Indicates that the channel operation completed successfully.
3 tekrardan planlandı replanned Indicates that an unsuccessful operation was moved to a new agenda.

Example

0 — cancel
8. create date

8. create date

Parameter identifier: 8 Data type: datetime
Turkish name oluşturma tarihi
English name create date

Description

The Coordinated Universal Time at which the main agenda document was first created. It is written with the current time when a document for a new date is prepared; it is preserved when an existing agenda is updated, and additional parts carry the same creation time because they are produced from copied main data.

Example

2026-10-25T10:00:00
9. update date

9. update date

Parameter identifier: 9 Data type: datetime
Turkish name güncelleme tarihi
English name update date

Description

The last update time written when an existing agenda’s journey list changes or an old agenda is marked as replanned. It may be absent initially on a new document; it is refreshed with current Coordinated Universal Time when additions, removals, or replanning occur on an existing document.

Example

2026-10-25T10:00:00
About WDC Campaign / Customer / Journey / Operation / Survey
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Customer / Journey / Operation / Survey

Stores predefined and manual answers of a completed WDC survey under the latest channel operation.

Answer-recording flow

The timer retrieves completed surveys, finds the latest operation of the journey, and creates an active answer record. Predefined question identifiers 0–33 map to fields 1–34; general opinion is written to 35 and manual answers under list 37.

Code findings: Survey generation uses answer identifiers 1–5 while result WDM options are 0–4, and recording performs no conversion. In addition, parameter 36 create date and parameter 41 answer date are not written automatically.
0. status

0. status

Parameter identifier: 0 Data type: select
Turkish name durum
English name status

Description

The activity state of the survey-answer record. The timer creates a record only for surveys whose survey-service result is `complete` and writes the state as active; an expired but incomplete survey is removed from the queue, but no passive answer record is created in this layer.

Options

Value Turkish English Behavior
0 pasif passive Represents a passive record in the schema; the automatic creation path does not write this value.
1 aktif active Stores the completed survey answer as an active reporting record.

Example

0 — passive
1. how likely are you to recommend our service to others?

1. how likely are you to recommend our service to others?

Parameter identifier: 1 Data type: select
Turkish name hizmetimizi başkalarına tavsiye etme olasılığınız nedir?
English name how likely are you to recommend our service to others?

Description

The selected answer value for the predefined question “how likely are you to recommend our service to others?”. Survey-service question identifier 0 is mapped to WDM field 1 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
2. how would you rate the service you received overall?

2. how would you rate the service you received overall?

Parameter identifier: 2 Data type: select
Turkish name genel olarak aldığınız hizmeti nasıl değerlendirirsiniz?
English name how would you rate the service you received overall?

Description

The selected answer value for the predefined question “how would you rate the service you received overall?”. Survey-service question identifier 1 is mapped to WDM field 2 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
3. how satisfied were you with the doctor's service?

3. how satisfied were you with the doctor's service?

Parameter identifier: 3 Data type: select
Turkish name hekimin sunduğu hizmetten ne kadar memnun kaldınız?
English name how satisfied were you with the doctor's service?

Description

The selected answer value for the predefined question “how satisfied were you with the doctor's service?”. Survey-service question identifier 2 is mapped to WDM field 3 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
4. how would you rate the reception and registration process?

4. how would you rate the reception and registration process?

Parameter identifier: 4 Data type: select
Turkish name banko ve kayıt işlemleri sürecini nasıl değerlendirirsiniz?
English name how would you rate the reception and registration process?

Description

The selected answer value for the predefined question “how would you rate the reception and registration process?”. Survey-service question identifier 3 is mapped to WDM field 4 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
5. how satisfied were you with the nursing services?

5. how satisfied were you with the nursing services?

Parameter identifier: 5 Data type: select
Turkish name hemşirelik hizmetlerinden ne düzeyde memnun kaldınız?
English name how satisfied were you with the nursing services?

Description

The selected answer value for the predefined question “how satisfied were you with the nursing services?”. Survey-service question identifier 4 is mapped to WDM field 5 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
6. how would you rate the beautician's service?

6. how would you rate the beautician's service?

Parameter identifier: 6 Data type: select
Turkish name estetisyen hizmetini nasıl değerlendirirsiniz?
English name how would you rate the beautician's service?

Description

The selected answer value for the predefined question “how would you rate the beautician's service?”. Survey-service question identifier 5 is mapped to WDM field 6 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
7. were you satisfied with the podologist's service?

7. were you satisfied with the podologist's service?

Parameter identifier: 7 Data type: select
Turkish name podolog hizmetinden memnun kaldınız mı?
English name were you satisfied with the podologist's service?

Description

The selected answer value for the predefined question “were you satisfied with the podologist's service?”. Survey-service question identifier 6 is mapped to WDM field 7 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
8. how would you rate the cleaning services?

8. how would you rate the cleaning services?

Parameter identifier: 8 Data type: select
Turkish name temizlik hizmetlerini nasıl değerlendirirsiniz?
English name how would you rate the cleaning services?

Description

The selected answer value for the predefined question “how would you rate the cleaning services?”. Survey-service question identifier 7 is mapped to WDM field 8 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
9. how satisfied were you with the food services?

9. how satisfied were you with the food services?

Parameter identifier: 9 Data type: select
Turkish name yemek hizmetlerinden ne kadar memnun kaldınız?
English name how satisfied were you with the food services?

Description

The selected answer value for the predefined question “how satisfied were you with the food services?”. Survey-service question identifier 8 is mapped to WDM field 9 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
10. how would you rate the admission and discharge process?

10. how would you rate the admission and discharge process?

Parameter identifier: 10 Data type: select
Turkish name yatış ve taburculuk sürecini nasıl değerlendirirsiniz?
English name how would you rate the admission and discharge process?

Description

The selected answer value for the predefined question “how would you rate the admission and discharge process?”. Survey-service question identifier 9 is mapped to WDM field 10 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
11. were you satisfied with the parking services?

11. were you satisfied with the parking services?

Parameter identifier: 11 Data type: select
Turkish name otopark hizmetlerinden memnun kaldınız mı?
English name were you satisfied with the parking services?

Description

The selected answer value for the predefined question “were you satisfied with the parking services?”. Survey-service question identifier 10 is mapped to WDM field 11 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
12. how would you rate the valet parking service?

12. how would you rate the valet parking service?

Parameter identifier: 12 Data type: select
Turkish name vale otopark hizmetini nasıl değerlendirirsiniz?
English name how would you rate the valet parking service?

Description

The selected answer value for the predefined question “how would you rate the valet parking service?”. Survey-service question identifier 11 is mapped to WDM field 12 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
13. how satisfied were you with the sleep technician's service?

13. how satisfied were you with the sleep technician's service?

Parameter identifier: 13 Data type: select
Turkish name uyku teknikerinin hizmetinden ne ölçüde memnun kaldınız?
English name how satisfied were you with the sleep technician's service?

Description

The selected answer value for the predefined question “how satisfied were you with the sleep technician's service?”. Survey-service question identifier 12 is mapped to WDM field 13 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
14. how would you rate the service provided by the embryologist?

14. how would you rate the service provided by the embryologist?

Parameter identifier: 14 Data type: select
Turkish name embriyolog tarafından sunulan hizmeti nasıl değerlendirirsiniz?
English name how would you rate the service provided by the embryologist?

Description

The selected answer value for the predefined question “how would you rate the service provided by the embryologist?”. Survey-service question identifier 13 is mapped to WDM field 14 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
15. how satisfied were you with the physiotherapist's service?

15. how satisfied were you with the physiotherapist's service?

Parameter identifier: 15 Data type: select
Turkish name fizyoterapist hizmetinden ne kadar memnun kaldınız?
English name how satisfied were you with the physiotherapist's service?

Description

The selected answer value for the predefined question “how satisfied were you with the physiotherapist's service?”. Survey-service question identifier 14 is mapped to WDM field 15 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
16. how would you rate the facilities of the breastfeeding room?

16. how would you rate the facilities of the breastfeeding room?

Parameter identifier: 16 Data type: select
Turkish name emzirme odasının olanaklarını nasıl değerlendirirsiniz?
English name how would you rate the facilities of the breastfeeding room?

Description

The selected answer value for the predefined question “how would you rate the facilities of the breastfeeding room?”. Survey-service question identifier 15 is mapped to WDM field 16 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
17. were you satisfied with the service provided by the eye technician?

17. were you satisfied with the service provided by the eye technician?

Parameter identifier: 17 Data type: select
Turkish name göz teknikeri tarafından sunulan hizmetten memnun kaldınız mı?
English name were you satisfied with the service provided by the eye technician?

Description

The selected answer value for the predefined question “were you satisfied with the service provided by the eye technician?”. Survey-service question identifier 16 is mapped to WDM field 17 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
18. how would you rate the blood sampling process?

18. how would you rate the blood sampling process?

Parameter identifier: 18 Data type: select
Turkish name kan alma sürecini nasıl değerlendirirsiniz?
English name how would you rate the blood sampling process?

Description

The selected answer value for the predefined question “how would you rate the blood sampling process?”. Survey-service question identifier 17 is mapped to WDM field 18 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
19. how would you rate the cafeteria services?

19. how would you rate the cafeteria services?

Parameter identifier: 19 Data type: select
Turkish name kafeterya hizmetlerini nasıl değerlendirirsiniz?
English name how would you rate the cafeteria services?

Description

The selected answer value for the predefined question “how would you rate the cafeteria services?”. Survey-service question identifier 18 is mapped to WDM field 19 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
20. how would you rate the anesthesia process?

20. how would you rate the anesthesia process?

Parameter identifier: 20 Data type: select
Turkish name anestezi sürecini nasıl değerlendirirsiniz?
English name how would you rate the anesthesia process?

Description

The selected answer value for the predefined question “how would you rate the anesthesia process?”. Survey-service question identifier 19 is mapped to WDM field 20 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
21. were you satisfied with the service provided by the dental technician?

21. were you satisfied with the service provided by the dental technician?

Parameter identifier: 21 Data type: select
Turkish name diş teknikerinin sunduğu hizmetten memnun kaldınız mı?
English name were you satisfied with the service provided by the dental technician?

Description

The selected answer value for the predefined question “were you satisfied with the service provided by the dental technician?”. Survey-service question identifier 20 is mapped to WDM field 21 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
22. how would you rate the in-clinic coordination and guidance?

22. how would you rate the in-clinic coordination and guidance?

Parameter identifier: 22 Data type: select
Turkish name klinik içi koordinasyon ve yönlendirmeyi nasıl değerlendirirsiniz?
English name how would you rate the in-clinic coordination and guidance?

Description

The selected answer value for the predefined question “how would you rate the in-clinic coordination and guidance?”. Survey-service question identifier 21 is mapped to WDM field 22 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
23. what was your experience with the mobile application?

23. what was your experience with the mobile application?

Parameter identifier: 23 Data type: select
Turkish name mobil uygulama deneyiminiz nasıldı?
English name what was your experience with the mobile application?

Description

The selected answer value for the predefined question “what was your experience with the mobile application?”. Survey-service question identifier 22 is mapped to WDM field 23 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
24. how satisfied were you with the service of the radiotherapy team?

24. how satisfied were you with the service of the radiotherapy team?

Parameter identifier: 24 Data type: select
Turkish name radyoterapi ekibinin hizmetinden ne kadar memnun kaldınız?
English name how satisfied were you with the service of the radiotherapy team?

Description

The selected answer value for the predefined question “how satisfied were you with the service of the radiotherapy team?”. Survey-service question identifier 23 is mapped to WDM field 24 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
25. how would you rate the process of sharing results and discussing results?

25. how would you rate the process of sharing results and discussing results?

Parameter identifier: 25 Data type: select
Turkish name sonuçların paylaşımı ve sonuç görüşmesi sürecini nasıl değerlendirirsiniz?
English name how would you rate the process of sharing results and discussing results?

Description

The selected answer value for the predefined question “how would you rate the process of sharing results and discussing results?”. Survey-service question identifier 24 is mapped to WDM field 25 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
26. to what extent were you satisfied with the resolution process of your complaints?

26. to what extent were you satisfied with the resolution process of your complaints?

Parameter identifier: 26 Data type: select
Turkish name şikâyetlerinizin çözüm sürecinden ne ölçüde memnun kaldınız?
English name to what extent were you satisfied with the resolution process of your complaints?

Description

The selected answer value for the predefined question “to what extent were you satisfied with the resolution process of your complaints?”. Survey-service question identifier 25 is mapped to WDM field 26 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
27. how would you rate your experience using the website?

27. how would you rate your experience using the website?

Parameter identifier: 27 Data type: select
Turkish name web sitesini kullanma deneyiminizi nasıl değerlendirirsiniz?
English name how would you rate your experience using the website?

Description

The selected answer value for the predefined question “how would you rate your experience using the website?”. Survey-service question identifier 26 is mapped to WDM field 27 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
28. how did you find the process of submitting your complaints and receiving feedback?

28. how did you find the process of submitting your complaints and receiving feedback?

Parameter identifier: 28 Data type: select
Turkish name şikâyetlerinizi iletme ve geri dönüş sürecini nasıl buldunuz?
English name how did you find the process of submitting your complaints and receiving feedback?

Description

The selected answer value for the predefined question “how did you find the process of submitting your complaints and receiving feedback?”. Survey-service question identifier 27 is mapped to WDM field 28 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
29. how would you rate the in-hospital guidance and transfer process?

29. how would you rate the in-hospital guidance and transfer process?

Parameter identifier: 29 Data type: select
Turkish name hastane içi yönlendirme ve aktarım sürecini nasıl değerlendirirsiniz?
English name how would you rate the in-hospital guidance and transfer process?

Description

The selected answer value for the predefined question “how would you rate the in-hospital guidance and transfer process?”. Survey-service question identifier 28 is mapped to WDM field 29 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
30. were you satisfied with the video clinic (remote consultation) service?

30. were you satisfied with the video clinic (remote consultation) service?

Parameter identifier: 30 Data type: select
Turkish name video klinik (uzaktan görüşme) hizmetinden memnun kaldınız mı?
English name were you satisfied with the video clinic (remote consultation) service?

Description

The selected answer value for the predefined question “were you satisfied with the video clinic (remote consultation) service?”. Survey-service question identifier 29 is mapped to WDM field 30 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
31. how would you rate the content and scope of the check-up?

31. how would you rate the content and scope of the check-up?

Parameter identifier: 31 Data type: select
Turkish name check-up içeriği ve kapsamını nasıl değerlendirirsiniz?
English name how would you rate the content and scope of the check-up?

Description

The selected answer value for the predefined question “how would you rate the content and scope of the check-up?”. Survey-service question identifier 30 is mapped to WDM field 31 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
32. what was your experience communicating with the call center?

32. what was your experience communicating with the call center?

Parameter identifier: 32 Data type: select
Turkish name çağrı merkezi ile iletişim deneyiminiz nasıldı?
English name what was your experience communicating with the call center?

Description

The selected answer value for the predefined question “what was your experience communicating with the call center?”. Survey-service question identifier 31 is mapped to WDM field 32 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
33. how would you rate the appointment and service scheduling?

33. how would you rate the appointment and service scheduling?

Parameter identifier: 33 Data type: select
Turkish name randevu ve hizmet zamanlamasını nasıl değerlendirirsiniz?
English name how would you rate the appointment and service scheduling?

Description

The selected answer value for the predefined question “how would you rate the appointment and service scheduling?”. Survey-service question identifier 32 is mapped to WDM field 33 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
34. to what extent were you satisfied with the service of the radiology technician?

34. to what extent were you satisfied with the service of the radiology technician?

Parameter identifier: 34 Data type: select
Turkish name radyoloji teknikerinin hizmetinden ne düzeyde memnun kaldınız?
English name to what extent were you satisfied with the service of the radiology technician?

Description

The selected answer value for the predefined question “to what extent were you satisfied with the service of the radiology technician?”. Survey-service question identifier 33 is mapped to WDM field 34 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

Options

Value Turkish English Behavior
0 😞 kesinlikle memnun değilim 😞 i am definitely not satisfied Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 😕 memnun değilim 😕 i am not satisfied Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 😐 kararsızım 😐 i am undecided Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 🙂 memnunum 🙂 i am satisfied Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 😍 çok memnunum 😍 i am very satisfied Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.

Example

0 — 😞 i am definitely not satisfied
35. could you write your general thoughts?

35. could you write your general thoughts?

Parameter identifier: 35 Data type: textarea
Turkish name genel olarak düşüncelerinizi yazabilir misiniz ?
English name could you write your general thoughts?

Description

The answer to the free-text question created when general opinion is enabled in survey settings. Result code writes an answer whose question identifier is `note` or `35` into this field; campaign reporting collects a nonempty value as text answer number 35.

Example

Hizmetten genel olarak memnun kaldım.
36. create date

36. create date

Parameter identifier: 36 Data type: datetime
Turkish name oluşturma tarihi
English name create date

Description

Defined to store the creation time of the survey-answer record, and campaign reporting first attempts to use this field for period grouping. However, the inspected timer does not write parameter 36 when creating an answer record; when it is empty, reporting falls back to the journey date.

Example

2026-10-25T09:45:55
37. manuel answer list

37. manuel answer list

Parameter identifier: 37 Data type: list_parameter
Turkish name manuel cevap listesi
English name manuel answer list

Description

A repeating list that stores answers to manual questions outside the 34 predefined fields. Each answer is stored with its question identifier; parameter 39, answer identifier, is used when the manual question is select type, while parameter 40, answer text, is used for other types. This preserves different manual answer types together for reporting.

Example

[{ ... }]
38. question id

38. question id

Parameter identifier: 38 Data type: text
Turkish name soru id
English name question id

Description

The identifier that specifies which manual question owns the answer. Because manual questions are generated as `m_0`, `m_1`, and so on in survey settings, result code writes the same `q_id` from the service response here; reporting groups questions by this identifier.

Example

question id-example
39. answer id

39. answer id

Parameter identifier: 39 Data type: text
Turkish name yanıt id
English name answer id

Description

The identifier of the answer option selected by the user for a select-type manual question. It is written when result input `type` is `select`; campaign reporting reads this field first and classifies a nonempty answer as select.

Example

answer id-example
40. answer text

40. answer text

Parameter identifier: 40 Data type: textarea
Turkish name yanıt metni
English name answer text

Description

The answer text supplied by the user for manual question types other than select. Result code writes incoming `answer` into this textarea without distinguishing int, float, text, textarea, date, or datetime; reporting uses it as a text answer when parameter 39 is empty.

Example

answer text-example
41. answer date

41. answer date

Parameter identifier: 41 Data type: datetime
Turkish name yanıt tarihi
English name answer date

Description

Defined to store the answer date of an individual manual response. The inspected survey-result recording code does not write this field, and campaign reporting does not read manual answer time from it; it must not be assumed to populate automatically in the current standard flow.

Example

2026-10-25T09:45:55