Skip to content

Commit ad3013c

Browse files
committed
edits
1 parent c411bb6 commit ad3013c

File tree

1 file changed

+14
-12
lines changed

1 file changed

+14
-12
lines changed

src/connections/reverse-etl/index.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -174,15 +174,7 @@ The Segment Connections destination enables you to mold data extracted from your
174174
When you set up destination actions in Reverse ETL, depending on the destination, some mapping fields may require data to be in the form of an object or array.
175175

176176
### Object mapping
177-
To send data to a mapping field that requires object data, you can choose between these two options:
178-
179-
Option | Details
180-
------ | --------
181-
Customize Object | This enables you to manually set up the mapping fields with any data from the model. If the model contains some object data, you can select properties within the object to set up the mappings as well.
182-
Select Object | This enables you to send all nested properties within an object. The model needs to provide data in the format of the object. An example is an `Order completed` model with a `Products` column that’s in object format.
183-
184-
> success ""
185-
> Certain object mapping fields have a fixed list of properties they can accept. If the names of the nested properties in your object don't match with the destination properties, the data won't send. Segment recommends you to use **Customize Object** to ensure your mapping is successful.
177+
You can send data to a mapping field that requires object data. An example of object mapping is an `Order completed` model with a `Products` column that’s in object format.
186178

187179
Example:
188180

@@ -197,10 +189,20 @@ Example:
197189
"productName": "skirt"
198190
}
199191
}
200-
192+
193+
To send data to a mapping field that requires object data, you can choose between these two options:
194+
195+
Option | Details
196+
------ | --------
197+
Customize Object | This enables you to manually set up the mapping fields with any data from the model. If the model contains some object data, you can select properties within the object to set up the mappings as well.
198+
Select Object | This enables you to send all nested properties within an object. The model needs to provide data in the format of the object.
199+
200+
> success ""
201+
> Certain object mapping fields have a fixed list of properties they can accept. If the names of the nested properties in your object don't match with the destination properties, the data won't send. Segment recommends you to use **Customize Object** to ensure your mapping is successful.
202+
201203

202204
### Array mapping
203-
To send data to a mapping field that requires array data, the model must to provide data in the format of an array of objects. An example is an `Order completed` model with a `Product purchased` column that’s in an array format.
205+
To send data to a mapping field that requires array data, the model must provide data in the format of an array of objects. An example is an `Order completed` model with a `Product purchased` column that’s in an array format.
204206

205207
Example:
206208

@@ -226,8 +228,8 @@ To send data to a mapping field that requires array data, you can choose between
226228

227229
Option | Details
228230
------ | --------
229-
Select array | This enables you to send all nested properties within the array.
230231
Customize array | This enables you to select the specific nested properties to send to the destination.
232+
Select array | This enables you to send all nested properties within the array.
231233

232234
> success ""
233235
> Certain array mapping fields have a fixed list of properties they can accept. If the names of the nested properties in your array don't match the destination properties, the data won't send. Segment recommends you to use the **Customize array** option to ensure your mapping is successful.

0 commit comments

Comments
 (0)