Inflection Source (#4901)

* Inflection Source

* Edits and formatting

* add frontmatter and hide

* unhide and add id (integration is going live)

* add slug overrides to fix the integrations from being hidden (#4952)

* Small spelling fix

- add comma after "cloud mode"
- fix spelling of "anononymous" to "anonymous"

* catalog update

---------

Co-authored-by: markzegarelli <[email protected]>
Co-authored-by: Thomas Gilbert <[email protected]>
Co-authored-by: Sarah Rudy <[email protected]>
Co-authored-by: rchinn-segment <[email protected]>

Author: 5 people

src/_data/catalog/destinations.yml

@@ -27408,7 +27408,7 @@ items:
   display_name: Google Analytics 4 Cloud
   name: Google Analytics 4 Cloud
   slug: google-analytics-4-cloud
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
@@ -69849,14 +69849,14 @@ items:
 - id: 63bedc136a8484a53739e013
   display_name: VWO Cloud Mode (Actions)
   name: VWO Cloud Mode (Actions)
-  slug: vwo-cloud-mode-actions
-  hidden: true
+  slug: actions-vwo-cloud
+  hidden: false
   endpoints:
   - US
   regions:
   - us-west-2
   - eu-west-1
-  url: connections/destinations/catalog/vwo-cloud-mode-actions
+  url: connections/destinations/catalog/actions-vwo-cloud
   previous_names:
   - VWO Cloud Mode (Actions)
   website: https://vwo.com
@@ -70250,6 +70250,173 @@ items:
       timestamp:
         '@path': $.timestamp
     trigger: type = "track"
+- id: 637c192eba61b944e08ee158
+  display_name: VWO Web Mode (Actions)
+  name: VWO Web Mode (Actions)
+  slug: actions-vwo-web
+  hidden: false
+  endpoints:
+  - US
+  regions:
+  - us-west-2
+  - eu-west-1
+  url: connections/destinations/catalog/actions-vwo-web
+  previous_names:
+  - VWO Web Mode (Actions)
+  website: https://vwo.com
+  status: PUBLIC_BETA
+  categories:
+  - A/B Testing
+  - Heatmaps & Recordings
+  logo:
+    url: https://cdn.filepicker.io/api/file/o9X4IJO1RDegnGVmfje0
+  mark:
+    url: https://cdn.filepicker.io/api/file/L6U6f3KrRoScOQbUDMKj
+  methods:
+    track: true
+    identify: true
+    group: true
+    alias: true
+    screen: false
+    page: true
+  platforms:
+    browser: true
+    mobile: false
+    server: false
+    warehouse: false
+  components: []
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  replay: false
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: true
+      mobile: false
+      server: false
+  settings:
+  - name: addSmartcode
+    type: boolean
+    defaultValue: true
+    description: >-
+      When enabled, Segment will load the VWO SmartCode onto the webpage. When
+      disabled, you will have to manually add SmartCode to your webpage. The
+      setting is enabled by default, however we recommended manually adding
+      SmartCode to the webpage to avoid flicker issues.
+    required: true
+    label: Add Asynchronous SmartCode
+  - name: libraryTolerance
+    type: number
+    defaultValue: 2500
+    description: >-
+      The maximum amount of time (in milliseconds) to wait for VWO’s full
+      library to be downloaded before simply displaying your original page.
+    required: true
+    label: Library Tolerance
+  - name: settingsTolerance
+    type: number
+    defaultValue: 2000
+    description: >-
+      The maximum amount of time (in milliseconds) to wait for test settings
+      before VWO will simply display your original page.
+    required: true
+    label: Settings Tolerance
+  - name: useExistingJquery
+    type: boolean
+    defaultValue: false
+    description: >-
+      If your page already includes JQuery, you can set this to “true”.
+      Otherwise, VWO will include JQuery onto the page for you. VWO needs JQuery
+      on the page to function correctly. 
+    required: true
+    label: Use Existing JQuery
+  - name: vwoAccountId
+    type: number
+    defaultValue: 0
+    description: Your VWO account ID, used for fetching your VWO async smart code.
+    required: true
+    label: VWO Account ID
+  actions:
+  - id: 6uTbf9uHvZBJ3YnMmFHWtZ
+    name: Track Event
+    slug: trackEvent
+    description: Sends Segment's track event to VWO
+    platform: WEB
+    hidden: false
+    defaultTrigger: type = "track"
+    fields:
+    - id: jNmcxw9HaJsSVJUp54bW9d
+      sortOrder: 0
+      fieldKey: eventName
+      label: Name
+      type: STRING
+      description: Name of the event.
+      placeholder: ''
+      defaultValue:
+        '@path': $.event
+      required: true
+      multiple: false
+      choices: null
+      dynamic: false
+      allowNull: false
+    - id: 7nTcRCU7denYUgiFAqxr5x
+      sortOrder: 1
+      fieldKey: properties
+      label: Properties
+      type: OBJECT
+      description: >-
+        JSON object containing additional properties that will be associated
+        with the event.
+      placeholder: ''
+      defaultValue:
+        '@path': $.properties
+      required: false
+      multiple: false
+      choices: null
+      dynamic: false
+      allowNull: false
+  - id: tR1J9N9e3vk4XtqGjUfTSm
+    name: Identify User
+    slug: identifyUser
+    description: Sends Segment's page event to VWO
+    platform: WEB
+    hidden: false
+    defaultTrigger: type = "identify"
+    fields:
+    - id: nL8QQNucajeL5tiekANaDm
+      sortOrder: 0
+      fieldKey: attributes
+      label: Attributes
+      type: OBJECT
+      description: >-
+        JSON object containing additional attributes that will be associated
+        with the user.
+      placeholder: ''
+      defaultValue:
+        '@path': $.traits
+      required: true
+      multiple: false
+      choices: null
+      dynamic: false
+      allowNull: false
+  presets:
+  - actionId: 6uTbf9uHvZBJ3YnMmFHWtZ
+    name: Track Event
+    fields:
+      eventName:
+        '@path': $.event
+      properties:
+        '@path': $.properties
+    trigger: type = "track"
+  - actionId: tR1J9N9e3vk4XtqGjUfTSm
+    name: Identify User
+    fields:
+      attributes:
+        '@path': $.traits
+    trigger: type = "identify"
 - id: 5d25d6e0885427000195bf80
   display_name: WalkMe
   name: WalkMe

src/_data/catalog/regional-supported.yml

@@ -541,7 +541,7 @@ sources:
       - us
   - id: glwy6LwOVo
     display_name: Inflection
-    hidden: true
+    hidden: false
     slug: inflection
     url: connections/sources/catalog/cloud-apps/inflection
     regions:

src/_data/catalog/slugs.yml

@@ -7,6 +7,10 @@ sources:
   - original: "shopify-by-littledata"
     override: "shopify-littledata"
 destinations:
+  - original: "vwo-cloud-mode-actions"
+    override: "actions-vwo-cloud"
+  - original: "vwo-web-mode-actions"
+    override: "actions-vwo-web"
   - original: "talon-one"
     override: "talonone"
   - original: "google-adwords-remarketing-lists-customer-match"

src/_data/catalog/sources.yml

@@ -911,7 +911,7 @@ items:
     isCloudEventSource: true
     slug: inflection
     url: connections/sources/catalog/cloud-apps/inflection
-    hidden: true
+    hidden: false
     regions:
       - us
     endpoints:
@@ -1595,7 +1595,7 @@ items:
     isCloudEventSource: false
     slug: postgres
     url: connections/sources/catalog/cloud-apps/postgres
-    hidden: false
+    hidden: true
     regions:
       - us
     endpoints:

src/connections/destinations/catalog/clevertap/index.md

@@ -29,7 +29,7 @@ All other traits will be sent to CleverTap as custom attributes. The default log
 
 
 > info ""
-> In cloud mode CleverTap uses Segment anononymous ID as the CleverTap ID.
+> In cloud mode, CleverTap uses Segment anonymous ID as the CleverTap ID.
 > In device mode, CleverTap ignores the anonymous ID and CleverTap injects its own ID.
 
 ## Alias

src/connections/sources/catalog/cloud-apps/inflection/index.md

@@ -1,4 +1,64 @@
 ---
-title: 'Inflection Source'
-hidden: true
----
+title: Inflection Source
+id: glwy6LwOVo
+---
+[Inflection](https://inflection.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) provides a B2B marketing automation platform for product-led growth companies.
+
+This is an [Event Cloud Source](/docs/sources/#event-cloud-sources) which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.
+
+This source is maintained by Inflection. For any issues with the source, [contact their Support team](mailto:[email protected]).
+
+## Getting Started
+
+1. From the [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog) in your workspace, click **Add Source**.
+2. Search for "Inflection" in the Sources Catalog, select Inflection, and click **Add Source**.
+3. On the next screen, give the Source a nickname configure any other settings.
+4. Click **Add Source** to save your settings.
+5. Copy the Write key from the Segment UI and log in to your Inflection account - navigate to Connections > Add a new connection > Segment Integration > Select Source > and paste the write key in the Segment as Destination Field.
+
+## Stream 
+
+Inflection uses its stream Source component to send Segment event data. It uses a server-side (select from `track`, `identify`, `page`, `group`) methods to send data to Segment. 
+
+Inflection passes the `userId` associated with the email recipient as the `userId`. In cases where Inflection does not have an associated `userId` value, Inflection passes `personId` to Segment as an `anonymousId`. When Inflection receives the `userId` for the email it sends an Identify call with both the `personId` and `userId` to Segment.
+
+## Events
+
+The table below lists events that Inflection sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations. Inflection includes the `userId` if available.
+
+| Event Name                        | Description                                              |
+| --------------------------------- | -------------------------------------------------------- |
+| Email Delivered                   | Email was sent successfully                              |
+| Email Opened                      | Prospect opened the email                                |
+| Email Unique Opens                | Unique email open by a prospect                          |
+| Email Bounced                     | Email servers rejected the email                         |
+| Email Reported as Spam            | Prospect reported the email as spam                      |
+| Link Clicked                      | Prospect clicked the tracking link                       |
+| Unique Link Click                 | Unique tracking link click by a prospect                 |
+| Unique Link Click per Unique Open | Unique tracking link click per unique open by a prospect |
+| Email Unsubscribed                | Prospect clicked the unsubscribe link                    |
+
+## Event Properties
+
+The table below list the properties included in the events listed above.
+
+| Property Name     | Description                                        |
+| ----------------- | -------------------------------------------------- |
+| `event`           | Email event type                                   |
+| `userId`          | Prospect email ID                                  |
+| `email_id`        | ID of the email                                    |
+| `campaign_id`     | Campaign ID                                        |
+| `campaign_run_id` | Campaign Run ID                                    |
+| `campaign_name`   | Campaign Name                                      |
+| `email_subject`   | Subject line of the email                          |
+| `email_link_url`  | URL of the link clicked                            |
+| `is_unique_open`  | Unique email open by a prospect (true or false)    |
+| `is_unique_click` | Unique tracking link by a prospect (true or false) |
+
+## Adding Destinations
+
+Now that your Source is set up, you can connect it with Destinations.
+
+Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the [Event Delivery](/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting.
+
+If there are any issues with how the events are arriving to Segment, [contact the Inflection support team](mailto:[email protected]).