diff --git a/src/connections/destinations/catalog/amazon-lambda/index.md b/src/connections/destinations/catalog/amazon-lambda/index.md index 9e21aea1c3..aec548d258 100644 --- a/src/connections/destinations/catalog/amazon-lambda/index.md +++ b/src/connections/destinations/catalog/amazon-lambda/index.md @@ -1,14 +1,16 @@ --- -rewrite: true title: Amazon Lambda Destination +rewrite: true --- -Segment makes it easy to send your data to AWS Lambda (and lots of other destinations). Once you've tracked your data through our open source [libraries](https://segment.com/libraries) we'll translate and route your data to AWS Lambda in the format they understand. [Learn more about how to use AWS Lambda with Segment.](/docs/connections/destinations/catalog/amazon-lambda) +Segment makes it easy to send your data to AWS Lambda (and lots of other destinations). Once you've tracked your data using our open source [libraries](https://segment.com/libraries) we'll translate and route your data to AWS Lambda in the format they understand. [AWS Lambda](https://aws.amazon.com/lambda/) lets you run code without provisioning or managing servers. You pay only for the compute time you consume - there is no charge when your code is not running. With Lambda, you can run code for virtually any type of application or backend service - all with zero administration. Just upload your code and Lambda takes care of everything required to run and scale your code with high availability. You can set up your code to automatically trigger from other AWS services or call it directly from any web or mobile app. +[Read more about AWS Lambda on the Segment blog](https://segment.com/blog/unleashing-the-power-of-raw-data-with-amazon-lambda/). + ## Getting Started {% include content/connection-modes.md %} diff --git a/src/connections/sources/catalog/libraries/server/object-api/index.md b/src/connections/sources/catalog/libraries/server/object-api/index.md index c4d9ad34fd..5ce7e2d102 100644 --- a/src/connections/sources/catalog/libraries/server/object-api/index.md +++ b/src/connections/sources/catalog/libraries/server/object-api/index.md @@ -148,19 +148,23 @@ This call sends a collection of "rooms". "rooms" becomes the table name in your - + - +

`collection`

Required		`collection` - Required String -

A string that represents the name of the collection. The collection name will become the table name in your data warehouse.

-

Collection must consist of lowercase letters and underscores and maximum of 100 characters. Can not begin or end with an underscore.

+ A string that represents the name of the collection. The collection name will become the table name in your data warehouse. + + Collection must consist of lowercase letters and underscores and maximum of 100 characters. Can not begin or end with an underscore. +

`objects`

`objects` Array -

A required array of objects describing the objects and properties being set.

-

Must consist of atleast one json object and a maximum of 10

+ A required array of objects describing the objects and properties being set. + + Must consist of at least one json object and a maximum of 10. +
@@ -169,20 +173,22 @@ Each object inside of the objects array must consist of the following parameters - + - +

`id`

Required		`id` - Required String -

The unique ID representing the object in the third party system.

-

Maximum of 100 characters.

+ The unique ID representing the object in the third party system. + Maximum of 100 characters.

`Properties`

Required		`Properties` - Required Object -

The object properties that represent the object. Example:

-

Each value could be a string (ISO dates are parsed and recognised as `isodate` type), an integer, or a float (json types).

-

Values cannot be lists or objects. Each value must be less 32kb in size.

+The object properties that represent the object. Example: + +Each value could be a string (ISO dates are parsed and recognised as `isodate` type), an integer, or a float (json types). + +Values cannot be lists or objects. Each value must be less 32kb in size.
@@ -229,7 +235,7 @@ curl https://objects.segment.com/v1/set \ ## FAQ -### Should I use the Objects API instead of `.identify()` and `.group()`? +### Should I use the Objects API instead of .identify() and .group()? No; you should continue use `analytics.identify` to identify your customers. We'll sync that to your data warehouse as `select * from project.users`. diff --git a/src/connections/spec/track.md b/src/connections/spec/track.md index 56eacfb2d1..6d436bb8f9 100644 --- a/src/connections/spec/track.md +++ b/src/connections/spec/track.md @@ -81,7 +81,7 @@ Here's a complete example of a `track` call: Every `track` call records a single user action. We call these "events". We recommend that you make your event names human-readable, so that everyone on your team (even you, after all that caffeine) can know what they mean instantly. -Do not use nondescript names like **Event 12** or **TMDropd**. Instead, use unique but recognizable names like **Video Recorded ** and **Order Completed**. +Do not use nondescript names like **Event 12** or **TMDropd**. Instead, use unique but recognizable names like **Video Recorded** and **Order Completed**. **We recommend event names built from a noun and past-tense verb.** For more information about best practices in event naming, check out our [Analytics Academy lesson on best practices for naming conventions for clean data](/academy/collecting-data/naming-conventions-for-clean-data/).