Updating links to custom identifiers documentation (#878)

* Update dbtUnified_0.1.2.json

Updated links to custom identifiers page from customer-identifiers to custom-identifiers.

* Update links in dbtUtils_0.16.0.json 

Updated links for custom identifiers

* Update links in dbtMobile_1.0.0.json

Update links to custom-identifiers

* Update links in dbtWeb_1.0.0.json

Updated links to custom-identifiers

* Update links in dbtEcommerce_0.8.1.json

Updated links to custom-identifiers

* Update links in dbtUtils_0.16.4.json

Updated links to custom-identifiers

* Update dbtUnified_0.4.0.json

* Update dbtUnified_0.3.1.json

* Update links in dbtUnified_0.3.0.json

Updated links to custom-identifiers

* Update links in dbtMediaPlayer_0.7.2.json

Updated links to custom-identifiers

* Update links in dbtMediaPlayer_0.7.0.json

Updated links to custom-identifiers

* Update links in dbtMediaPlayer_0.7.1.json

Updated links to custom-identifiers

* Update links in dbtUnified_0.2.0.json

Updated links to custom-identifiers

* Update links in dbtEcommerce_0.8.2.json

Updated links to custom-identifiers

* Update links in dbtEcommerce_0.8.0.json

Updated links to custom-identifiers

* Update links in dbtEcommerce_0.6.1.json

Updated links to custom-identifiers

* Update links in dbtEcommerce_0.6.0.json

Updated links to custom-identifiers

* Update links in dbtEcommerce_0.7.0.json

Updated links to custom-identifiers

* Update links in dbtWeb_0.16.2.json

Updated links to custom-identifiers

* Update links in dbtWeb_0.16.1.json

Updated links to custom-identifiers

* Update links in dbtWeb_0.16.0.json

Updated links to custom-identifiers

* Update links in dbtUtils_0.16.2.json

Updated links to custom-identifiers

* Update links in dbtUtils_0.16.1.json

Updated links to custom-identifiers

* Update links in dbtUtils_0.16.3.json

Updated links to custom-identifiers

* Update links in  dbtUtils_0.15.2.json

Updated links to custom-identifiers

* Update custom identifiers link in _redirects

Updated URL to custom-identifiers

src/components/JsonSchemaValidator/Schemas/dbtEcommerce_0.6.0.json

@@ -347,7 +347,7 @@
       "consoleGroup": "advanced",
       "title": "Session Identifiers",
       "group": "Operation and Logic",
-      "longDescription": "A list of key:value dictionaries which contain all of the contexts and fields where your session identifiers are located. For each entry in the list, if your map contains the `schema` value `atomic`, then this refers to a field found directly in the atomic `events` table. If you are trying to introduce a context/entity with an identifier in it, the package will look for the context in your events table with the name specified in the `schema` field. It will use the specified value in the `field` key as the field name to access. For Redshift/Postgres, using the `schema` key the package will try to find a table in your `snowplow__events_schema` schema with the same name as the `schema` value provided, and join that. If multiple fields are specified, the package will try to coalesce all fields in the order specified in the list. For a better understanding of the advanced usage of this variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/customer-identifiers/) section for more details.",
+      "longDescription": "A list of key:value dictionaries which contain all of the contexts and fields where your session identifiers are located. For each entry in the list, if your map contains the `schema` value `atomic`, then this refers to a field found directly in the atomic `events` table. If you are trying to introduce a context/entity with an identifier in it, the package will look for the context in your events table with the name specified in the `schema` field. It will use the specified value in the `field` key as the field name to access. For Redshift/Postgres, using the `schema` key the package will try to find a table in your `snowplow__events_schema` schema with the same name as the `schema` value provided, and join that. If multiple fields are specified, the package will try to coalesce all fields in the order specified in the list. For a better understanding of the advanced usage of this variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/custom-identifiers/) section for more details.",
       "packageDefault": "[{\"schema\" : \"atomic\", \"field\" : \"domain_sessionid\"}]",
       "type": "array",
       "description": "> Click the plus sign to add a new entry",
@@ -379,7 +379,7 @@
       "consoleGroup": "advanced",
       "type": "string",
       "title": "SQL for your session identifier",
-      "longDescription": "This allows you to override the `session_identifiers` SQL, to define completely custom SQL in order to build out a session identifier for your events. If you are interested in using this instead of providing identifiers through the `session_identifiers` variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/customer-identifiers/) section for more details on how to do that.",
+      "longDescription": "This allows you to override the `session_identifiers` SQL, to define completely custom SQL in order to build out a session identifier for your events. If you are interested in using this instead of providing identifiers through the `session_identifiers` variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/custom-identifiers/) section for more details on how to do that.",
       "packageDefault": "",
       "group": "Operation and Logic"
     },
@@ -400,7 +400,7 @@
       "type": "array",
       "title": "User Identifiers",
       "group": "Operation and Logic",
-      "longDescription": "A list of key:value dictionaries which contain all of the contexts and fields where your user identifiers are located. For each entry in the list, if your map contains the `schema` value `atomic`, then this refers to a field found directly in the atomic `events` table. If you are trying to introduce a context/entity with an identifier in it, the package will look for the context in your events table with the name specified in the `schema` field. It will use the specified value in the `field` key as the field name to access. For Redshift/Postgres, using the `schema` key the package will try to find a table in your `snowplow__events_schema` schema with the same name as the `schema` value provided, and join that. If multiple fields are specified, the package will try to coalesce all fields in the order specified in the list. For a better understanding of the advanced usage of this variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/customer-identifiers/) section for more details.",
+      "longDescription": "A list of key:value dictionaries which contain all of the contexts and fields where your user identifiers are located. For each entry in the list, if your map contains the `schema` value `atomic`, then this refers to a field found directly in the atomic `events` table. If you are trying to introduce a context/entity with an identifier in it, the package will look for the context in your events table with the name specified in the `schema` field. It will use the specified value in the `field` key as the field name to access. For Redshift/Postgres, using the `schema` key the package will try to find a table in your `snowplow__events_schema` schema with the same name as the `schema` value provided, and join that. If multiple fields are specified, the package will try to coalesce all fields in the order specified in the list. For a better understanding of the advanced usage of this variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/custom-identifiers/) section for more details.",
       "packageDefault": "[{\"schema\" : \"atomic\", \"field\" : \"domain_userid\"}]",
       "description": "> Click the plus sign to add a new entry",
       "minItems": 0,
@@ -431,7 +431,7 @@
       "consoleGroup": "advanced",
       "type": "string",
       "title": "SQL for your user identifier",
-      "longDescription": "This allows you to override the `user_identifiers` SQL, to define completely custom SQL in order to build out a user identifier for your events. If you are interested in using this instead of providing identifiers through the `user_identifiers` variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/customer-identifiers/) section for more details on how to do that.",
+      "longDescription": "This allows you to override the `user_identifiers` SQL, to define completely custom SQL in order to build out a user identifier for your events. If you are interested in using this instead of providing identifiers through the `user_identifiers` variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/custom-identifiers/) section for more details on how to do that.",
       "packageDefault": "",
       "group": "Operation and Logic"
     },

src/components/JsonSchemaValidator/Schemas/dbtEcommerce_0.6.1.json

@@ -347,7 +347,7 @@
       "consoleGroup": "advanced",
       "title": "Session Identifiers",
       "group": "Operation and Logic",
-      "longDescription": "A list of key:value dictionaries which contain all of the contexts and fields where your session identifiers are located. For each entry in the list, if your map contains the `schema` value `atomic`, then this refers to a field found directly in the atomic `events` table. If you are trying to introduce a context/entity with an identifier in it, the package will look for the context in your events table with the name specified in the `schema` field. It will use the specified value in the `field` key as the field name to access. For Redshift/Postgres, using the `schema` key the package will try to find a table in your `snowplow__events_schema` schema with the same name as the `schema` value provided, and join that. If multiple fields are specified, the package will try to coalesce all fields in the order specified in the list. For a better understanding of the advanced usage of this variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/customer-identifiers/) section for more details.",
+      "longDescription": "A list of key:value dictionaries which contain all of the contexts and fields where your session identifiers are located. For each entry in the list, if your map contains the `schema` value `atomic`, then this refers to a field found directly in the atomic `events` table. If you are trying to introduce a context/entity with an identifier in it, the package will look for the context in your events table with the name specified in the `schema` field. It will use the specified value in the `field` key as the field name to access. For Redshift/Postgres, using the `schema` key the package will try to find a table in your `snowplow__events_schema` schema with the same name as the `schema` value provided, and join that. If multiple fields are specified, the package will try to coalesce all fields in the order specified in the list. For a better understanding of the advanced usage of this variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/custom-identifiers/) section for more details.",
       "packageDefault": "[{\"schema\" : \"atomic\", \"field\" : \"domain_sessionid\"}]",
       "type": "array",
       "description": "> Click the plus sign to add a new entry",
@@ -379,7 +379,7 @@
       "consoleGroup": "advanced",
       "type": "string",
       "title": "SQL for your session identifier",
-      "longDescription": "This allows you to override the `session_identifiers` SQL, to define completely custom SQL in order to build out a session identifier for your events. If you are interested in using this instead of providing identifiers through the `session_identifiers` variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/customer-identifiers/) section for more details on how to do that.",
+      "longDescription": "This allows you to override the `session_identifiers` SQL, to define completely custom SQL in order to build out a session identifier for your events. If you are interested in using this instead of providing identifiers through the `session_identifiers` variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/custom-identifiers/) section for more details on how to do that.",
       "packageDefault": "",
       "group": "Operation and Logic"
     },
@@ -400,7 +400,7 @@
       "type": "array",
       "title": "User Identifiers",
       "group": "Operation and Logic",
-      "longDescription": "A list of key:value dictionaries which contain all of the contexts and fields where your user identifiers are located. For each entry in the list, if your map contains the `schema` value `atomic`, then this refers to a field found directly in the atomic `events` table. If you are trying to introduce a context/entity with an identifier in it, the package will look for the context in your events table with the name specified in the `schema` field. It will use the specified value in the `field` key as the field name to access. For Redshift/Postgres, using the `schema` key the package will try to find a table in your `snowplow__events_schema` schema with the same name as the `schema` value provided, and join that. If multiple fields are specified, the package will try to coalesce all fields in the order specified in the list. For a better understanding of the advanced usage of this variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/customer-identifiers/) section for more details.",
+      "longDescription": "A list of key:value dictionaries which contain all of the contexts and fields where your user identifiers are located. For each entry in the list, if your map contains the `schema` value `atomic`, then this refers to a field found directly in the atomic `events` table. If you are trying to introduce a context/entity with an identifier in it, the package will look for the context in your events table with the name specified in the `schema` field. It will use the specified value in the `field` key as the field name to access. For Redshift/Postgres, using the `schema` key the package will try to find a table in your `snowplow__events_schema` schema with the same name as the `schema` value provided, and join that. If multiple fields are specified, the package will try to coalesce all fields in the order specified in the list. For a better understanding of the advanced usage of this variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/custom-identifiers/) section for more details.",
       "packageDefault": "[{\"schema\" : \"atomic\", \"field\" : \"domain_userid\"}]",
       "description": "> Click the plus sign to add a new entry",
       "minItems": 0,
@@ -431,7 +431,7 @@
       "consoleGroup": "advanced",
       "type": "string",
       "title": "SQL for your user identifier",
-      "longDescription": "This allows you to override the `user_identifiers` SQL, to define completely custom SQL in order to build out a user identifier for your events. If you are interested in using this instead of providing identifiers through the `user_identifiers` variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/customer-identifiers/) section for more details on how to do that.",
+      "longDescription": "This allows you to override the `user_identifiers` SQL, to define completely custom SQL in order to build out a user identifier for your events. If you are interested in using this instead of providing identifiers through the `user_identifiers` variable, please see the [Custom Identifiers](docs/modeling-your-data/modeling-your-data-with-dbt/package-features/custom-identifiers/) section for more details on how to do that.",
       "packageDefault": "",
       "group": "Operation and Logic"
     },