diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index dfcb7c0c7e..4cf8c20b5f 100644 --- a/src/_data/catalog/destination_categories.yml +++ b/src/_data/catalog/destination_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination categories last updated 2021-11-23 +# destination categories last updated 2021-11-25 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml index 3560229429..9207cfade7 100644 --- a/src/_data/catalog/destinations.yml +++ b/src/_data/catalog/destinations.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2021-11-23 +# destination data last updated 2021-11-25 items: - display_name: 2mee name: 2mee @@ -2799,6 +2799,54 @@ items: description: You can find your Site ID in your Auryc account. required: true label: Site ID +- display_name: AutopilotApp + name: AutopilotApp + slug: autopilotapp + hidden: false + url: connections/destinations/catalog/autopilotapp + previous_names: + - AutopilotApp + website: https://autopilotapp.com/ + status: PUBLIC_BETA + categories: + - Email Marketing + - Marketing Automation + logo: + url: >- + https://public-segment-devcenter-production.s3.amazonaws.com/b5eba5a9-10f3-47eb-8de3-416d8663caf6.svg + mark: + url: >- + https://public-segment-devcenter-production.s3.amazonaws.com/ea4945e2-eaaa-44ac-aa87-b042272d35e3.svg + methods: + track: true + identify: true + group: false + alias: false + page: false + platforms: + browser: true + mobile: true + server: true + components: [] + browserUnbundlingSupported: false + browserUnbundlingPublic: false + replay: false + connection_modes: + device: + web: false + mobile: false + server: false + cloud: + web: false + mobile: false + server: false + settings: + - name: apiKey + type: string + defaultValue: '' + description: Enter your autopilot API key here + required: true + label: API Key - display_name: AutopilotHQ name: AutopilotHQ slug: autopilothq diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index 30ffd0785b..03b3789fa7 100644 --- a/src/_data/catalog/source_categories.yml +++ b/src/_data/catalog/source_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# source cateogries last updated 2021-11-23 +# source cateogries last updated 2021-11-25 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml index 9eddc39fb2..5aac4b37cb 100644 --- a/src/_data/catalog/sources.yml +++ b/src/_data/catalog/sources.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# sources last updated 2021-11-23 +# sources last updated 2021-11-25 items: - display_name: .NET slug: net diff --git a/src/_data/catalog/warehouse.yml b/src/_data/catalog/warehouse.yml index e20c10431e..8f77ef1a84 100644 --- a/src/_data/catalog/warehouse.yml +++ b/src/_data/catalog/warehouse.yml @@ -18,7 +18,7 @@ items: description: >- The AWS S3 destination provides a more secure way to store data in your AWS S3 buckets. url: connections/storage/catalog/aws-s3 - status: PUBLIC_BETA + status: PUBLIC logo: url: 'https://d3hotuclm6if1r.cloudfront.net/logos/amazon-s3-default.svg' mark: diff --git a/src/config-api/index.md b/src/config-api/index.md index 4588a993e4..2250418582 100644 --- a/src/config-api/index.md +++ b/src/config-api/index.md @@ -2,6 +2,11 @@ title: Config API Overview --- +> info "The Segment Public API: Beta Release" +> The Segment Public API is available in Public Beta. This new API features more consistent endpoints, improved error handling and reporting, support for pagination, and more. +> +> See the [Segment Public API documentation](https://api.segmentapis.com/docs/){:target="_blank"} for more information. + The Config API enables you to programmatically manage Segment workspaces, sources, destinations and more. With the API you can: * List all your workspace Sources and Destinations to see how data flows through Segment diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md index cc2a30ab3d..78e224563c 100644 --- a/src/connections/destinations/catalog/actions-amplitude/index.md +++ b/src/connections/destinations/catalog/actions-amplitude/index.md @@ -138,7 +138,7 @@ Build your own subscriptions! Combine supported [triggers](/docs/connections/des - [Map User](#map-user) - [Group Identify User](#group-identify-user) -You can see the Segment event fields Amplitude accepts for each action in the Actions subscription set up page. Combine these +You can see the Segment event fields Amplitude accepts for each action in the Actions subscription set up page. ### Log Event diff --git a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md index 89e1ff452f..6ff4e43e0e 100644 --- a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md +++ b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md @@ -11,10 +11,10 @@ hidden: true > success "" > **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Google Enhanced Conversions Segment destination. -The Google Enhanced Conversions destination enables you to improve the accuracy of your conversion measurement. You can send first-party customer conversion data from your website, such as email address, to Google Ads. Segment hashes this data sends it in a privacy-safe way. Google matches hashed data with signed-in Google accounts to attribute the conversion to ad events, such as clicks or views. To learn more about Google Enhanced Conversions, see Google's documentation [About enhanced conversions (beta)](https://support.google.com/google-ads/answer/9888656?hl=en-GB){:target="_blank"}. +The Google Enhanced Conversions destination enables you to improve the accuracy of your conversion measurement. You can supplement existing conversion tags by sending first-party customer conversion data from your website, such as email address, to Google Ads. Segment hashes this data and sends it in a privacy-safe way. Google matches hashed data with signed-in Google accounts to attribute the conversion to ad events, such as clicks or views. To learn more about Google Enhanced Conversions, see Google's documentation [About enhanced conversions](https://support.google.com/google-ads/answer/9888656?hl=en-GB){:target="_blank"}. > warning "Before you begin" -> Enable Enhanced Conversions in your Google Ads account. For each Conversion, specify in the settings to that you will use the enhanced conversions API: +> Enable Enhanced Conversions in your Google Ads account. For each Conversion, specify in the settings that you will use the Enhanced Conversions API: > 1. When you log in to Google Ads, make sure you are in [Expert Mode](https://support.google.com/google-ads/answer/9520605?hl=en){:target="_blank"}. > 2. Click **Tools & Settings** in the top bar, and select **Conversions** from the dropdown. Select the **Conversion Action** you want Segment to log to. > 3. Expand the tab for **Enhanced conversions**. Enable **Turn on enhanced conversions**. Under "To start, select how you want to set up enhanced conversions", select **API**. diff --git a/src/connections/destinations/catalog/autopilotapp/index.md b/src/connections/destinations/catalog/autopilotapp/index.md new file mode 100644 index 0000000000..3d0c4d642e --- /dev/null +++ b/src/connections/destinations/catalog/autopilotapp/index.md @@ -0,0 +1,55 @@ +--- +title: AutopilotApp Destination +rewrite: true +beta: true +--- + +[Autopilot](https://autopilotapp.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) helps thousands of organizations around the world automate their communications via email notifications, such as regular email newsletters, abandoned cart emails, as well as SMS messages, and more, to help organizations market and grow their businesses faster. + +Once you connect Segment to AutopilotApp (the Autopilot product), you can leverage Autopilot's powerful [campaign](https://help.autopilotapp.com/user/latest/campaigns/) features on your Segment customer data. + +This destination is maintained by Autopilot. For any issues with the destination, [contact the Autopilot Support team](mailto:help@autopilotapp.com). + + +## Getting Started + +{% include content/connection-modes.md %} + +1. From the Destinations catalog page in the Segment App, click **Add Destination**. +2. Search for "AutopilotApp" in the Destinations Catalog, and select the "AutopilotApp" destination. +3. Click **Configure AutopilotApp** and choose which Source should send data to the "AutopilotApp" destination. +4. If requested, specify the Destination Name for your "AutopilotApp" destination, and click **Save**. +5. Complete [integrating your Autopilot account with Segment](https://help.autopilotapp.com/user/latest/data-sources/configuring-a-new-data-source/3rd-party-integrations/segment.html), which automatically configures your Autopilot API keys within your "AutopilotApp" destination in Segment. + + +## Supported methods + +Autopilot 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 [people](https://help.autopilotapp.com/user/latest/people/) in Autopilot. For example: + +```js +analytics.identify('userId123', { + firstName: 'John', + lastName: 'Doe', + email: 'john.doe@example.com' +}); +``` + +Segment sends Identify calls to Autopilot as an `identify` event. + + +### Track + +Send [Track](/docs/connections/spec/track) calls to create or update [activities](https://help.autopilotapp.com/user/latest/activities/) (including activity attributes) in Autopilot. For example: + +```js +analytics.track('Login Button Clicked', { + action: "login-clicked" +}); +``` + +Segment sends Track calls to Autopilot as a `track` event. \ No newline at end of file diff --git a/src/connections/destinations/catalog/salesforce/index.md b/src/connections/destinations/catalog/salesforce/index.md index 23c7929d74..d6031a9d6f 100644 --- a/src/connections/destinations/catalog/salesforce/index.md +++ b/src/connections/destinations/catalog/salesforce/index.md @@ -179,7 +179,10 @@ To create resources of other types, such as Accounts or custom objects, Segment ### Sandbox Mode -To enable an integration with a Salesforce Sandbox instance, toggle the Sandbox setting to true. +To enable an integration with a Salesforce Sandbox instance: +1. Toggle the Sandbox setting to `true` in the Salesforce Destination settings. +2. Append the sandbox name to the account email, as shown below: + - `name@work.com` -> `name@work.com.sandboxname` where `sandboxname` is the name of your sandbox. ### API Call Limits diff --git a/src/connections/sources/catalog/libraries/mobile/android/troubleshooting.md b/src/connections/sources/catalog/libraries/mobile/android/troubleshooting.md index 0ae606ecb4..b7d4d3b611 100644 --- a/src/connections/sources/catalog/libraries/mobile/android/troubleshooting.md +++ b/src/connections/sources/catalog/libraries/mobile/android/troubleshooting.md @@ -10,7 +10,7 @@ strat: android - The `writekey` might change when you make changes to the source from the Segment web app. - If the `writeKey` you entered is something other than a string or an empty string your app may crash - If the `writeKey` you entered is a valid form but not the correct writeKey for your specific source, you won't see an error response. Segment receives the data, but cannot route it to your source (debugger). -3. [Enable logging](/docs/connections/sources/catalog/libraries/mobile/android/#debugging) to confirm if call is being sent to Segment +3. [Enable logging](/docs/connections/sources/catalog/libraries/mobile/android/#adding-debug-logging) to confirm if call is being sent to Segment ## No events in my destinations @@ -29,7 +29,7 @@ If you still don't see data getting to your destination, continue debugging base Inspect one of your data payloads. If you are using device-mode for a specific destination, the value of that integration should be set to `false` in the `integrations` object. That means that the data is being sent from the device directly to the destination's API endpoints, and not through Segment's servers. This is expected if you chose to use a device-mode destination's SDK with Segment's during installation. -Enable verbose [logging](/docs/connections/sources/catalog/libraries/mobile/android/#debugging) and trigger the call in question. You should see a call to Segment, and one going to the partner SDK. It will show you exactly which partner method was invoked and the arguments it was invoked with! +Enable verbose [logging](/docs/connections/sources/catalog/libraries/mobile/android/#adding-debug-logging) and trigger the call in question. You should see calls to Segment and the partner SDK that show the partner method that was invoked and the arguments with which it was invoked. ## Debugging Cloud-mode Destinations diff --git a/src/connections/sources/catalog/libraries/mobile/swift-ios/index.md b/src/connections/sources/catalog/libraries/mobile/swift-ios/index.md index b0bb8dcb70..6845f11087 100644 --- a/src/connections/sources/catalog/libraries/mobile/swift-ios/index.md +++ b/src/connections/sources/catalog/libraries/mobile/swift-ios/index.md @@ -256,7 +256,7 @@ class SomePlugin: EventPlugin { #### DestinationPlugin The `DestinationPlugin` interface is commonly used for device-mode destinations. This plugin contains an internal timeline that follows the same process as the analytics timeline, enabling you to modify and augment how events reach a particular destination. -For example, if you want to implement a device-mode destination plugin for Amplitude, you can use this: +For example, if you want to implement a device-mode destination plugin for AppsFlyer, you can use this: ```swift internal struct AppsFlyerSettings: Codable { diff --git a/src/connections/sources/catalog/libraries/ott/roku/index.md b/src/connections/sources/catalog/libraries/ott/roku/index.md index 03e59f4016..09d4a80a5a 100644 --- a/src/connections/sources/catalog/libraries/ott/roku/index.md +++ b/src/connections/sources/catalog/libraries/ott/roku/index.md @@ -43,7 +43,7 @@ To instantiate the library, you first need to update the application scene .xml 1. Include SegmentAnalyticsConnector.brs BrightScript file ``` -