Merge pull request #1954 from segmentio/develop

Release 1.39.1

Author: markzegarelli

src/connections/destinations/catalog/google-cloud-function/index.md

@@ -21,17 +21,18 @@ Before you can process events from Segment, you must provide a Google Cloud Func
 
 1. Go to https://cloud.google.com/functions.
 2. Click **VIEW CONSOLE**.
-   ![](images/gcloud1.png)
-
 3. Select a project.
 4. Click **CREATE FUNCTION**.
-   ![](images/gcloud2.png)
 5. Enter a name for your function, and choose how much memory the function can use.
-7. In the **Trigger** field, select `HTTP`. Save the `URL` GCP gives you. You'll use this to configure the Segment destination later.
-8. Choose how you'll provide the function's code (in the **Source code** field) and what language the code is written in (in the **Runtime** field).
-9. Enter the name of the function as you defined it in your code, in the **Function to execute** field.
-10. Click **Create** to save your settings and create the Google Cloud Function.
-![](images/gcloud3.png)
+6. In the **Trigger** field, select `HTTP`. Save the `URL` GCP gives you. You'll use this to configure the Segment destination later.
+7. Choose how you'll provide the function's code (in the **Source code** field) and what language the code is written in (in the **Runtime** field).
+8. Enter the name of the function as you defined it in your code, in the **Function to execute** field.
+9.  Click **Create** to save your settings and create the Google Cloud Function.
+
+
+### Test the function
+
+Segment recommends that you use the Debugger of the source you intend to connect to the Google Cloud Function destination to inspect the request body of the incoming event. This allows you to build handlers in your function based on accurate incoming data. For more information, see [Testing Connections](/docs/connections/test-connections/). 
 
 ## Configure the Google Cloud Function Destination
 
@@ -44,7 +45,7 @@ Once you create the Google Cloud Function, you can set up a Segment destination
 3. Click **Configure Google Cloud Function**.
 4. Enter the destination settings for this GCF destination.
 
-| Setting  | Description         |
-| -------- | ------------------- |
-| **HTTP Trigger**  | The URL given under the `Trigger` section when you created the Google Cloud Function.    |
+| Setting                | Description                                                                                                                                                                                                                                                           |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **HTTP Trigger**       | The URL given under the `Trigger` section when you created the Google Cloud Function.                                                                                                                                                                                 |
 | **API Key** (optional) | A string to identify that a request is coming from Segment, if required by the function. <br><br>The API key is injected in the `Authorization` header as a [basic authorization header](https://en.wikipedia.org/wiki/Basic_access_authentication) without password. |

src/connections/sources/catalog/libraries/mobile/ios/ios-faqs.md

@@ -243,7 +243,7 @@ Analytics.shared().track("Clicked Button", properties: nil, options: ["context":
 
 ## How can I get the user’s IDFA?
 
-Some destinations, especially mobile attribution tools (e.g. Kochava), require the IDFA (identifier for advertisers). The IDFA appears in Segment calls in the debugger as `context.device.advertisingId`. To capture this value with Analytics-iOS, follow the steps in [Ad-tracking and IDFA](/docs/connections/sources/catalog/libraries/mobile/ios#ad-tracking-and-idfa).  Remember that Apple now requires that the user consent to your tracking before you can collect the IDFA.
+Some destinations, especially mobile attribution tools (for example, [Kochava](https://www.kochava.com/){:target="_blank"}), require the IDFA (identifier for advertisers). The IDFA appears in Segment calls in the debugger as `context.device.advertisingId`. To capture this value with Analytics-iOS, follow the steps in [Ad-tracking and IDFA](/docs/connections/sources/catalog/libraries/mobile/ios#ad-tracking-and-idfa).  Remember that Apple now requires that the user consent to your tracking before you can collect the IDFA.
 
 
 

src/connections/spec/ecommerce/v2.md

@@ -2633,7 +2633,7 @@ This event supports the following semantic properties:
 
 Example:
 ```js
-analytics.track('Cart Viewed', {
+analytics.track('Cart Shared', {
   share_via: 'email',
   share_message: 'Hey, check out this item',
   recipient: '[email protected]',

src/connections/spec/mobile.md

@@ -6,11 +6,13 @@ One of the core components of the Segment [Spec](/docs/connections/spec/) is the
 
 By standardizing the events that comprise the core **mobile application lifecycle** and associated **mobile campaign and referral events**, Segment and our partners can, wherever possible, automatically collect and forward these events on your behalf and build downstream destinations which take full advantage of the semantic meaning associated with these events and their properties.
 
-**Note:** If you're already collecting similar events, we recommend migrating to these event names so that you can take advantage of available features in our destinations which depend on the spec as they become available.
+> info ""
+>  If you're already collecting similar events, we recommend migrating to these event names so that you can take advantage of available features in our destinations which depend on the spec as they become available.
 
-These events pair nicely with our [ecommerce spec](/docs/connections/spec/ecommerce/v2/) for mobile marketplaces to take full advantage of features like dynamic ads in Facebook and the ability to take full advantage of server-side destinations with Mobile Attribution Platforms like Tune and Kochava.
+These events pair nicely with our [ecommerce spec](/docs/connections/spec/ecommerce/v2/) for mobile marketplaces to take full advantage of features like dynamic ads in Facebook and the ability to take full advantage of server-side destinations with Mobile Attribution Platforms like [Tune](https://www.tune.com/){:target="_blank"} and [Kochava](https://www.kochava.com/){:target="_blank"}.
 
-**Note** Per our [Privacy Policy](https://segment.com/legal/privacy/#sensitive-personal-information) and applicable terms, don't send us sensitive personal information about your users. Certain features from Segment and our partners allow you to opt-in to automatically track data (for example: Application Installed or Deep Link Clicked). When working with these features and Segment in general, be cognizant of the data that is being tracked to ensure its matching both your obligations under your agreement with Segment and the privacy expectations of your users.
+> info ""
+>  Per the [Privacy Policy](https://segment.com/legal/privacy/#sensitive-personal-information) and applicable terms, don't send us sensitive personal information about your users. Certain features from Segment and our partners allow you to opt-in to automatically track data (for example: Application Installed or Deep Link Clicked). When working with these features and Segment in general, be cognizant of the data that is being tracked to ensure its matching both your obligations under your agreement with Segment and the privacy expectations of your users.
 
 ## Overview of Events