Merge branch 'master' into DOC-204_papi_catalog

markzegarelli · web-flow · commit fd3f8285a156 · 2021-06-23T17:17:27.000-07:00
diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml
@@ -5246,9 +5246,95 @@ items:
     summary: accepts device-mode data only from Analytics.js.
     cmode_type: device-only
     case: '2'
+settings:
+  - name: accountNumber
+    display_name: Account Number
+    type: STRING
+    deprecated: false
+    required: true
+    string_validators:
+      regexp: ^\d+$
+    description: >-
+      You can find your Account Number by going to the [Crazy Egg Setup
+      Instructions](http://www.crazyegg.com/instructions) and clicking **I use
+      Segment.** Your account number will appear in bold. It should be a series
+      of numbers, like `00938301`.
+    settings: []
 - display_name: Crisp
-  name: Crisp
   slug: crisp
+  name: catalog/destinations/crisp
+  url: connections/destinations/catalog/crisp
+  description: Crisp is an all-in-one platform to connect with your customers.
+  hidden: false
+  status: PUBLIC
+  previous_names:
+  - Crisp
+  logo:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/db6f4c77-470b-429c-b77a-77b1228ade63.svg
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/45cad587-47d4-4ada-a09d-c730242af27e.svg
+  categories:
+  - CRM
+  - Customer Success
+  - Email Marketing
+  - Marketing Automation
+  methods:
+    alias: false
+    group: false
+    identify: true
+    page_view: false
+    track: true
+  components:
+  - type: WEB
+  platforms:
+    browser: true
+    server: true
+    mobile: true
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  connection_modes:
+    device:
+      web: true
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: false
+      server: false
+    summary: accepts device-mode data only from Analytics.js.
+    cmode_type: device-only
+    case: '2'
+  settings:
+  - name: apiKey
+    display_name: API Key
+    type: STRING
+    deprecated: false
+    required: true
+    string_validators:
+      regexp: '^.{8,}$'
+    description: >-
+      The API key is autoset when linking Crisp with Segment. Click "Connect to
+      Segment" in the Crisp plugins section
+    settings: []
+  - name: websiteId
+    display_name: Website ID
+    type: STRING
+    deprecated: false
+    required: false
+    string_validators:
+      regexp: ''
+    description: ''
+    settings: []
+- display_name: Criteo App & Web Events
+  slug: criteo-app-web-events
+  name: catalog/destinations/criteo
+  url: connections/destinations/catalog/criteo-app-web-events
+  description: >-
+    Criteo uses state of the art machine learning to transform digital
+    advertising into a personal experience. Please Note: Our web integration
+    with Criteo is currently in Beta.
   hidden: false
   url: connections/destinations/catalog/crisp
   previous_names:
@@ -13107,6 +13193,78 @@ items:
       Cloud Mode or send track events from one of our server side libraries. Use
       these fields to map your Segment track event names to Marketo Custom
       Activities. We'll only send events that you specify.
+    settings:
+    - name: marketoActivityId
+      display_name: Marketo Custom Activity ID
+      type: STRING
+      deprecated: false
+      required: true
+      string_validators:
+        regexp: '^[0-9]+$'
+      description: Enter the Marketo Custom Activity ID. This must be an Integer.
+      settings: []
+    - name: segmentProperty
+      display_name: Marketo Fields
+      type: MIXED
+      deprecated: false
+      required: false
+      description: Map your Segment properties to the Marketo Activity Fields
+      settings:
+      - name: segmentProperty
+        display_name: Segment Property Name
+        type: STRING
+        deprecated: false
+        required: true
+        string_validators:
+          regexp: ''
+        description: >-
+          Enter the Segment Property Name. This is case sensitive so make sure
+          the name matches exactly how you are passing it in your .track() call.
+        settings: []
+      - name: marketoAttributeName
+        display_name: Marketo Field Name
+        type: STRING
+        deprecated: false
+        required: true
+        string_validators:
+          regexp: ''
+        description: >-
+          Enter the Marketo Field name. Make sure to copy and paste the exact
+          API Name for your field as it appears in Marketo.
+        settings: []
+      - name: marketoAttributeType
+        display_name: Marketo Field Type
+        type: SELECT
+        deprecated: false
+        required: true
+        select_validators:
+          select_options:
+          - string
+          - boolean
+          - number
+          - date
+        description: Enter the Marketo Field type.
+        settings: []
+      - name: primaryKey
+        display_name: Set as Primary Key
+        type: BOOLEAN
+        deprecated: false
+        required: false
+        description: Mark this property as the Primary field in Marketo.
+        settings: []
+    - name: event
+      display_name: Segment Event Name
+      type: STRING
+      deprecated: false
+      required: true
+      string_validators:
+        regexp: ''
+      description: Enter the Segment Event Name.
+      settings: []
+  - name: traits
+    display_name: Marketo Custom Fields
+    type: MIXED
+    deprecated: false
     required: false
   - name: privateKey
     type: string
@@ -17102,7 +17260,120 @@ items:
     description: >-
       Use these fields to map your Segment event names to Responsys Supplemental
       Tables. We'll only send events and properties that you specify.
-    required: false
+    settings:
+    - name: columns
+      display_name: Columns
+      type: MIXED
+      deprecated: false
+      required: false
+      description: Map your Segment properties to Responsys Columns
+      settings:
+      - name: primaryKey
+        display_name: Set as Primary Key
+        type: BOOLEAN
+        deprecated: false
+        required: false
+        description: Mark this property as a Primary Key in Responsys.
+        settings: []
+      - name: columns
+        display_name: Segment Property Name
+        type: STRING
+        deprecated: false
+        required: true
+        string_validators:
+          regexp: ''
+        description: Enter the Segment Property Name.
+        settings: []
+      - name: fieldName
+        display_name: Responsys Column Name
+        type: STRING
+        deprecated: false
+        required: true
+        string_validators:
+          regexp: ''
+        description: Enter the Responsys column name.
+        settings: []
+      - name: fieldType
+        display_name: Responsys Column Type
+        type: SELECT
+        deprecated: false
+        required: true
+        select_validators:
+          select_options:
+          - CHAR
+          - STR25
+          - STR100
+          - STR500
+          - STR4000
+          - Number
+          - INTEGER
+          - TIMESTAMP
+        description: Enter the Responsys column type.
+        settings: []
+    - name: mapEmail
+      display_name: Map Email
+      type: BOOLEAN
+      deprecated: false
+      required: false
+      description: >-
+        Check this box if you want to automatically create and or map Segment's
+        `email` property (in `context.traits.email` or `properties.email`) as a
+        column in Responsys. Highly **recommended** if you are calling
+        `.identify()` with an `email` trait for anonymous users without
+        `userId`s.
+      settings: []
+    - name: mapUserId
+      display_name: Map Segment UserId
+      type: BOOLEAN
+      deprecated: false
+      required: false
+      description: >-
+        Check this box if you want to automatically create and or map Segment's
+        `userId` field as a column in Responsys. Highly **recommended** if you
+        want to connect records in your Profile Lists/Extension Tables with
+        records in this Supplemental Table.
+      settings: []
+    - name: folderName
+      display_name: Responsys Folder Name
+      type: STRING
+      deprecated: false
+      required: true
+      string_validators:
+        regexp: ''
+      description: >-
+        Optional. Enter a Responsys Folder Name where this Supplemental exists
+        or where you'd like one to be created. If this input is left blank, we
+        will fallback on the default Folder Name you've provided at the top
+        level settings.
+      settings: []
+    - name: suppName
+      display_name: Responsys Supplemental Table Name
+      type: STRING
+      deprecated: false
+      required: true
+      string_validators:
+        regexp: ''
+      description: Enter a Responsys Supplemental Table Name.
+      settings: []
+    - name: event
+      display_name: Segment Event Name
+      type: STRING
+      deprecated: false
+      required: true
+      string_validators:
+        regexp: ''
+      description: Enter the Segment Event Name.
+      settings: []
+    - name: useSegmentMsgId
+      display_name: Use Segment Message ID
+      type: BOOLEAN
+      deprecated: false
+      required: false
+      description: >-
+        Use Segment's `messageId` as one of the four Primary Keys to easily
+        ensure that you do not overwrite historical records in your Supplemental
+        Tables.
+      settings: []
   - name: folderName
     type: string
     defaultValue: ''
diff --git a/src/connections/destinations/catalog/crisp/index.md b/src/connections/destinations/catalog/crisp/index.md
@@ -1,4 +1,50 @@
 ---
-title: 'Crisp Destination'
-hidden: true
---- %}
+ title: Crisp Destination
+rewrite: true
+---
+[Crisp](https://crisp.chat/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is an all-in-one solution to communicate with your customers using text-messaging.
+
+This destination is maintained by Crisp. For any issues with the destination, [contact the Crisp Support team](mailto:support@crisp.chat).
+
+## Getting Started
+
+{% include content/connection-modes.md %} 
+
+1. Go to the [Crisp Plugins page](app.crisp.chat).
+2. Search for the "Segment" plugin, click **Connect to Segment**.
+3. The Segment App opens in a new window. Log in to authenticate the connection from Crisp.
+4. Select the Workspace and Source to connect with Crisp.
+
+## Supported methods
+
+Crisp supports the following methods, as specified in the [Segment Spec](/docs/connections/spec/).
+
+### Identify
+
+Send [Identify](/docs/connections/spec/identify/) calls to create or update a User profile. The `email` trait is required to create new Users. For example:
+
+```js
+analytics.identify('userId123', {
+  name: 'John Doe',
+  email: 'john.doe@segment.com',
+  phone: '012346789',
+  avatar: 'https://pbs.twimg.com/profile_images/834424630630817795/TfyS4uXb_400x400.jpg'
+});
+```
+
+### Track
+
+Crisp adds [Track](/docs/connections/spec/track/) events to the User's profile events stream.
+
+```js
+analytics.track('Completed Purchase', {
+  revenue: 42.99,
+  shippingMethod: '2-day',
+  category: 'Conversion'
+});
+```
+> warning ""
+> Send an Identify call for any user who triggers Track calls. If Crisp receives a Track call for an unknown `userId`, the call is dropped.
+
+
+
