Merge branch 'develop' into dummy-form-test

Author: forstisabella

scripts/private-destination.js

@@ -17,6 +17,8 @@ require('dotenv').config();
 const PAPI_URL = "https://api.segmentapis.com"
 
 const PRIVATE_DESTINATIONS = yaml.load(fs.readFileSync(path.resolve(__dirname, `../src/_data/catalog/destinations_private.yml`)))
+const slugOverrides = yaml.load(fs.readFileSync(path.resolve(__dirname, `../src/_data/catalog/slugs.yml`)))
+
 const privateDests = PRIVATE_DESTINATIONS.items
 let private = []
 const getCatalog = async (url, page_token = "MA==") => {
@@ -37,25 +39,65 @@ const getCatalog = async (url, page_token = "MA==") => {
     return res.data
   } catch (err) {
     console.error("Error response:");
-    console.error(err.response.data);    // ***
-    console.error(err.response.status);  // ***
+    console.error(err.response.data); // ***
+    console.error(err.response.status); // ***
     console.error(err.response.headers); // ***
   } finally {
-    
+
   }
 }
 
+const slugify = (displayName) => {
+  let slug = displayName
+    .toLowerCase()
+    .replace(/\s+/g, '-')
+    .replace('-&-', '-')
+    .replace('/', '-')
+    .replace(/[\(\)]/g, '')
+    .replace('.', '-')
+
+  for (key in slugOverrides) {
+    let original = slugOverrides[key].original
+    let override = slugOverrides[key].override
+
+    if (slug == original) {
+      slug = override
+    }
+  }
+
+  return slug
+}
 
 const checkDestinationStatus = async (id) => {
   const res = await getCatalog(`${PAPI_URL}/catalog/destinations/${id}`)
   let destination = res.data.destinationMetadata
   return destination
 }
+
+const makeDestinationPublic = async (itemURL) => {
+  const catalogPath = path.resolve('src/', itemURL, 'index.md')
+  const f = fm(fs.readFileSync(catalogPath, 'utf8'));
+  const fmatter = f.attributes
+  fmatter.private = false
+  fmatter.hidden = false
+  let new_fm = ""
+  for (const property in fmatter) {
+    if (property == "versions") {
+      console.log(`Need to fix versions on this one`)
+    }
+    //console.log(`${property}: ${fmatter[property]}`);
+    new_fm += `${property}: ${fmatter[property]}\n`
+  }
+  const attr = `---\n${new_fm}\n---\n`
+  const body = f.body
+  const content = attr + body
+  fs.writeFileSync(catalogPath, content)
+}
 const getDestinationData = async (id) => {
   const res = await getCatalog(`${PAPI_URL}/catalog/destinations/${id}`)
   if (res == null) {
     return
-  } 
+  }
   let destination = res.data.destinationMetadata
   let settings = destination.options
   settings.sort((a, b) => {
@@ -69,11 +111,13 @@ const getDestinationData = async (id) => {
   })
   let actions = destination.actions
   let presets = destination.presets
+  let slug = slugify(destination.name)
+  let url = `connections/destinations/catalog/${slug}`
 
   // Force screen method into supportedMethods object
   destination.supportedMethods.screen = false
   // Set it true for LiveLike, per request
-  if (destination.id == '63e42b47479274407b671071'){
+  if (destination.id == '63e42b47479274407b671071') {
     destination.supportedMethods.screen = true
   }
 
@@ -93,8 +137,9 @@ const getDestinationData = async (id) => {
     id: destination.id,
     display_name: destination.name,
     name: destination.name,
-    slug: destination.slug,
+    slug: slugify(destination.name),
     previous_names: destination.previousNames,
+    url,
     website: destination.website,
     status: destination.status,
     logo: {
@@ -119,6 +164,7 @@ const getDestinationData = async (id) => {
     private.push(updatePrivateDest)
   } else {
     console.log(`${destination.name} is public and will be removed`)
+    makeDestinationPublic(url)
   }
 
   const options = {
@@ -148,12 +194,18 @@ const checkExistingStatus = async () => {
     let id = existingIds[i]
     let destination = await checkDestinationStatus(id)
     let status = destination.status
+    let slug = slugify(destination.name)
+    let url = `connections/destinations/catalog/${slug}`
+
+    
+    
 
     if (status === "PRIVATE_BETA") {
       // console.log(`${destination.name} is private`)
       newIds.push(id)
     } else {
-      // console.log(`${destination.name}is public`)
+      console.log(`src/connections/${destination.name}is public`)
+      makeDestinationPublic(url)
     }
   }
   return newIds

src/_data/catalog/destinations_private.yml

@@ -1,12 +1,13 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-03-30 
+# destination data last updated 2023-03-31 
 items:
   - id: 54521fd725e721e32a72eec1
     display_name: HubSpot
     name: HubSpot
     slug: hubspot
     previous_names:
       - HubSpot
+    url: connections/destinations/catalog/hubspot
     website: http://www.hubspot.com
     status: PRIVATE_BETA
     logo:
@@ -123,6 +124,7 @@ items:
     slug: intercom
     previous_names:
       - Intercom
+    url: connections/destinations/catalog/intercom
     website: http://intercom.com
     status: PRIVATE_BETA
     logo:
@@ -231,6 +233,7 @@ items:
     slug: pardot
     previous_names:
       - Pardot
+    url: connections/destinations/catalog/pardot
     website: http://pardot.com
     status: PRIVATE_BETA
     logo:
@@ -342,6 +345,7 @@ items:
     slug: salesforce
     previous_names:
       - Salesforce
+    url: connections/destinations/catalog/salesforce
     website: http://salesforce.com
     status: PRIVATE_BETA
     logo:
@@ -472,6 +476,7 @@ items:
     slug: webhooks
     previous_names:
       - Webhooks
+    url: connections/destinations/catalog/webhooks
     website: https://segment.com/docs/integrations/webhooks
     status: PRIVATE_BETA
     logo:
@@ -531,9 +536,10 @@ items:
   - id: 62b256147cbb49302d1486d0
     display_name: Heap Web (Actions)
     name: Heap Web (Actions)
-    slug: actions-heap-web
+    slug: actions-heap
     previous_names:
       - Heap Web (Actions)
+    url: connections/destinations/catalog/actions-heap
     website: https://heap.io/
     status: PRIVATE_BETA
     logo:
@@ -735,6 +741,7 @@ items:
     slug: actions-iterate
     previous_names:
       - Iterate Web (Actions)
+    url: connections/destinations/catalog/actions-iterate
     website: http://www.segment.com
     status: PRIVATE_BETA
     logo:
@@ -846,6 +853,7 @@ items:
     slug: actions-sabil
     previous_names:
       - Sabil
+    url: connections/destinations/catalog/actions-sabil
     website: https://sabil.io
     status: PRIVATE_BETA
     logo:
@@ -923,6 +931,7 @@ items:
     slug: actions-saleswings
     previous_names:
       - Saleswings (Actions)
+    url: connections/destinations/catalog/actions-saleswings
     website: >-
       https://www.saleswingsapp.com/lead-scoring-segment-com/?utm_campaign=segmentcatalogue&utm_medium=partnerlisting&utm_source=segment
     status: PRIVATE_BETA
@@ -1805,6 +1814,7 @@ items:
     slug: actions-livelike-cloud
     previous_names:
       - LiveLike
+    url: connections/destinations/catalog/actions-livelike-cloud
     website: https://livelike.com/
     status: PRIVATE_BETA
     logo:
@@ -2050,6 +2060,7 @@ items:
     slug: actions-emarsys
     previous_names:
       - Emarsys (Actions)
+    url: connections/destinations/catalog/actions-emarsys
     website: http://www.emarsys.com
     status: PRIVATE_BETA
     logo:
@@ -2350,9 +2361,10 @@ items:
   - id: 63ff8bae963d5cb4fc79f097
     display_name: Outfunnel
     name: Outfunnel
-    slug: outfunnel
+    slug: actions-outfunnel
     previous_names:
       - Outfunnel
+    url: connections/destinations/catalog/actions-outfunnel
     website: https://outfunnel.com/product-led-sales-platform/
     status: PRIVATE_BETA
     logo:
@@ -2822,6 +2834,7 @@ items:
     slug: actions-toplyne-cloud
     previous_names:
       - Toplyne Cloud Mode (Actions)
+    url: connections/destinations/catalog/actions-toplyne-cloud
     website: http://www.segment.com
     status: PRIVATE_BETA
     logo:

src/_data/catalog/slugs.yml

@@ -83,4 +83,20 @@
 - original: "qualtrics"
   override: "actions-qualtrics"
 - original: "tiktok-audiences"
-  override: "actions-tiktok-audiences"
+  override: "actions-tiktok-audiences"
+- original: "heap-web-actions"
+  override: "actions-heap"
+- original: "iterate-web-actions"
+  override: "actions-iterate"
+- original: "sabil"
+  override: "actions-sabil"
+- original: "saleswings-actions"
+  override: "actions-saleswings"
+- original: "livelike"
+  override: "actions-livelike-cloud"
+- original: "emarsys-actions"
+  override: "actions-emarsys"
+- original: "outfunnel"
+  override: "actions-outfunnel"
+- original: "toplyne-cloud-mode-actions"
+  override: "actions-toplyne-cloud"

src/_data/products.yml

@@ -138,7 +138,7 @@ items:
     business: true
     add-on: true
 - product_display_name: Regional Segment
-  slug: data-residency
+  slug: regional
   plan-note: "Regional Segment is available to customers on the Business Tier plan."
   plans:
     free: false

src/_includes/content/plan-grid.md

@@ -48,6 +48,6 @@
 {% else %}
 <p style="font-size:12px">{{productData.product_display_name}} is available for the listed account plans only.
 {% endif %}
-<br>See the <a href="https://segment.com/pricing">available plans</a>, or <a href="https://segment.com/help/contact/">contact us</a>.</p></div>
+<br>See the <a href="https://segment.com/pricing">available plans</a>, or <a href="https://segment.com/help/contact/">contact Support</a>.</p></div>
 </div>
 {% endif %}

src/connections/destinations/catalog/actions-google-analytics-4-web/index.md

@@ -61,3 +61,10 @@ Google may take [24-48 hours](https://support.google.com/analytics/answer/933379
 ### Data is not sent to Google
 
 Ensure that at least one mapping has been configured and enabled in the destination mappings for an event you want to send to Google Analytics. If no mappings are enabled, the destination does not send events.
+
+### Page Views
+
+The **Page Views** advanced setting prevents sending the `page_view` included in the gtag.js snippet, not Segment's `analytics.page()` event available in the Analytics.js snippet by default. If you enable this setting, once the page loads, two `page_view` events will still send to the GA4 SDK, one from the Segment snippet and one from the gtag.js snippet. If you see duplicate `page_view` events in your GA4 dashboard, you need to either:
+
+1. Disable the **Page Views** advanced setting (set it to *False*) so only Segment's `analytics.page()` sends to the GA4 SDK. Or,
+2.  Edit or disable the preset **Set Configuration Fields** mapping so only the `page_view` included in the gtag.js snippet sends to the GA4 SDK.

src/connections/destinations/catalog/actions-salesforce/index.md

@@ -20,7 +20,7 @@ Segment’s Salesforce (Actions) destination allows you to create, update or ups
 The Salesforce (Actions) destination provides the following benefits over the classic Salesforce destination:
 - **Fewer settings**. Data mapping for actions-based destinations happens during configuration, which eliminates the need for most settings.
 - **Clearer mapping of data**. Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to Salesforce.
-- **OAuth 2.0 support**. Authentication with Salesforce leverages OAuth 2.0 instead of a username/password.
+- **OAuth 2.0 support**. Authentication with Salesforce uses OAuth 2.0 instead of a username/password.
 - **Flexible match keys**. Upsert and update records based on any match key, including external IDs, record IDs, email and other object fields.
 - **Batch support**. Reduce Salesforce overages and rate-limit errors by batching your Segment data to Salesforce's Bulk API 2.0.
 
@@ -60,10 +60,58 @@ When using the `update` and `upsert` operations, you must specify the match key(
 
 If multiple fields are provided in the Record Matchers object, Segment uses an "OR" operator to query Salesforce for a record. If multiple records are returned upon query, no updates will be made. Segment will instead record a 300 error status for the request, and the request will not be retried. **Please use fields that result in unique records**.
 
-Please note Salesforce only allows querying on fields that have the "Filter" property. For example, we cannot query on the Case `Description` because it is not a filterable property. You can lookup the standard field properties in [Salesforce’s API documentation](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm){:target="_blank"} to determine if a field is available for querying.
+Please note Salesforce only allows querying on fields that have the "Filter" property. For example, Segment doesn't query on the Case `Description` because it is not a filterable property. You can lookup the standard field properties in [Salesforce’s API documentation](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm){:target="_blank"} to determine if a field is available for querying.
 
 ![the filter property](images/image1.png)
 
+## Migrate from Salesforce (Classic)
+
+To migrate from Salesforce (Classic), complete the following steps before May 31, 2023:
+
+1. Log in to your Segment workspace and review the copied settings in each new Salesforce (Actions) instance to ensure their accuracy. 
+2. Authenticate Segment with Salesforce with OAuth.
+3. Enable the Salesforce (Actions) destination & disable the Classic destination.
+
+> info "Authenticate with Salesforce"
+> Salesforce (Actions) requires OAuth based authentication while Salesforce Classic uses tokens and credentials. Because of this, Segment can't migrate authentication credentials. Your workspace owner must login and configure OAuth Authentication for each Salesforce (Actions) destinations that were migrated.
+
+If you have more than one Salesforce instance connected to Segment, repeat these three steps for each instance. 
+
+Keep the following in mind as you begin to use Salesforce (Actions):
+- Salesforce (Actions) supports batching. The workspace owner can edit the enabled-batching field manually for any of the mappings. This setting is disabled by default.
+- Salesforce (Actions) doesn’t support Delete CRUD operations on Custom Object. Custom Objects with CRUD the operation set to `delete` are not migrated.
+- Sending Identify events to Salesforce (Classic) results in a create or update operation for Leads, and maps properties from `event.traits` Salesforce (Actions) does not support this behavior. By default, the migration tool maps only a subset of the most used Lead properties as mentioned below. The workspace owner must map any additional Salesforce properties or Custom properties manually.
+
+Review the tables below to see how settings from Salesforce (Classic) were migrated to Salesforce (Actions).
+
+### Leads
+
+| Salesforce (Actions) property | Migrated behavior                                                                                             |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| Record Matchers               | Uses **Custom Lead Lookup** fields from Salesforce (Classic), if available, or **Email** as a fallback value. |
+| Name                          | Appears within the **Other Fields** property, defaults to `traits.name`.                                      |
+| Phone                         | Appears within the **Other Fields** property, defaults to `coalesce(traits.phone, traits.phoneNumber)`.       |
+| Title                         | Appears within the **Other Fields** property, defaults to `coalesce(traits.address.title, traits.position)`.  |
+| Website                       | Appears within the **Other Fields** property, defaults to `traits.website`.                                   |
+| Description                   | Appears within the **Other Fields** property, defaults to `traits.description`.                               |
+| Lead Source                   | Appears within the **Other Fields** property, defaults to `traits.leadSource`.                                |
+
+### Account
+
+| Salesforce (Actions) property | Migrated behavior                                                                                             |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| Billing Street | Created only if the **Send Address as Billing Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.street, traits.street)`. |
+| Billing City | Created only if the **Send Address as Billing Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.city, traits.city)`. |
+| Billing State | Created only if the **Send Address as Billing Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.state, traits.state)`. |
+| Billing Country | Created only if the **Send Address as Billing Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.country, traits.country)`. |
+| Billing Postal Code | Created only if the **Send Address as Billing Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.postalCode, traits.postalCode)`. |
+| Shipping Street | Created only if the **Send Address as Shipping Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.street, traits.street)`. |
+| Shipping City | Created only if the **Send Address as Shipping Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.city, traits.city)`. |
+| Shipping State | Created only if the **Send Address as Shipping Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.state, traits.state)`. |
+| Shipping Country | Created only if the **Send Address as Shipping Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.country, traits.country)`. |
+| Shipping Postal Code | Created only if the **Send Address as Shipping Address** property is set in Salesforce (Classic). Defaults to `coalesce(traits.address.postalCode, traits.postalCode)`. |
+
+
 ## FAQ
 
 ### How do I enable a sandbox instance?
@@ -72,7 +120,7 @@ To send data to a Salesforce sandbox instance, navigate to **Settings > Advanced
 Your Salesforce sandbox username appends the sandbox name to your Salesforce production username. For example, if a username for a production org is `[email protected]` and the sandbox is named `test`, the username to log in to the sandbox is `[email protected]`.
 
 ### How do I add custom fields?
-Custom fields can be included in the Other Fields mapping. Custom fields must be predefined in your Salesforce account and should end with `__c` (i.e. `My_Custom_Field__c`). Please include the `__c` in your mapping.
+Custom fields can be included in the Other Fields mapping. Custom fields must be predefined in your Salesforce account and should end with `__c` (for example, `My_Custom_Field__c`). Please include the `__c` in your mapping.
 
 You can see Salesforce API names in Salesforce under **Setup > Objects and Fields > Object Manager > Select your object > Fields & Relationships > FIELD NAME**.
 

src/connections/destinations/catalog/actions-wisepops/index.md

@@ -3,7 +3,6 @@ title: Wisepops Destination
 hide-boilerplate: true
 hide-dossier: true
 id: 6372e1e36d9c2181f3900834
-private: true
 ---
 
 {% include content/plan-grid.md name="actions" %}