Dell PowerConnect W Clearpass 100 Software Advertising Services Deployment Gui - Page 125

Demographic & non-demographic user information

Page 125 highlights

Advertising Services Version 1.3 5 Gathering User Information NOTE The amigopod Visitor Management Appliance is able to gather user information when users (guests) register for access to the network. It is able to do this through the registration forms that it provides. Guest Self-Registration forms can be customized to include additional fields, which can be either factory preset fields or custom fields that are created and configured by a system administrator. The scope of this document covers the deployment of Advertising Services. As such, details regarding the customization of guest self-registration forms are limited to a small number of examples on how to gather demographic information (§3.2), and to defining the types of custom fields that can be used for the intelligent delivery of advertisements (§5.2). For complete details regarding customization of the Guest Self-Registration forms, refer to the amigopod Deployment Guide (§1.2). 5.1 Demographic & non-demographic user information An important concept to understand pertains to the difference between various types of information. Certain types of information can be used to infer that a person belongs to one group or another. Where as other types of information do not infer membership to a group. A number of examples will help to illustrate this point. Let's say that a user registers with an amigopod to gain access to the network. On the registration form, there are a number of fields, including:  Name  Postcode / ZIP code  Mobile phone number  Email address  Gender  Age group  Personal interests (fashion, music, ..., reading) Of these fields, the following do not (directly) place a user into a group:  Name - there are an unlimited number of names that could be provided as a response to a name field, and so a name does not (directly) place a person into a group.  Postcode / ZIP code - there are a large number of possible responses to a request for a postcode or ZIP code, so again, such a field does not (directly) place a person into a group. 125

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128

Advertising Services
Version 1.3
125
5
Gathering User Information
The
amigopod Visitor Management Appliance
is able to gather user
information when users (guests) register for access to the network. It is able
to do this through the registration forms that it provides.
Guest Self-Registration forms can be customized to include additional fields,
which can be either factory preset fields or custom fields that are created and
configured by a system administrator.
The scope of this document covers the deployment of Advertising Services.
As such, details regarding the customization of guest self-registration forms
are limited to a small number of examples on how to gather demographic
information (§3.2), and to defining the types of custom fields that can be used
for the
intelligent delivery
of advertisements (§5.2).
NOTE
For complete details regarding customization of the Guest Self-Registration
forms, refer to the
amigopod Deployment Guide
(§1.2).
5.1
Demographic & non-demographic user information
An important concept to understand pertains to the difference between
various types of information. Certain types of information can be used to infer
that a person belongs to one
group
or another. Where as other types of
information do not infer membership to a group.
A number of examples will help to illustrate this point. Let’s say that a user
registers with an amigopod to gain access to the network. On the registration
form, there are a number of fields, including:
Name
Postcode / ZIP code
Mobile phone number
Email address
Gender
Age group
Personal interests (fashion, music, …, reading)
Of these fields, the following do
not
(directly) place a user into a
group
:
Name
– there are an unlimited number of names that could be
provided as a response to a name field, and so a name does not
(directly) place a person into a group.
Postcode / ZIP code
– there are a large number of possible
responses to a request for a postcode or ZIP code, so again, such
a field does not (directly) place a person into a group.