diff --git a/src/_data/catalog/beta_sources.yml b/src/_data/catalog/beta_sources.yml new file mode 100644 index 0000000000..3ab4d1785e --- /dev/null +++ b/src/_data/catalog/beta_sources.yml @@ -0,0 +1,24 @@ +# This file is manually generated. +# Add the ids of beta sources to give them a beta flag on the catalog page. +# (/docs/connections/sources/catalog) + +- 8aF29Uq46F +- QhEUZnE5uF +- Zd5BXedXsa +- glwy6LwOVo +- 3x07B5Dn5h +- DY0B0Q2Gce +- n8YgCndi75 +- 9TYqEh3nMe +- xqegKCQA0W +- L9XPA9n2Mc +- kpDbTUR9oD +- wFC7PGNwGR +- vMEJCURfHh +- EjYD7n6dOa +- VETiUX9u66 +- NC2jsEkA8Y +- o9OyD6xsVJ +- ODf0vA6dcH +- YWOGVbyMVz +- CwGEZ7eCcA \ No newline at end of file diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index d8bbcde9dd..27e64d1bdd 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 2023-12-28 +# destination categories last updated 2024-01-02 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 8a3f1d30f6..3e1cd2dc56 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 2023-12-28 +# destination data last updated 2024-01-02 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -52797,6 +52797,7 @@ items: categories: - Heatmaps & Recordings - Analytics + - Performance Monitoring logo: url: https://cdn.filepicker.io/api/file/pwDtlWjnSkGqmplSKEEv mark: @@ -87733,6 +87734,261 @@ items: label: API Key actions: [] presets: [] +- id: 6514281004d549fae3fd086a + display_name: Yahoo Audiences + name: Yahoo Audiences + slug: yahoo-audiences + hidden: false + endpoints: + - US + regions: + - us-west-2 + - eu-west-1 + url: connections/destinations/catalog/yahoo-audiences + previous_names: + - Yahoo Audiences + website: https://www.advertising.yahooinc.com/ + status: PUBLIC_BETA + categories: + - Advertising + logo: + url: https://cdn-devcenter.segment.com/3ff01988-e346-4dc3-a4cf-b031bbe5aea6.png + mark: + url: https://cdn-devcenter.segment.com/f107f33d-8dc6-4880-8bab-10b03997cf97.png + methods: + track: true + identify: true + group: true + alias: true + screen: false + page: true + platforms: + browser: true + mobile: false + server: true + warehouse: false + components: [] + browserUnbundlingSupported: false + browserUnbundlingPublic: false + replay: false + connection_modes: + device: + web: false + mobile: false + server: false + cloud: + web: true + mobile: false + server: true + settings: + - name: customer_desc + type: string + defaultValue: '' + description: Engage space name and description + required: true + label: Customer Description + - name: engage_space_id + type: string + defaultValue: '' + description: Engage Space Id found in Unify > Settings > API Access + required: true + label: Engage Space Id + - name: mdm_id + type: string + defaultValue: '' + description: Yahoo MDM ID provided by Yahoo representative + required: true + label: MDM ID + actions: + - id: cUoo5pvmwBqHsfmBA5eGjR + name: Sync To Yahoo Ads Segment + slug: updateSegment + description: Sync Segment Audience to Yahoo Ads Segment + platform: CLOUD + hidden: false + defaultTrigger: type = "identify" or type = "track" + fields: + - id: fcwi1Zm7Sx9rNEKfi5jHM9 + sortOrder: 0 + fieldKey: segment_audience_id + label: Segment Audience Id + type: STRING + description: >- + Segment Audience Id (aud_...). Maps to "Id" of a Segment node in Yahoo + taxonomy + placeholder: '' + defaultValue: + '@path': $.context.personas.computation_id + required: true + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 9pamTiX3BVxte2gZuTTvBs + sortOrder: 1 + fieldKey: segment_audience_key + label: Segment Audience Key + type: STRING + description: >- + Segment Audience Key. Maps to the "Name" of the Segment node in Yahoo + taxonomy + placeholder: '' + defaultValue: + '@path': $.context.personas.computation_key + required: true + multiple: false + choices: null + dynamic: false + allowNull: false + - id: h419tA6RaDVCh9qb8o3chd + sortOrder: 2 + fieldKey: event_attributes + label: Event traits or properties. Do not modify this setting + type: OBJECT + description: Event traits or properties. Do not modify this setting + placeholder: '' + defaultValue: + '@if': + exists: + '@path': $.properties + then: + '@path': $.properties + else: + '@path': $.traits + required: true + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 5MvAQUp9Nufymb6QdVYtUT + sortOrder: 3 + fieldKey: segment_computation_action + label: Segment Computation Action + type: STRING + description: >- + Segment computation class used to determine if input event is from an + Engage Audience'. Value must be = 'audience'. + placeholder: '' + defaultValue: + '@path': $.context.personas.computation_class + required: true + multiple: false + choices: + - label: audience + value: audience + dynamic: false + allowNull: false + - id: r49EEVEvv7qgyK9uD6QxQx + sortOrder: 4 + fieldKey: phone + label: User Phone + type: STRING + description: Phone number of a user + placeholder: '' + defaultValue: + '@if': + exists: + '@path': $.traits.phone + then: + '@path': $.traits.phone + else: + '@path': $.properties.phone + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: gUCewL7dGh6RMBeLuGhwR6 + sortOrder: 5 + fieldKey: email + label: User Email + type: STRING + description: Email address of a user + placeholder: '' + defaultValue: + '@if': + exists: + '@path': $.traits.email + then: + '@path': $.traits.email + else: + '@path': $.context.traits.email + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: oHfFDfUV16uEKEX7eKicVi + sortOrder: 6 + fieldKey: advertising_id + label: User Mobile Advertising ID + type: STRING + description: User's mobile advertising Id + placeholder: '' + defaultValue: + '@path': $.context.device.advertisingId + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: bgmjvPJFQ3p4p4AUkdmhDG + sortOrder: 7 + fieldKey: device_type + label: User Mobile Device Type + type: STRING + description: User's mobile device type + placeholder: '' + defaultValue: + '@path': $.context.device.type + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: q8QzUyQcwiXirVbmmHNuN9 + sortOrder: 8 + fieldKey: gdpr_flag + label: GDPR Flag + type: BOOLEAN + description: >- + Set to true to indicate that audience data is subject to GDPR + regulations + placeholder: '' + defaultValue: false + required: true + multiple: false + choices: null + dynamic: false + allowNull: false + - id: hy9wWydYAA5FJVWmUe7XgL + sortOrder: 9 + fieldKey: gdpr_euconsent + label: GDPR Consent Attributes + type: STRING + description: >- + Required if GDPR flag is set to "true". Using IAB Purpose bit + descriptions specify the following user consent attributes: "Storage and + Access of Information", "Personalization" + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: m35EEjochsb3me5wxDa4Wo + sortOrder: 10 + fieldKey: enable_batching + label: Enable Batching? + type: BOOLEAN + description: When enabled, Segment will send events in batches. + defaultValue: false + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + presets: [] - id: 54521fdc25e721e32a72ef07 display_name: Yandex Metrica name: Yandex Metrica diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index 2fe73a22ba..8c3e762a15 100644 --- a/src/_data/catalog/destinations_private.yml +++ b/src/_data/catalog/destinations_private.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2023-12-28 +# destination data last updated 2024-01-02 items: - id: 54521fd725e721e32a72eec6 display_name: Intercom diff --git a/src/_data/catalog/regional-supported.yml b/src/_data/catalog/regional-supported.yml index 17c660570f..213237a2ae 100644 --- a/src/_data/catalog/regional-supported.yml +++ b/src/_data/catalog/regional-supported.yml @@ -54,8 +54,10 @@ sources: url: connections/sources/catalog/cloud-apps/amazon-s3 regions: - us + - eu endpoints: - us + - eu - id: TNBRknbbnE display_name: AMP hidden: true diff --git a/src/_data/catalog/slugs.yml b/src/_data/catalog/slugs.yml index dd3c33d186..991eb17ebb 100644 --- a/src/_data/catalog/slugs.yml +++ b/src/_data/catalog/slugs.yml @@ -129,4 +129,8 @@ destinations: override: "actions-iterable" - original: "listrak-actions" override: "actions-listrak" + - original: "logrocket" + override: "actions-logrocket" + - original: "yahoo-audiences" + override: "actions-yahoo-audiences" diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index 9922df3609..e4da6451aa 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 categories last updated 2023-12-28 +# source categories last updated 2024-01-02 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 ab5b3e1629..156c20712e 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 2023-12-28 +# sources last updated 2024-01-02 items: - id: 8HWbgPTt3k display_name: .NET @@ -2009,23 +2009,6 @@ items: categories: - Marketing Automation - Referrals - - id: xeZMgSrtAQ - display_name: White Label Loyalty - isCloudEventSource: true - slug: white-label-loyalty - url: connections/sources/catalog/cloud-apps/white-label-loyalty - hidden: false - regions: - - us - endpoints: - - us - source_type: cloud-app - description: Enterprise loyalty technology platform - logo: - url: >- - https://cdn-devcenter.segment.com/1a2490eb-79fe-419f-800c-6497fe858e8b.svg - categories: - - Analytics - id: 7GmYZcBQyw display_name: WorkRamp isCloudEventSource: true diff --git a/src/_data/catalog/test_sources.yml b/src/_data/catalog/test_sources.yml index 4ecbf9eb6c..2cdf4fcd27 100644 --- a/src/_data/catalog/test_sources.yml +++ b/src/_data/catalog/test_sources.yml @@ -1,3 +1,6 @@ +# This file is manually generated. +# Add the ID for a source here to skip adding it to the sources.yml catalog file. + - kEQE5O66XH - 6mJhCgRpsP - 6qp2MXy9jT diff --git a/src/_data/catalog/warehouse.yml b/src/_data/catalog/warehouse.yml index 68d552b7a3..321b83eed1 100644 --- a/src/_data/catalog/warehouse.yml +++ b/src/_data/catalog/warehouse.yml @@ -8,6 +8,11 @@ items: to yours, where you can then perform custom analysis on them. url: connections/storage/catalog/amazon-s3 status: PUBLIC + endpoints: + - us + regions: + - us + - eu logo: url: 'https://d3hotuclm6if1r.cloudfront.net/logos/amazon-s3-default.svg' mark: @@ -19,6 +24,11 @@ items: 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 + endpoints: + - us + regions: + - us + - eu logo: url: 'https://d3hotuclm6if1r.cloudfront.net/logos/amazon-s3-default.svg' mark: @@ -29,6 +39,11 @@ items: description: '' url: connections/storage/catalog/azuresqldw status: PUBLIC + endpoints: + - us + regions: + - us + - eu logo: url: 'https://cdn.filepicker.io/api/file/VKbuWjNjQPKOnOWijFe4' mark: @@ -41,6 +56,11 @@ items: description: '' url: connections/storage/catalog/bigquery status: PUBLIC + endpoints: + - us + regions: + - us + - eu logo: url: 'https://cdn.filepicker.io/api/file/bDzeRa75SZc6FfgfoUK6' mark: @@ -53,6 +73,11 @@ items: description: '' url: connections/storage/catalog/databricks-delta-lake status: PRIVATE_BETA + endpoints: + - us + regions: + - us + - eu logo: url: 'https://images.ctfassets.net/h6ufgtwb6nv1/4vYEAgYz6nGLC9F64Jxeb6/fcf3ecdae5386f806ae72eb39ce07094/db.svg?w=256&q=75' mark: @@ -65,6 +90,11 @@ items: description: '' url: connections/storage/catalog/google-cloud-storage status: PUBLIC_BETA + endpoints: + - us + regions: + - us + - eu logo: url: 'https://cdn.filepicker.io/api/file/G6kRHZtSoaEslLkENhPC' mark: @@ -77,6 +107,11 @@ items: description: '' url: connections/storage/catalog/db2 status: PUBLIC + endpoints: + - us + regions: + - us + - eu logo: url: 'https://image.ibb.co/i4rS3K/IBM_Db2_logotype_pos_RGB.jpg' mark: @@ -89,6 +124,11 @@ items: description: '' url: connections/storage/catalog/postgres status: PUBLIC + endpoints: + - us + regions: + - us + - eu logo: url: 'https://d3hotuclm6if1r.cloudfront.net/logos/postgres-default.svg' mark: @@ -101,6 +141,11 @@ items: description: '' url: connections/storage/catalog/redshift status: PUBLIC + endpoints: + - us + regions: + - us + - eu logo: url: 'https://d3hotuclm6if1r.cloudfront.net/logos/redshift-default.svg' mark: @@ -113,6 +158,11 @@ items: description: '' url: connections/storage/catalog/data-lakes status: PUBLIC + endpoints: + - us + regions: + - us + - eu logo: url: 'https://cdn.filepicker.io/api/file/YR7dKXAiQWyYvBiVOZNX' mark: @@ -125,6 +175,11 @@ items: description: '' url: connections/storage/catalog/snowflake status: PUBLIC + endpoints: + - us + regions: + - us + - eu logo: url: 'https://cdn.filepicker.io/api/file/JrQWOYvMRRCVvSHp4HL0' mark: diff --git a/src/_data/regional-support.yml b/src/_data/regional-support.yml index f172396012..3de01ebc5b 100644 --- a/src/_data/regional-support.yml +++ b/src/_data/regional-support.yml @@ -56,6 +56,7 @@ sources: - beamer - airship - adwords + - amazon-s3 endpoint: - intercom - amp @@ -91,6 +92,7 @@ sources: - google-ads - facebook-ads - iterable + - amazon-s3 destinations: region: - 2mee diff --git a/src/_includes/content/regional-integrations-table.md b/src/_includes/content/regional-integrations-table.md index 5b7e3bc141..6fec47618f 100644 --- a/src/_includes/content/regional-integrations-table.md +++ b/src/_includes/content/regional-integrations-table.md @@ -1,5 +1,5 @@ {% assign destinations = site.data.catalog.destinations.items %} -{% assign warehouses = site.data.catalog.regional-supported.warehouses %} +{% assign warehouses = site.data.catalog.warehouse.items | where: "status", "PUBLIC" %} @@ -15,7 +15,6 @@ Integration US Workspace EU workspace w/ US Endpoint - EU workspace w/ EU Endpoint @@ -33,9 +32,6 @@ {% if destination.regions contains "eu-west-1" and destination.endpoints contains "US" %}{% else %}{% endif %} - {% if destination.regions contains "eu-west-1" and destination.endpoints contains "EU" %}{% else %}{% endif %} {% endfor %} @@ -51,9 +47,6 @@ {% if warehouse.regions contains "eu" and warehouse.endpoints contains "us" %}{% else %}{% endif %} - {% if warehouse.regions contains "eu" and warehouse.endpoints contains "eu" %}{% else %}{% endif %} {% endfor %} diff --git a/src/_includes/menu/menu-source.html b/src/_includes/menu/menu-source.html index bb402fee7a..c7ddfdcedd 100644 --- a/src/_includes/menu/menu-source.html +++ b/src/_includes/menu/menu-source.html @@ -18,13 +18,14 @@ diff --git a/src/_includes/sidebar/source-menu.html b/src/_includes/sidebar/source-menu.html index 8f004c561e..92fa22386a 100644 --- a/src/_includes/sidebar/source-menu.html +++ b/src/_includes/sidebar/source-menu.html @@ -1,4 +1,4 @@ -{% assign destination_categories = "Website, Mobile, Server, Ott, Cloud apps" | split: ", " %} +{% assign destination_categories = "Website, Mobile, Server, A/B Testing, Advertising, Analytics, Attribution, CRM, Custom, Customer Success, Email Marketing, Enrichment, Feature Flagging, Helpdesk, Learning Management System, Livechat, Marketing Automation, Ott, Payments, Performance Monitoring, Personalization, Raw Data, Referrals, SMS & Push Notifications, Surveys, Virtual Assistant" | split: ", " %}

On this page

diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md index 532dfcc01e..b6bfba567d 100644 --- a/src/connections/destinations/catalog/actions-amplitude/index.md +++ b/src/connections/destinations/catalog/actions-amplitude/index.md @@ -23,7 +23,7 @@ Amplitude (Actions) provides the following benefits over the classic Amplitude d - **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 the destination. - **Support for Amplitude's HTTP API v2**. Amplitude (Actions) is built on the latest version of [Amplitude's HTTP API](https://developers.amplitude.com/docs/http-api-v2){:target="_blank"}. - **Revenue is a top-level property**. Amplitude (Actions) elevates `revenue` to a top-level property in requests sent to Amplitude. This enables inclusion of this data in Amplitude features like customer LTV reports. -- **Session tracking in cloud-mode**. Amplitude (Actions) supports sending session details from cloud-mode sources. +- **Tracking in cloud-mode**. Amplitude (Actions) supports sending details from cloud-mode sources. ## Getting started @@ -56,7 +56,7 @@ The Amplitude (actions) destination does not offer a device-mode connection mode Most previous deployments of the Amplitude Segment destination used the device-mode connection to use the `session_id` tracking feature. The new Actions-framework Amplitude destination, includes session ID tracking by default. When connected to the Analytics.js 2.0 source, Segment automatically loads a plugin on your website for session tracking and enrichment as an alternative to the Amplitude SDK. This means you don't need to bundle any software to run on the user's device, or write any code. It also means that you can use more of the Segment platform features on data going to Amplitude, such as Protocols filtering and transformations, and Profiles Identity Resolution. -Session tracking is available with Segment's new libraries: [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”} or [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}. +Session tracking is available with Segment's new libraries: [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”} or [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}. ### Device ID Mappings @@ -68,7 +68,7 @@ By default, Segment maps the Segment property `context.device.id` to the Amplitu JavaScript sources automatically enable session tracking. -The session ID Segment passes to Amplitude stores locally in a key-value pair. View the value associated with the `analytics_session_id`key to access the session ID. +The session ID Segment passes to Amplitude stores locally in a key-value pair. View the value associated with the `analytics_session_id`key to access the session ID. The session ID is set to timeout every 30 minutes by default. ### Enable Amplitude session tracking for Swift diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-1.png b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-1.png new file mode 100644 index 0000000000..a9f77078c0 Binary files /dev/null and b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-1.png differ diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-2.png b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-2.png new file mode 100644 index 0000000000..bc5a96ac12 Binary files /dev/null and b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-2.png differ diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-3.png b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-3.png new file mode 100644 index 0000000000..7bad4b6e31 Binary files /dev/null and b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-3.png differ diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-4.png b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-4.png new file mode 100644 index 0000000000..a47150bf40 Binary files /dev/null and b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-4.png differ diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-5.png b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-5.png new file mode 100644 index 0000000000..a84425d074 Binary files /dev/null and b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-5.png differ diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-6.png b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-6.png new file mode 100644 index 0000000000..bc7ad77cbe Binary files /dev/null and b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-6.png differ diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-7.png b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-7.png new file mode 100644 index 0000000000..7f328557b0 Binary files /dev/null and b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-7.png differ diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-8.png b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-8.png new file mode 100644 index 0000000000..01f22d25b8 Binary files /dev/null and b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-8.png differ diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-9.png b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-9.png new file mode 100644 index 0000000000..53fae42296 Binary files /dev/null and b/src/connections/destinations/catalog/actions-yahoo-audiences/images/yahoo-9.png differ diff --git a/src/connections/destinations/catalog/actions-yahoo-audiences/index.md b/src/connections/destinations/catalog/actions-yahoo-audiences/index.md new file mode 100644 index 0000000000..ebab386bd9 --- /dev/null +++ b/src/connections/destinations/catalog/actions-yahoo-audiences/index.md @@ -0,0 +1,110 @@ +--- +title: Yahoo Audiences Destination +id: 6514281004d549fae3fd086a +beta: true +--- + +The Yahoo Audiences integration facilitates seamless connectivity between Engage Audiences and Yahoo DSP, offering users the flexibility to configure their data delivery preferences within the Segment platform. + +This integration is designed to accommodate various identifiers, including **email**, **phone**, and **MAIDs** (iOS IDFA, Android Advertising Id). To ensure data security, the integration hashes **email** and **phone** identifiers, while also formatting phone numbers to comply with E.164 requirements. + +Operating on the [Yahoo DataX platform](https://developer.yahooinc.com/datax/guide/){:target="_blank"}, the integration harnesses the power of the [Yahoo Realtime API](https://developer.yahooinc.com/datax/guide/datax-online-spec/user-data-audience-data/){:target="_blank"} for audience synchronization. Users can enjoy the convenience of syncing both realtime and batch audiences, with incremental batches supporting a maximum of 1000 user records. Notably, each synchronized user record can encompass the individual's membership in multiple audiences. + +In addition to these features, the integration provides support for [Trait Activation](/docs/engage/trait-activation/) functionalities, specifically [Trait Enrichment](/docs/engage/trait-activation/trait-enrichment/) and [ID Sync](/docs/engage/trait-activation/id-sync/), enhancing the overall user experience. + + +## Getting started + +To connect your Yahoo Audiences Destination: +1. Create your Engage Audience. +2. Navigate to **Engage** > **Engage Settings** > **Destinations** and click **Add Destination**. +3. Select **Yahoo Audiences**, select your Engage space as the source, and name your destination. +4. Configure global destination settings on the **Settings** tab: + - **Name**: Specify the destination name, for example “Yahoo Audiences Production”. This value will be only available in Segment. + - **MDM ID**: Specify the MDM ID provided by your Yahoo DSP representative. + - **Engage Space ID**: Specify the Engage Space ID. To locate Engage Space ID navigate to **Unify** > **Unify Settings** > **API Access**. This value identifies your customer node in Yahoo Data Taxonomy. Do not provide arbitrary values in this field, or any values other than your Engage Space ID. + - **NOTE:** The destination displays an error if the provided value includes any characters other than [a-zA-Z0-9] and “_” (underscore). This is to prevent passing values not supported by Yahoo. + - **Customer Description**: Provide an optional description for the integration. + - Turn on the **Enable Destination** toggle. + - Click **Save Changes** to save the destination. + - This creates a new customer node in the Yahoo Data Taxonomy. The Customer node ID matches the Engage Space ID provided in the settings. +5. Configure destination Action Mappings. Action Mappings determine the information sent from Engage to Yahoo Audiences destination. Below you will find general information on configuring the mapping, as well as specific configuration for various use-cases. + - On the **Mapping** tab click **Add Mapping** and select **Sync to Yahoo Ads Segment**. + - Within the mapping’s **Select events to map and send** configure whether the mapping should be triggered for all audiences connected to the destination, or for specific audiences only. + - **NOTE:** Action mapping settings apply to all audiences that are processed by the mapping. The mapping can be configured to (1) process all audiences connected to the destination, or (2) only specific audiences. This can be helpful when enabling the GDPR flag only for specific audiences. + - To apply the mapping only to specific audiences, modify the trigger as follows: + ![A screenshot subscription settingsfor specific audience](images/yahoo-1.png) + - To apply the mapping to all audiences, modify the trigger as follows: + ![A screenshot subscription settings for all audiences](images/yahoo-2.png) + - Configure the mapping for **Email**, **Phone**, **Mobile Advertising Id** and **Device Type** fields. You can keep default mapping for these fields, if your data matches default mappings. + - **NOTE:** The destination expects mobile advertising Id to be a combination of 2 fields: advertising Id and device type. If device type field is not available in your data, the destination deduces the platform (iOS /Android) based on advertising Id value formatting. If the value is capitalized - the destination assumes that this is iOS IDFA, otherwise the destination assumes that is Android DSP ID. + - Configure whether **GDPR Flag** should be sent. + - **NOTE:** **GDPR Flag** setting applies to the entire audience. Set this setting to TRUE if the audience is subject to GDPR regulations. If you have set **GDPR Flag** to YES, then populate **GDPR Consent Attributes** setting with the following IAB user consent attributes: “Access of Information” and “Personalization”. See more in [Yahoo DSP API documentation](https://developer.yahooinc.com/datax/guide/gdpr/faq/){:target="_blank"}. If **GDPR Flag** setting is set to YES, and **GDPR Consent Attributes** is not populated, audience sync will fail. + - If you’ve opted to send a **GDPR Flag**, provide **GDPR Consent Attributes**. + - Save the mapping by clicking **Save** button. +6. Connect the Destination to the Audience and configure Audience Sync settings: + - Navigate to **Engage** > **Audiences** > **(your audience)**, click **Add Destination** and select the destination you just created. + - Configure how the audience should be synced. Enable **Send Track** and disable **Send Identify**. + - Select the identifiers to be synced to Yahoo: + - **Default Setup** - sends all email Ids available on a user profile + - **Customized Setup** - configure the identifiers to be sent to Yahoo DSP* + - If you’d like to send iOS IDFA and Android Advertising ID - turn on **Send Mobile IDs** and map MAIDs using **Customized Setup**. + - Do not modify the **Placeholder** setting. + - Click **Save Settings**. + +> info "" +> Yahoo DSP supports the following identifiers: **email**, **phone**, **iOS IDFA**, **Android Advertising Id**. Segment hashes email and phone per Yahoo DSP requirements, so you don’t have to hash email and phone. Segment formats the phone to meet E.164 requirements: removes non-digit characters and adds “+” sign. Your phone trait/identifier must include country code, as Segment does not prepend phone with country code. + +Once the Audience is connected to the Destination, Segment makes a request to Yahoo DSP to create an ‘audience’ (‘segment’) node in Yahoo Data Taxonomy. The node is identified by Audience ID, and named with Audience Key. After Engage has computed the audience, the Destination syncs the audience to Yahoo DSP. + +{% include components/actions-fields.html %} + +## Destination configurations for various use-cases + +### Use-case 1 + +Email, phone, IOS IDFA and Android Advertising ID are available as Engage Identifiers. + +- **Action Mappings**: +Keep default field mappings. +- **Audience Sync settings**: +Select **Customized Setup**, and map available identifiers under the Identifiers section. You can select whether Engage should send First, Last or All Available identifiers. +![A screenshot customized setup configuration](images/yahoo-3.png) + +### Use-case 2 + +Email, phone, IOS IDFA and Android Advertising Id are available as Engage Identifiers and/or Traits. + +- **Action Mappings**: +Modify the mapping to reflect your custom trait names. For example, if you’re planning to send ‘email_addr’ trait as email to Yahoo Audiences, map ‘email_addr’ trait in the **User Email** field. +![A screenshot user email field configuration](images/yahoo-4.png) +- **Audience Sync settings**: +Click **Customized Setup** and select the **Identifiers** and **Traits** that you are planning to send to Yahoo Audiences. For example, if you are planning to send ‘phone’ identifier and ‘email_addr’ trait, map these fields as shown below: +![A screenshot customized setup configuration with traits](images/yahoo-5.png) + +### Use-case 3 +Sending mobile advertising Id custom traits to Yahoo Audiences. + +- **Action Mappings**: +The destination expects 2 fields for mobile advertising Id: advertising Id field (trait) storing the Id value itself, and device type field (trait) storing mobile platform name (‘ios’ or ‘android’). + +If your Engage data includes these 2 fields, you can map them as follows: +![A screenshot mapping settings for 2 fields](images/yahoo-6.png) + +If your data does not include a field with the device type, you can map only the advertising Id trait. The destination detects device type based on the Id value format: Apple IDFA is typically capitalized, and Android advertising Id is typically lowercase. +![A screenshot mapping settings for when device type is not included](images/yahoo-7.png) + +If you have separate traits for iOS IDFA and Android Advertising Id, you can map them using coalesce() function: +![A screenshot mapping settings for iOS IDFA](images/yahoo-8.png) + +- **Audience Sync settings**: +Use Customized Setup to map custom advertising Id and, if available, device type traits: +![A screenshot customized setup configuration for use-case 3](images/yahoo-9.png) + +## FAQs + +### Why am I seeing the difference between audience size in Engage and in Yahoo DSP? +The difference between audience size in Segment and in Yahoo DSP is expected due to ID matching. Yahoo DSP will recognize only users it has matching ID (email / phone / MAID) for. + +### The audience has synced, but I’m seeing 0 population in Yahoo DSP UI. +As soon as user records land in Yahoo DSP, users become targetable in minutes. However, Yahoo DSP reporting is not realtime, and might take 24-48 hrs to catch up. This delay does not affect targeting. Because of that you might see 0 users in the Yahoo DSP audience immediately after the sync. diff --git a/src/connections/destinations/catalog/logrocket/index.md b/src/connections/destinations/catalog/logrocket/index.md deleted file mode 100644 index 1544222446..0000000000 --- a/src/connections/destinations/catalog/logrocket/index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'LogRocket Destination' -hidden: true -id: 635ada35ce269dbe305203ff -published: false -beta: true ---- diff --git a/src/connections/sources/catalog/index.md b/src/connections/sources/catalog/index.md index d950c643a8..48892ee6dd 100644 --- a/src/connections/sources/catalog/index.md +++ b/src/connections/sources/catalog/index.md @@ -20,9 +20,8 @@ Below is a list of the available sources on the Segment platform.
{% assign categories = site.data.catalog.source_categories.items %} - {% assign promoted_categories = "Website, Mobile, Server, Ott" | split: ", " %} - - {% for category in promoted_categories %} + {% assign all_categories = "Website, Mobile, Server, A/B Testing, Advertising, Analytics, Attribution, CRM, Custom, Customer Success, Email Marketing, Enrichment, Feature Flagging, Helpdesk, Learning Management System, Livechat, Marketing Automation, Ott, Payments, Performance Monitoring, Personalization, Raw Data, Referrals, SMS & Push Notifications, Surveys, Virtual Assistant" | split: ", " %} + {% for category in all_categories %}

{{ category }} @@ -43,7 +42,7 @@ Below is a list of the available sources on the Segment platform.

{{ integration.display_name }}
- {% if integration.status == 'PUBLIC_BETA' %} + {% if site.data.catalog.beta_sources contains integration.id %}

Beta

{% endif %}
@@ -52,39 +51,4 @@ Below is a list of the available sources on the Segment platform. {% endfor %} - {% endfor %} - - -
-

- Cloud-apps -

-
- {% assign integrations = site.data.catalog.sources.items %} - {% for integration in integrations %} - {% unless integration.categories contains promoted_categories[0] or integration.categories contains promoted_categories[1] or integration.categories contains promoted_categories[2] or integration.categories contains promoted_categories[3] or integration.hidden == true %} -
- -
-
-
- {% if integration.logos.mark != '' %} - - {% else %} - - {% endif %} -
-
{{ integration.display_name }}
-
- {% if integration.status == 'PUBLIC_BETA' %} -

Beta

- {% endif %} -
- -
- {% endunless %} - {% endfor %} -
-
- - + {% endfor %} \ No newline at end of file diff --git a/src/connections/sources/catalog/libraries/website/javascript/index.md b/src/connections/sources/catalog/libraries/website/javascript/index.md index 1027cca576..ede8715a82 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/index.md +++ b/src/connections/sources/catalog/libraries/website/javascript/index.md @@ -564,6 +564,21 @@ For example: analytics.load('writekey', { highEntropyValuesClientHints: ['architecture', 'bitness', 'model', 'platformVersion', 'uaFullVersion', 'fullVersionList', 'wow64'] }) ``` +#### Disabling +For testing or staging environments, it can be useful to disable your SDK to ensure no events send. + +If `disable: true` is passed, all analytics method calls will be a no-op, and no network calls will be initiated. + +```ts +analytics.load('writekey', { disable: true }) +``` + +For wrapper/plugin authors: if you have a use case where you need special access to the CDN Settings (for example, consent management), you can also pass a function. This API waits for `cdnSettings` to be fetched. Keep in mind that `cdnSettings` is an _unstable_ object. + +```ts +analytics.load('writekey', { disable: (cdnSettings) => true }) +``` + ## Retries When enabled, Analytics.js automatically retries network and server errors. With persistent retries, Analytics.js can: diff --git a/src/connections/sources/index.md b/src/connections/sources/index.md index af87b3caa1..f2b9d16591 100644 --- a/src/connections/sources/index.md +++ b/src/connections/sources/index.md @@ -204,4 +204,4 @@ To create a source: > - Debugger ease of use - mixing libraries/sources on a single API key means you’re heavily reliant on filtering to actually test events > - Flexibility sending data to different projects - if you want to have different warehouse schemas, analytics projects, etc, having multiple sources would create this separation > - More control - as your account grows with the number of destinations you enable, having separate sources allows you to have more control -> - A source type cannot be changed once it is created. You must create a new source if you would like to use a different source type. +> - A source type cannot be changed once it is created. You must create a new source if you would like to use a different source type. \ No newline at end of file diff --git a/src/engage/trait-activation/trait-activation-setup.md b/src/engage/trait-activation/trait-activation-setup.md index 805a5147a5..b055c0857a 100644 --- a/src/engage/trait-activation/trait-activation-setup.md +++ b/src/engage/trait-activation/trait-activation-setup.md @@ -22,6 +22,8 @@ You'll first choose a Destinaton to connect to your Audience and use with Trait |[SendGrid Marketing Campaigns](/docs/connections/destinations/catalog/actions-sendgrid/) | Event | 1. Connect SendGrid Marketing Campaigns to your Segment space.
2. Enter your SendGrid Marketing Campaigns API key into the connection settings. | |[LiveRamp](/docs/connections/destinations/catalog/actions-liveramp-audiences/) | Event | 1. Set up your LiveRamp file drop.
2. Connect LiveRamp Audiences to your Segment space. | |[Iterable (Actions)](/docs/connections/destinations/catalog/actions-iterable/) | Event | 1. Connect Iterable (Actions) to your Segment space.
2. Enter your Iterable (Actions) API key and Data Center Location into the Destination Settings. | +|[Yahoo Audiences (Actions)](/docs/connections/destinations/catalog/actions-yahoo-audiences/) | Event | 1. Connect Yahoo Audiences to your Engage space.
2. Enter your Yahoo MDM ID, Engage Space ID, and provide description (optional). | + ## Resyncs diff --git a/src/guides/regional-segment.md b/src/guides/regional-segment.md index 4c79cab20a..fbfa5649c7 100644 --- a/src/guides/regional-segment.md +++ b/src/guides/regional-segment.md @@ -83,10 +83,13 @@ Use Segment's custom CIDR `3.251.148.96/29` while authorizing Segment to write i ## Destination support and Regional endpoint availability > info "Don't see a regional endpoint for a tool you're using?" -> As more of the partner tools you use (Sources and Destinations) start to support a regional endpoint, Segment will update this list. Your contact for that tool should have a timeline for when they're hoping to support regional data ingestion. You can also visit Segment's [support page](https://segment.com/help/contact/) for any Segment-related questions. +> As more of the partner tools you use (Sources, Destinations, and Warehouses) start to support a regional endpoint, Segment will update this list. Your contact for that tool should have a timeline for when they're hoping to support regional data ingestion. You can also visit Segment's [support page](https://segment.com/help/contact/){:target="_blank"} for any Segment-related questions. The following integrations marked with a ![Supports EU regional endpoints](/docs/images/supported.svg){:class="inline"} (checkmark) support EU Regional endpoints. +> warning "Integrations available in EU workspaces do not guarantee data residency" +> Before you configure an integration, you should check directly with the integration partner to determine if they offer EU endpoints. + {% include content/regional-integrations-table.md %} ## Source Regional support @@ -96,4 +99,4 @@ The following integrations marked with a ![Supports EU regional endpoints](/docs The following Sources marked with a ![Supports EU regional endpoints](/docs/images/supported.svg){:class="inline"} (checkmark) are supported in EU workspaces. -{% include content/regional-sources-table.md %} +{% include content/regional-sources-table.md %} \ No newline at end of file diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index 2cbace1812..3c7eb6861e 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -50,8 +50,8 @@ Segment deletes messages with this `userId` from connected raw data Destinations Segment forwards these deletion requests to a [growing list of supported partners](/docs/privacy/faq/#which-destinations-can-i-send-deletion-requests-to). -Note that Segment has a 30-day SLA for submitted deletion requests. Additionally, Segment's deletion manager can only accommodate 100,000 users within a 30-day period and cannot guarantee a 30-day SLA if there are more than 100,000 deletion requests submitted within those 30 days. [Contact Support](https://segment.com/help/contact/){:target="_blank"} if you need to process more than 100,000 users within a 30 day period. - +Note that Segment has a 30-day SLA for submitted deletion requests. Additionally, Segment's deletion manager can only accommodate 100,000 users within a 30-day period and cannot guarantee a 30-day SLA if there are more than 100,000 deletion requests submitted within those 30 days. You can delete up to 5000 `userId`s per call via Public API. [Contact Support](https://segment.com/help/contact/){:target="_blank"} if you need to process more than 100,000 users within a 30 day period. + **Segment cannot guarantee that data is deleted from your Destinations.** Segment forwards deletion requests to [supported Destinations](/docs/privacy/faq/#which-destinations-can-i-send-deletion-requests-to) (such as Braze, Intercom, and Amplitude) but you should confirm that each partner fulfills the request.