Configure necessary custom fields and segments in SendGrid for production and staging environments.
For staging and production environments, create the following custom fields, using the "number" custom field type
[x] One for each of the 59 community districts
[x] One for "citywide"
[x] One to track whether or not the user has confirmed their subscriptions
Custom field naming convention
Naming convention for CD fields should follow this pattern zap_<environment>_<CD identifier>. CD identifier should use ZAP CD IDs which ZAP Search already has a copy of here - look at the first item in each of the nested arrays (K01, K02, etc). For example, the field for K01 has already been created for staging:
Naming for "citywide" field should be zap_<environment>_CW
Naming for "confirmed" field should be zap_<environment>_confirmed
Note you should create 122 custom properties total
For staging and production environments, configure the following segments
[x] One for each of the 59 community districts
[x] One for "citywide"
Note you should have 120 segments total
Segment naming conventions
Follow pattern zap-<environment>-<CD identifier>. For example, zap-staging-K01. For citywide segments, use CW for identifier.
Segments should be associated with the Lists for their environments - (zap-subscribers-staging and zap-subscribers-production)
Each segment should have two conditions
The custom field for the corresponding identifier is 1
The "confirmed" custom field for the corresponding environment is 1
Configure necessary custom fields and segments in SendGrid for production and staging environments.
For staging and production environments, create the following custom fields, using the "number" custom field type
Custom field naming convention
zap_<environment>_<CD identifier>
. CD identifier should use ZAP CD IDs which ZAP Search already has a copy of here - look at the first item in each of the nested arrays (K01
,K02
, etc). For example, the field forK01
has already been created for staging:zap_<environment>_CW
zap_<environment>_confirmed
For staging and production environments, configure the following segments
Segment naming conventions
zap-<environment>-<CD identifier>
. For example,zap-staging-K01
. For citywide segments, useCW
for identifier.zap-subscribers-staging
andzap-subscribers-production
)1
1