From 0d24c6c499af819ad18a786cbaa47180c3dbdbeb Mon Sep 17 00:00:00 2001 From: Liz Kane <68755692+lizkane222@users.noreply.github.com> Date: Fri, 31 May 2024 16:14:04 -0700 Subject: [PATCH 1/9] Update index.md ID Sync --- .../destinations/catalog/adwords-remarketing-lists/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md index 3c7ab2ca73..ce13f5b0dc 100644 --- a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md +++ b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md @@ -151,6 +151,9 @@ You can set an email on the user profile by including `email` as a trait, as a p If a user has more than one email address or IDFA on their account as `external_ids`, Engage sends the most recent id on the user profile to Adwords for matching. The match rate will be low if Google can't identify users based on the data that you provide. +> info [**ID Sync**]([url](https://segment.com/docs/engage/trait-activation/id-sync/)) +> Now with Segment's ID Sync feature, you can send additional identifiers to actions destinations. Since Google has a requirement on the limit of identifiers that can be sent in each request, the Google Ads Remarketing Lists destination can only be configured to send one additional identifier in its audience's payloads. If the Google Ads Remarketing Lists destination has already been receiving data from an audience, then configuring ID Sync on the destination afterwards will not be applied to the audience users retroactively, and would require a resync in order to add those identifiers to the entire user base. [Contact Segment support](https://segment.com/requests/integrations/) if you would like to request a resync of your audience to its Google Ads Remarketing Lists destination with the newly enabled ID Sync configuration added. + ### Invalid Settings error in Event Delivery Make sure that this destination was created in [Engage](/docs/engage/) as it requires additional event data not available in standard destinations. From c53930ac8438b72d4fdab8d9093afcb38c6cedf1 Mon Sep 17 00:00:00 2001 From: Samantha Crespo <100810716+samkcrespo@users.noreply.github.com> Date: Mon, 22 Jul 2024 16:05:07 -0700 Subject: [PATCH 2/9] Update index.md - user-provided data feature (GA4) --- .../destinations/catalog/actions-google-analytics-4/index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/connections/destinations/catalog/actions-google-analytics-4/index.md b/src/connections/destinations/catalog/actions-google-analytics-4/index.md index 661c681903..def73c8855 100644 --- a/src/connections/destinations/catalog/actions-google-analytics-4/index.md +++ b/src/connections/destinations/catalog/actions-google-analytics-4/index.md @@ -229,5 +229,9 @@ Because [Google's Measurement Protocol API](https://developers.google.com/analyt The Google Analytics 4 Cloud destination does not support Google Optimize. This destination operates in cloud-mode (sending events from Segment servers to Google Analytics using the Measurement Protocol API), which prevents the required [Optimize SDK](https://support.google.com/optimize/answer/11287798?visit_id=637903946258690719-978290187&rd=1){:target="_blank"} snippet from loading on the page. ### Client/server-side event deduplication + Google doesn't offer guidance around how to deduplicate the same event coming in server and client side. As a result, Segment recommends that you not send the same event into Google Analytics 4 from two different locations such that you would expect Google to deduplicate one of the events out of their pipeline. You can [deduplicate user counts](https://support.google.com/analytics/answer/9355949?hl=en){:target="_blank"} using the `User ID` field, but you cannot deduplicate whole events in the Google platform as far as Segment is aware. +### User-provided data collection + +Google has introduced a beta feature for collecting data provided by users, [User-provided data collection](https://support.google.com/analytics/answer/14077171?hl=en&utm_id=ad). It's important to note that this feature is currently not supported by Segment, and, acknowledging this feature policy in your Google Analytics 4 Account has irreversible effects. From 7e8ad7ed5036f95a34af731ae6ba25789c9372dc Mon Sep 17 00:00:00 2001 From: stayseesong Date: Mon, 21 Oct 2024 14:03:00 -0700 Subject: [PATCH 3/9] fixed allowlisting ips --- src/connections/storage/catalog/azuresqldw/index.md | 12 +++++++++--- src/connections/storage/catalog/bigquery/index.md | 8 +++++++- src/connections/storage/catalog/databricks/index.md | 12 +++++++++--- src/connections/storage/catalog/db2/index.md | 7 +++++-- src/connections/storage/catalog/postgres/index.md | 10 ++++++++-- src/connections/storage/catalog/redshift/index.md | 9 ++++++++- src/connections/storage/catalog/snowflake/index.md | 2 -- src/connections/storage/warehouses/faq.md | 9 ++++----- 8 files changed, 50 insertions(+), 19 deletions(-) diff --git a/src/connections/storage/catalog/azuresqldw/index.md b/src/connections/storage/catalog/azuresqldw/index.md index 3872c901ac..1abec59e72 100644 --- a/src/connections/storage/catalog/azuresqldw/index.md +++ b/src/connections/storage/catalog/azuresqldw/index.md @@ -4,14 +4,12 @@ rewrite: true redirect_from: - '/connections/warehouses/catalog/azuresqldw/' --- -{% include content/warehouse-ip.html %} - Azure's [Azure Synapse Analytics](https://azure.microsoft.com/en-us/services/synapse-analytics/){:target="_blank"}, previously known as Azure SQL Data Warehouse, is a limitless analytics service that brings together enterprise data warehousing and Big Data analytics. {% include content/storage-do-include.md %} -## Getting Started +## Getting started Complete the following prerequisites in Microsoft Azure before connecting your Azure Synapse Analytics databases to Segment: @@ -87,6 +85,14 @@ The default [resource allocation class](https://docs.microsoft.com/en-us/azure/s Users with a Business Tier plan can enable Selective Sync for their Azure Synapse Analytics destination. With Selective Sync, you can customize which collections and properties from a source are sent to each warehouse, which leads to faster, more relevant syncs. To learn more about Selective Sync, review the [Warehouse Syncs](/docs/connections/storage/warehouses/warehouse-syncs/#warehouse-selective-sync) documentation. +### Allowlisting IPs + +Segment recommends enabling IP allowlists for added security. All Segment users with workspaces hosted in the US who use allowlists in their warehouses must update those allowlists to include the following ranges: +* `52.25.130.38/32` +* `34.223.203.0/28` + +Users with workspaces in the EU must allowlist `3.251.148.96/29`. + ## Troubleshooting ### Segment is not able to connect to Azure Synapse Analytics diff --git a/src/connections/storage/catalog/bigquery/index.md b/src/connections/storage/catalog/bigquery/index.md index a17a1c1d40..899bb27aef 100644 --- a/src/connections/storage/catalog/bigquery/index.md +++ b/src/connections/storage/catalog/bigquery/index.md @@ -4,7 +4,6 @@ rewrite: true redirect_from: - '/connections/warehouses/catalog/bigquery/' --- -{% include content/warehouse-ip.html %} Segment's [BigQuery](https://cloud.google.com/bigquery/){:target="_blank"} connector makes it easy to load web, mobile, and third-party source data like Salesforce, Zendesk, and @@ -138,6 +137,13 @@ To remove access to the shared Service Account: For more information about managing IAM access, refer to Google's documentation, [Manage access to projects, folders, and organization](https://cloud.google.com/iam/docs/granting-changing-revoking-access){:target="_blank"}. +### Allowlisting IPs + +Segment recommends enabling IP allowlists for added security. All Segment users with workspaces hosted in the US who use allowlists in their warehouses must update those allowlists to include the following ranges: +* `52.25.130.38/32` +* `34.223.203.0/28` + +Users with workspaces in the EU must allowlist `3.251.148.96/29`. ## Best Practices diff --git a/src/connections/storage/catalog/databricks/index.md b/src/connections/storage/catalog/databricks/index.md index 95e845e87e..df3a0c64b4 100644 --- a/src/connections/storage/catalog/databricks/index.md +++ b/src/connections/storage/catalog/databricks/index.md @@ -3,7 +3,6 @@ title: Databricks Destination public: true --- -{% include content/warehouse-ip.html %} With the Databricks Destination, you can ingest event data directly from Segment into your Databricks Lakehouse. @@ -87,7 +86,14 @@ Segment uses the service principal to access your Databricks workspace and assoc 1. Follow the [Databricks guide for adding a service principal to your account](https://docs.databricks.com/en/administration-guide/users-groups/service-principals.html#manage-service-principals-in-your-account){:target="_blank"}. This name can be anything, but Segment recommends something that identifies the purpose (for example, "Segment Storage Destinations"). Note the principal application ID that Databricks generates to use in this step. Segment doesn't require Account admin or Marketplace admin roles. 2. Follow the [Databricks instructions to generate an OAuth secret](https://docs.databricks.com/en/dev-tools/authentication-oauth.html#step-2-create-an-oauth-secret-for-a-service-principal){:target="_blank"}. Note the secret generated by Databricks to use in this step. Once you navigate away from this page, the secret is no longer visible. If you lose or forget the secret, delete the existing secret and create a new one. - Once connected, you'll see a confirmation screen with next steps and more info on using your warehouse. -{% include content/storage-do-include.md %} \ No newline at end of file +{% include content/storage-do-include.md %} + +## Security + +Segment recommends enabling IP allowlists for added security. All Segment users with workspaces hosted in the US who use allowlists in their warehouses must update those allowlists to include the following ranges: +* `52.25.130.38/32` +* `34.223.203.0/28` + +Users with workspaces in the EU must allowlist `3.251.148.96/29`. diff --git a/src/connections/storage/catalog/db2/index.md b/src/connections/storage/catalog/db2/index.md index e22c3a5198..b4486ef7f6 100644 --- a/src/connections/storage/catalog/db2/index.md +++ b/src/connections/storage/catalog/db2/index.md @@ -4,7 +4,6 @@ rewrite: true redirect_from: - '/connections/warehouses/catalog/db2/' --- -{% include content/warehouse-ip.html %} Use [IBM Db2](https://www.ibm.com/analytics/us/en/db2/){:target="_blank"} with Segment to get all of your event and Cloud Source data in a warehouse built by IBM. This @@ -64,7 +63,11 @@ To set up an IBM Db2 destination in the Segment app: ### Allowlisting IPs -If your Db2 Warehouse is in a private network, be sure to [allowlist Segment's IP address](/docs/connections/storage/warehouses/faq/#which-ips-should-i-allowlist) when creating the Db2 user Segment assumes. Otherwise, Segment won't be able to load your data. +Segment recommends enabling IP allowlists for added security. All Segment users with workspaces hosted in the US who use allowlists in their warehouses must update those allowlists to include the following ranges: +* `52.25.130.38/32` +* `34.223.203.0/28` + +Users with workspaces in the EU must allowlist `3.251.148.96/29`. ### Unique User diff --git a/src/connections/storage/catalog/postgres/index.md b/src/connections/storage/catalog/postgres/index.md index d1844ae0d4..a63457d8cf 100644 --- a/src/connections/storage/catalog/postgres/index.md +++ b/src/connections/storage/catalog/postgres/index.md @@ -4,8 +4,6 @@ rewite: true redirect_from: - '/connections/warehouses/catalog/postgres/' --- -{% include content/warehouse-ip.html %} - PostgreSQL, or Postgres, is an object-relational database management system (ORDBMS) with an emphasis on extensibility and standards compliance. As a database server, its primary functions are to store data securely and return that data in response to requests from other software applications. @@ -104,6 +102,14 @@ To make sure your Postgres database is secure: - Create a service user that has `read/write` permissions. - Always require SSL/TLS and make sure your data warehouse can only accept secure connections. Segment only connects to your data warehouse using SSL/TLS. +### Allowlisting IPs + +Segment recommends enabling IP allowlists for added security. All Segment users with workspaces hosted in the US who use allowlists in their warehouses must update those allowlists to include the following ranges: +* `52.25.130.38/32` +* `34.223.203.0/28` + +Users with workspaces in the EU must allowlist `3.251.148.96/29`. + ## Best Practices Once you've got your data in Postgres, you can do even more with it. You might develop an app that performs various functions based on different events being loaded to the database, potentially using [RabbitMQ](https://www.compose.io/articles/going-from-postgresql-rows-to-rabbitmq-messages/){:target="_blank"} as your asynchronous message broker. For example, you might want a banner to appear once your 1000th customer has signed up. The data is at your fingertips; you just need to decide how to use it. diff --git a/src/connections/storage/catalog/redshift/index.md b/src/connections/storage/catalog/redshift/index.md index f0c81b1268..335ed090bc 100644 --- a/src/connections/storage/catalog/redshift/index.md +++ b/src/connections/storage/catalog/redshift/index.md @@ -4,7 +4,6 @@ rewrite: true redirect_from: - '/connections/warehouses/catalog/redshift/' --- -{% include content/warehouse-ip.html %} This guide explains the process to provision a Redshift cluster and allow the Segment warehouse connector to write to it. @@ -75,6 +74,14 @@ VPCs keep servers inaccessible to traffic from the internet. With VPC, you're ab ### SSL/TLS Always require SSL/TLS and make sure your data warehouse accepts only secure connections. Segment only connects to your data warehouse using SSL/TLS. +### Allowlisting IPs + +Segment recommends enabling IP allowlists for added security. All Segment users with workspaces hosted in the US who use allowlists in their warehouses must update those allowlists to include the following ranges: +* `52.25.130.38/32` +* `34.223.203.0/28` + +Users with workspaces in the EU must allowlist `3.251.148.96/29`. + ## Best practices ### Networking diff --git a/src/connections/storage/catalog/snowflake/index.md b/src/connections/storage/catalog/snowflake/index.md index f9b341fcc8..aa76e90e8b 100644 --- a/src/connections/storage/catalog/snowflake/index.md +++ b/src/connections/storage/catalog/snowflake/index.md @@ -5,8 +5,6 @@ redirect_from: - '/connections/warehouses/catalog/snowflake/' --- -{% include content/warehouse-ip.html %} - [Snowflake](https://docs.snowflake.net/manuals/index.html){:target="_blank"} is a data warehouse, built for the cloud, that delivers performance, simplicity, concurrency and affordability. > info "" diff --git a/src/connections/storage/warehouses/faq.md b/src/connections/storage/warehouses/faq.md index e7c7249d60..79861a35f0 100644 --- a/src/connections/storage/warehouses/faq.md +++ b/src/connections/storage/warehouses/faq.md @@ -114,12 +114,11 @@ Segment recommends scripting any sort of additions of data you might have to war ## Which IPs should I allowlist? -{% include content/warehouse-ip.html %} +Segment recommends enabling IP allowlists for added security. All Segment users with workspaces hosted in the US who use allowlists in their warehouses must update those allowlists to include the following ranges: +* `52.25.130.38/32` +* `34.223.203.0/28` -You must allowlist Segment's custom IPs `52.25.130.38/32` and `34.223.203.0/28` while authorizing Segment to write in to your warehouse port. Currently, Redshift and Postgres are the only connectors that require you to configure an IP upon setup. Segment recommends enabling IP allowlists for added security. - - -If you're in the EU region, use CIDR `3.251.148.96/29`. To learn more about EU workspace locations, contact your account manager. +Users with workspaces in the EU must allowlist `3.251.148.96/29`. ## Will Segment sync my historical data? From 6e9bc26f9dc6bc90edc3e4654545799be105d114 Mon Sep 17 00:00:00 2001 From: prigiattiperrut <47340158+prigiattiperrut@users.noreply.github.com> Date: Tue, 29 Oct 2024 13:44:57 +0000 Subject: [PATCH 4/9] Update index.md --- .../catalog/facebook-pixel-server-side/index.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/connections/destinations/catalog/facebook-pixel-server-side/index.md b/src/connections/destinations/catalog/facebook-pixel-server-side/index.md index 38f324d7e6..2d1af9181c 100644 --- a/src/connections/destinations/catalog/facebook-pixel-server-side/index.md +++ b/src/connections/destinations/catalog/facebook-pixel-server-side/index.md @@ -323,3 +323,15 @@ minutes. You can confirm that Facebook received them: > **Note**: It might take a few minutes before events appear in the Events Manager. ![Verify events in the Overview tab of the Events Manager](images/image2.png) + +## Troubleshooting + +### Why am I seeing a "Mismatched IP Address" in Facebook after enabling Facebook Conversions API alongside Facebook Pixel? + +When both Facebook Pixel and Facebook Conversions API are enabled, you may see a "Mismatched IP Address" warning in Facebook reports. This happens because: + +* Facebook Pixel: This collects the user’s IP address directly from the browser, including IPv6 addresses when available, independently of Segment. So, even though Segment’s Analytics.js defaults to collecting only IPv4 addresses, the Facebook Pixel will still automatically collect IPv6 if available, and send it to Facebook. + +* Facebook Conversions API: Events sent to Facebook through the Conversions API may include an IPv4 address collected by Segment Analytics.js, which results in both IPv4 and IPv6 addresses being sent for the same event. + +Since these two addresses don’t match, Facebook flags it as a "Mismatched IP Address." To resolve this, you can manually collect and send the IPv6 address (when available) in the event payload to Segment, and map it to the Facebook Conversions API destination. This ensures consistency between the IP addresses received by Facebook. From 200e8df783c766eeec63dd16c78a921c778b7d29 Mon Sep 17 00:00:00 2001 From: prigiattiperrut <47340158+prigiattiperrut@users.noreply.github.com> Date: Tue, 29 Oct 2024 13:51:17 +0000 Subject: [PATCH 5/9] Update index.md Adding a link from FB official documentation --- .../destinations/catalog/facebook-pixel-server-side/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/facebook-pixel-server-side/index.md b/src/connections/destinations/catalog/facebook-pixel-server-side/index.md index 2d1af9181c..ce4e10645b 100644 --- a/src/connections/destinations/catalog/facebook-pixel-server-side/index.md +++ b/src/connections/destinations/catalog/facebook-pixel-server-side/index.md @@ -330,7 +330,7 @@ minutes. You can confirm that Facebook received them: When both Facebook Pixel and Facebook Conversions API are enabled, you may see a "Mismatched IP Address" warning in Facebook reports. This happens because: -* Facebook Pixel: This collects the user’s IP address directly from the browser, including IPv6 addresses when available, independently of Segment. So, even though Segment’s Analytics.js defaults to collecting only IPv4 addresses, the Facebook Pixel will still automatically collect IPv6 if available, and send it to Facebook. +* Facebook Pixel: This collects the user’s IP address directly from the browser, [including IPv6 addresses when available](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/customer-information-parameters#), independently of Segment. So, even though Segment’s Analytics.js defaults to collecting only IPv4 addresses, the Facebook Pixel will still automatically collect IPv6 if available, and send it to Facebook. * Facebook Conversions API: Events sent to Facebook through the Conversions API may include an IPv4 address collected by Segment Analytics.js, which results in both IPv4 and IPv6 addresses being sent for the same event. From 7529e6224e32710d8b0365c628534118be7e3c69 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Tue, 29 Oct 2024 11:55:26 -0500 Subject: [PATCH 6/9] minor rewording --- .../destinations/catalog/adwords-remarketing-lists/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md index ce13f5b0dc..87467c4695 100644 --- a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md +++ b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md @@ -151,8 +151,8 @@ You can set an email on the user profile by including `email` as a trait, as a p If a user has more than one email address or IDFA on their account as `external_ids`, Engage sends the most recent id on the user profile to Adwords for matching. The match rate will be low if Google can't identify users based on the data that you provide. -> info [**ID Sync**]([url](https://segment.com/docs/engage/trait-activation/id-sync/)) -> Now with Segment's ID Sync feature, you can send additional identifiers to actions destinations. Since Google has a requirement on the limit of identifiers that can be sent in each request, the Google Ads Remarketing Lists destination can only be configured to send one additional identifier in its audience's payloads. If the Google Ads Remarketing Lists destination has already been receiving data from an audience, then configuring ID Sync on the destination afterwards will not be applied to the audience users retroactively, and would require a resync in order to add those identifiers to the entire user base. [Contact Segment support](https://segment.com/requests/integrations/) if you would like to request a resync of your audience to its Google Ads Remarketing Lists destination with the newly enabled ID Sync configuration added. +> info "ID Sync" +> [Segment's ID Sync](/docs/engage/trait-activation/id-sync/), you can send additional identifiers to Actions destinations. However, due to Google’s restrictions on identifier limits per request, the Google Ads Remarketing Lists destination can only include one additional identifier in audience payloads. If the Google Ads Remarketing Lists destination is already receiving data from an audience and you enable ID Sync afterward, the new identifiers won’t be applied retroactively to existing users. To update identifiers for the entire user base, a full resync is required. [Contact Segment support](https://segment.com/requests/integrations/){:target="_blank"} to request a resync with your new ID Sync configuration. ### Invalid Settings error in Event Delivery From 258570e8341ba5b7c308f2f19fa1abab08679d51 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Tue, 29 Oct 2024 12:04:06 -0500 Subject: [PATCH 7/9] rewording and external link --- .../destinations/catalog/actions-google-analytics-4/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-google-analytics-4/index.md b/src/connections/destinations/catalog/actions-google-analytics-4/index.md index def73c8855..7c0b4db364 100644 --- a/src/connections/destinations/catalog/actions-google-analytics-4/index.md +++ b/src/connections/destinations/catalog/actions-google-analytics-4/index.md @@ -234,4 +234,4 @@ Google doesn't offer guidance around how to deduplicate the same event coming in ### User-provided data collection -Google has introduced a beta feature for collecting data provided by users, [User-provided data collection](https://support.google.com/analytics/answer/14077171?hl=en&utm_id=ad). It's important to note that this feature is currently not supported by Segment, and, acknowledging this feature policy in your Google Analytics 4 Account has irreversible effects. +Google offers a beta feature called [User-provided data collection](https://support.google.com/analytics/answer/14077171?hl=en&utm_id=ad){:target="_blank"} that collects data directly from users. Segment doesn't support this feature. Acknowledging the feature policy in your Google Analytics 4 account is permanent, even though you can later disable the data collection itself. From 407a1da3446528d900976b5d60bb311b4ffb44b1 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Tue, 29 Oct 2024 10:13:14 -0700 Subject: [PATCH 8/9] Update src/connections/destinations/catalog/facebook-pixel-server-side/index.md --- .../catalog/facebook-pixel-server-side/index.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/src/connections/destinations/catalog/facebook-pixel-server-side/index.md b/src/connections/destinations/catalog/facebook-pixel-server-side/index.md index ce4e10645b..35ec10ed08 100644 --- a/src/connections/destinations/catalog/facebook-pixel-server-side/index.md +++ b/src/connections/destinations/catalog/facebook-pixel-server-side/index.md @@ -326,12 +326,10 @@ minutes. You can confirm that Facebook received them: ## Troubleshooting -### Why am I seeing a "Mismatched IP Address" in Facebook after enabling Facebook Conversions API alongside Facebook Pixel? +### Why do I see a "Mismatched IP Address" warning in Facebook after enabling the Facebook Conversions API alongside Facebook Pixel? -When both Facebook Pixel and Facebook Conversions API are enabled, you may see a "Mismatched IP Address" warning in Facebook reports. This happens because: - -* Facebook Pixel: This collects the user’s IP address directly from the browser, [including IPv6 addresses when available](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/customer-information-parameters#), independently of Segment. So, even though Segment’s Analytics.js defaults to collecting only IPv4 addresses, the Facebook Pixel will still automatically collect IPv6 if available, and send it to Facebook. - -* Facebook Conversions API: Events sent to Facebook through the Conversions API may include an IPv4 address collected by Segment Analytics.js, which results in both IPv4 and IPv6 addresses being sent for the same event. +When you enable both Facebook Pixel and the Facebook Conversions API, you may see a "Mismatched IP Address" warning in Facebook reports. This happens because: +* Facebook Pixel collects the user’s IP address directly from the browser, [including IPv6 addresses when available](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/customer-information-parameters#){:target="_blank"}, independently of Segment. Even though Segment’s Analytics.js defaults to collecting only IPv4 addresses, Facebook Pixel automatically collects IPv6 if available, and sends it to Facebook. +* Events sent to Facebook through the Conversions API may include an IPv4 address collected by Segment Analytics.js, which results in both IPv4 and IPv6 addresses being sent for the same event. Since these two addresses don’t match, Facebook flags it as a "Mismatched IP Address." To resolve this, you can manually collect and send the IPv6 address (when available) in the event payload to Segment, and map it to the Facebook Conversions API destination. This ensures consistency between the IP addresses received by Facebook. From 37d2f63042a4c13aa34fd8ac189950688d95ef2d Mon Sep 17 00:00:00 2001 From: stayseesong Date: Tue, 29 Oct 2024 10:23:38 -0700 Subject: [PATCH 9/9] make catalog --- src/_data/catalog/destination_categories.yml | 2 +- src/_data/catalog/destinations.yml | 441 +++++++++++++++---- src/_data/catalog/destinations_private.yml | 2 +- src/_data/catalog/source_categories.yml | 2 +- src/_data/catalog/sources.yml | 2 +- 5 files changed, 361 insertions(+), 88 deletions(-) diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index ef1c8c6161..d4f365dbd1 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 2024-10-24 +# destination categories last updated 2024-10-29 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 15cde0a6c9..8bfaa0cb43 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 2024-10-24 +# destination data last updated 2024-10-29 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -80555,7 +80555,7 @@ items: hidden: false defaultTrigger: event = "Audience Exited" fields: - - id: 75x66yG81uLaYxiPtTV7qG + - id: 7nm8V3yYHhVPNDPC8UzN3Z sortOrder: 1 fieldKey: lookup_field label: Lookup Field @@ -80590,7 +80590,7 @@ items: value: sfdcOpptyId dynamic: false allowNull: false - - id: vt3u2J8A2EdDqpuXta4bQH + - id: 5kLrgBKkAjBy7XHkQXHHc6 sortOrder: 2 fieldKey: field_value label: Field Value @@ -80610,7 +80610,23 @@ items: choices: null dynamic: false allowNull: false - - id: dvBeP8WZtYJrKRdRNnZxPV + - id: knZwfEixC2V1Wxir9PM1bm + sortOrder: 4 + fieldKey: batch_size + label: Batch Size + type: NUMBER + description: >- + Maximum number of events to include in each batch. Actual batch sizes + may be lower. + placeholder: '' + defaultValue: 300 + required: true + multiple: false + choices: null + dynamic: false + allowNull: false + hidden: false + - id: drScuVuQVfjiSdA3gPF5vr sortOrder: 5 fieldKey: event_name label: Event Name @@ -80632,7 +80648,7 @@ items: hidden: false defaultTrigger: event = "Audience Entered" fields: - - id: 7h7i6r8CpTRHtoAS7F28B1 + - id: 6Lvo2Sjc35CZpmwUSHMyP sortOrder: 1 fieldKey: lookup_field label: Lookup Field @@ -80667,7 +80683,7 @@ items: value: sfdcOpptyId dynamic: false allowNull: false - - id: 4rt2BXxjpJbdDuQJdQUY9u + - id: quWxW7f7gpmmNVUCj1dsgZ sortOrder: 2 fieldKey: data label: Lead Info Fields @@ -80692,7 +80708,23 @@ items: choices: null dynamic: false allowNull: false - - id: agnnPPYiG8WhHhirQqohsD + - id: 3rUzAJBDujmKiH8bpqhcAL + sortOrder: 4 + fieldKey: batch_size + label: Batch Size + type: NUMBER + description: >- + Maximum number of events to include in each batch. Actual batch sizes + may be lower. + placeholder: '' + defaultValue: 300000 + required: true + multiple: false + choices: null + dynamic: false + allowNull: false + hidden: false + - id: spqFVkTYtjJn7Hpsv8rQ56 sortOrder: 5 fieldKey: event_name label: Event Name @@ -80706,7 +80738,7 @@ items: choices: null dynamic: false allowNull: false - - id: i4D4j8GMWQFHAFohgKZr6W + - id: 6JD7uPfCeHZmyQw2ggefJg sortOrder: 6 fieldKey: list_id label: Existing List ID @@ -80720,7 +80752,7 @@ items: choices: null dynamic: false allowNull: false - - id: 3dtF7aUvExMgjxM55YoukP + - id: 57pxKnw8Wvp6JKLG1vTnFD sortOrder: 7 fieldKey: list_name label: List Name @@ -80732,7 +80764,7 @@ items: choices: null dynamic: false allowNull: false - - id: tq1z2vnLt3dEmu7DXzG6bg + - id: 4mfrp14uPr5npZ89R6xXDN sortOrder: 8 fieldKey: retlOnMappingSave label: Connect to a static list in Marketo @@ -92787,7 +92819,7 @@ items: hidden: false defaultTrigger: type = "page" fields: - - id: pHvTXyLTgyASc6X5uqWcgv + - id: cYZYdxvQzBev6fZR5xdzwf sortOrder: 0 fieldKey: anonymousId label: Anonymous ID @@ -92802,7 +92834,7 @@ items: dynamic: false allowNull: true hidden: false - - id: FZVumySzDhkePXoUZhahx + - id: hsGJRRqsjoFqZKZ82zpxZB sortOrder: 1 fieldKey: timestamp label: Timestamp @@ -92817,7 +92849,7 @@ items: dynamic: false allowNull: false hidden: false - - id: d5JQVdD8RYd3KMXPnWaN4w + - id: v1VGGytx1NYqUgYHDSn5MT sortOrder: 2 fieldKey: referrer label: Page Referrer @@ -92838,7 +92870,7 @@ items: dynamic: false allowNull: true hidden: false - - id: nXE7WKs55KxBJAALSFJre8 + - id: dnSccvhcXFtXq7FYb6ap9v sortOrder: 3 fieldKey: url label: Page URL @@ -92859,7 +92891,7 @@ items: dynamic: false allowNull: true hidden: false - - id: cSvU5YXuWH3qiTrsUSbkn6 + - id: 6oR6Ba2jbPHFvpK3QRXbrG sortOrder: 4 fieldKey: ip label: User IP address @@ -92874,7 +92906,7 @@ items: dynamic: false allowNull: false hidden: false - - id: qMk6F1Vpq6wBcURZbwr3oh + - id: sN55PJZPUndAZcHmGz7nMr sortOrder: 5 fieldKey: library label: Segment Library @@ -92889,7 +92921,7 @@ items: dynamic: false allowNull: false hidden: false - - id: oCUXryqFkU1KBBYxJrvcbP + - id: iMhGsP389b4qc7JsMJ8Zt1 sortOrder: 6 fieldKey: userAgent label: User Agent @@ -92912,7 +92944,7 @@ items: hidden: false defaultTrigger: type = "track" fields: - - id: g8q44Qo39z3EZmKbZEebqk + - id: c5Cyryb66879sYfKuvi379 sortOrder: 0 fieldKey: anonymousId label: Anonymous ID @@ -92927,7 +92959,7 @@ items: dynamic: false allowNull: true hidden: false - - id: hEfmKxURw1pmPK9FbjqYVo + - id: f9Bz4NCkmubwGLLcP1yWYs sortOrder: 1 fieldKey: timestamp label: Timestamp @@ -92942,7 +92974,7 @@ items: dynamic: false allowNull: false hidden: false - - id: tBVgnUMJPPXRxftER9bb8C + - id: 92McJykQw7qH8Xi5gjTGuA sortOrder: 2 fieldKey: referrer label: Page Referrer @@ -92963,7 +92995,7 @@ items: dynamic: false allowNull: true hidden: false - - id: aW8DZA3wtcV1cF1BNpYeJr + - id: 31apiakvDM1jTp7dKFVBzs sortOrder: 3 fieldKey: url label: Page URL @@ -92984,7 +93016,7 @@ items: dynamic: false allowNull: true hidden: false - - id: qyms9647TSz6nDiscs4pNp + - id: 7ExWVm19PLZVYzfbXMFaUC sortOrder: 4 fieldKey: ip label: User IP address @@ -92999,7 +93031,7 @@ items: dynamic: false allowNull: false hidden: false - - id: t3aDAvPAxnmjLafXrq84uW + - id: npX2zKEB16yMmz7VYeaGhn sortOrder: 5 fieldKey: library label: Segment Library @@ -93014,7 +93046,7 @@ items: dynamic: false allowNull: false hidden: false - - id: ckRv1mQxUR2MrFgcMohat5 + - id: iGvB5w2qXuASKesXnRrQTy sortOrder: 6 fieldKey: userAgent label: User Agent @@ -93029,7 +93061,7 @@ items: dynamic: false allowNull: false hidden: false - - id: oFqipsX6gK9ZUTC4pBCCMr + - id: bQSecVUCXwSGEszBLvYeXX sortOrder: 7 fieldKey: email label: Email address @@ -93050,7 +93082,7 @@ items: dynamic: false allowNull: true hidden: false - - id: 3bZZVHnB5k6RWFDX6XWHsm + - id: 56kZ2bxgbeXT5JRHTefFfD sortOrder: 8 fieldKey: properties label: Event properties @@ -93078,7 +93110,7 @@ items: dynamic: false allowNull: false hidden: false - - id: edjPFAtJDdsE8YAre62pn7 + - id: tSQ1Q4pFQpoKoWy8YGbe2u sortOrder: 9 fieldKey: podscribeEvent label: Podscribe event type @@ -93095,7 +93127,7 @@ items: hidden: false presets: - actionId: wXFTRjNRXRVqqSPeFL66YJ - name: Signed Up Calls + name: Order Completed Calls fields: anonymousId: '@path': $.anonymousId @@ -93146,10 +93178,10 @@ items: '@path': $.properties.is_new_customer is_subscription: '@path': $.properties.is_subscription - podscribeEvent: signup - trigger: type = "track" and event = "Signed Up" - - actionId: otTeGZNHmduwXWxaTMe4ux - name: Page Calls + podscribeEvent: purchase + trigger: type = "track" and event = "Order Completed" + - actionId: wXFTRjNRXRVqqSPeFL66YJ + name: Signed Up Calls fields: anonymousId: '@path': $.anonymousId @@ -93177,9 +93209,33 @@ items: '@path': $.context.library userAgent: '@path': $.context.userAgent - trigger: type = "page" - - actionId: wXFTRjNRXRVqqSPeFL66YJ - name: Order Completed Calls + email: + '@if': + exists: + '@path': $.context.traits.email + then: + '@path': $.context.traits.email + else: + '@path': $.properties.email + properties: + total: + '@path': $.properties.total + order_id: + '@path': $.properties.order_id + currency: + '@path': $.properties.currency + coupon: + '@path': $.properties.coupon + num_items_purchased: + '@path': $.properties.num_items_purchased + is_new_customer: + '@path': $.properties.is_new_customer + is_subscription: + '@path': $.properties.is_subscription + podscribeEvent: signup + trigger: type = "track" and event = "Signed Up" + - actionId: otTeGZNHmduwXWxaTMe4ux + name: Page Calls fields: anonymousId: '@path': $.anonymousId @@ -93207,31 +93263,7 @@ items: '@path': $.context.library userAgent: '@path': $.context.userAgent - email: - '@if': - exists: - '@path': $.context.traits.email - then: - '@path': $.context.traits.email - else: - '@path': $.properties.email - properties: - total: - '@path': $.properties.total - order_id: - '@path': $.properties.order_id - currency: - '@path': $.properties.currency - coupon: - '@path': $.properties.coupon - num_items_purchased: - '@path': $.properties.num_items_purchased - is_new_customer: - '@path': $.properties.is_new_customer - is_subscription: - '@path': $.properties.is_subscription - podscribeEvent: purchase - trigger: type = "track" and event = "Order Completed" + trigger: type = "page" partnerOwned: true - id: 5d25eddde3ff660001b3adda display_name: Podsights @@ -93364,14 +93396,12 @@ items: website: https://posthog.com status: PUBLIC categories: - - A/B Testing - Analytics - - Heatmaps & Recordings - - Raw Data + - A/B Testing logo: - url: https://cdn-devcenter.segment.com/5d042cef-4694-4866-98c6-a922cfa1f715.svg + url: https://cdn-devcenter.segment.com/45976284-89f2-4a4a-9930-0cb4966d3c1a.svg mark: - url: https://cdn-devcenter.segment.com/d7a2a57f-4ae9-4018-a560-a0ce3a4dfc2e.svg + url: https://cdn-devcenter.segment.com/2b447431-1237-4ea1-85a9-726382ea4f66.svg methods: track: true identify: true @@ -106073,7 +106103,7 @@ items: hidden: false defaultTrigger: null fields: - - id: hqGau9H2YPp9vvFqQ7HCpD + - id: mf4v2hHVu18RCa47a8vzeB sortOrder: 0 fieldKey: enable_batching label: Batch Data to SendGrid Contacts PUT API @@ -106090,7 +106120,7 @@ items: dynamic: false allowNull: false hidden: false - - id: mksF7PZS3ehWcHUxpmFkrn + - id: jrLmfx9wm8c8mFpzApTur2 sortOrder: 1 fieldKey: first_name label: First Name @@ -106111,7 +106141,7 @@ items: dynamic: false allowNull: true hidden: false - - id: wB5pKNPMMuU9AVUHBvZsAo + - id: kgfHpkxzfPYY1ZRnaMyrVS sortOrder: 2 fieldKey: last_name label: Last Name @@ -106132,7 +106162,7 @@ items: dynamic: false allowNull: true hidden: false - - id: b7KfmtKozzd5GeBwr1sBwW + - id: qhqK55BgTQKZCqF37Ai87T sortOrder: 3 fieldKey: country label: Country @@ -106153,7 +106183,7 @@ items: dynamic: false allowNull: true hidden: false - - id: vPBFLYEDxf8bQVPiPqpwUY + - id: 7AYUyjGSJsor9oZB8gRTMU sortOrder: 4 fieldKey: postal_code label: Postal Code @@ -106174,7 +106204,7 @@ items: dynamic: false allowNull: true hidden: false - - id: fimhFZbSERbbNVPKbTb19e + - id: uVPiNMfXy5RYfacvhYjLUS sortOrder: 5 fieldKey: city label: City @@ -106195,7 +106225,7 @@ items: dynamic: false allowNull: true hidden: false - - id: oxBceQLdUu1ntMFuMskmKv + - id: qB5uFVAxtUXfKCub8KHjfQ sortOrder: 6 fieldKey: state label: State @@ -106216,7 +106246,7 @@ items: dynamic: false allowNull: true hidden: false - - id: 3Vhj8ZUHNV1GEfmQ4CtQNm + - id: soXcNfsq5fifUDuH1f323a sortOrder: 7 fieldKey: address_line_1 label: Address Line 1 @@ -106237,7 +106267,7 @@ items: dynamic: false allowNull: true hidden: false - - id: qRvWqLW4gH4ouBwYze3uvj + - id: 7cR7DJmmc14JitjCsfZDJ7 sortOrder: 8 fieldKey: address_line_2 label: Address Line 2 @@ -106258,7 +106288,7 @@ items: dynamic: false allowNull: true hidden: false - - id: jJrGRkhMxDx2s6NCdivPkq + - id: x7QfiK4HzV6Q8QCU82yjRB sortOrder: 9 fieldKey: phone_number label: Phone Number @@ -106281,7 +106311,7 @@ items: dynamic: false allowNull: true hidden: false - - id: muiSspbJscq3cbLxYH39FM + - id: a3REojCvEgsfjj7ppoDNxJ sortOrder: 10 fieldKey: whatsapp label: WhatsApp @@ -106302,7 +106332,7 @@ items: dynamic: false allowNull: true hidden: false - - id: hnHsEHjP5mSLP16hH34idJ + - id: n1RZxTuwRhDZzMsyWY1KWp sortOrder: 11 fieldKey: line label: Line @@ -106323,7 +106353,7 @@ items: dynamic: false allowNull: true hidden: false - - id: o7drFcH2kczfuEXCgPBFjC + - id: 4fiSwXGerXCahHn4wvCUPE sortOrder: 12 fieldKey: facebook label: Facebook @@ -106344,7 +106374,7 @@ items: dynamic: false allowNull: true hidden: false - - id: cCuxDshNhy4qQiavLpccr2 + - id: 9XyQoDrxmPPsrSQr56rJfM sortOrder: 13 fieldKey: unique_name label: Unique Name @@ -106365,7 +106395,7 @@ items: dynamic: false allowNull: true hidden: false - - id: 6QtJ8QsE8WDMkKtfgLraWQ + - id: gdxRRkenQnoCEPjkHstvDd sortOrder: 14 fieldKey: primary_email label: Email Address @@ -106386,7 +106416,7 @@ items: dynamic: false allowNull: true hidden: false - - id: xwDC9kamULiZ4RQ9BnHDDS + - id: pcpCbXskHEa9s5BN7Uexd sortOrder: 15 fieldKey: phone_number_id label: Phone Number ID @@ -106408,7 +106438,7 @@ items: choices: null dynamic: false allowNull: true - - id: vEV3Vk7kyeSE9KnUeE7hyw + - id: rhUfmcko47PSt1LPiH4Nuy sortOrder: 16 fieldKey: external_id label: External ID @@ -106428,7 +106458,7 @@ items: choices: null dynamic: false allowNull: true - - id: 5eKW34E8tqWpmsry1Ywoga + - id: 9JaivALq3VR1wCkDqwBq1p sortOrder: 17 fieldKey: anonymous_id label: 'Anonymous ID ' @@ -106442,7 +106472,7 @@ items: choices: null dynamic: false allowNull: true - - id: gi69M2JPB7n3bMa5rYaxfj + - id: 31h9b6JAhbQXaAqznPjDDe sortOrder: 18 fieldKey: customFields label: Other Fields @@ -106464,6 +106494,249 @@ items: dynamic: false allowNull: false hidden: false + - id: 2NyqxNN5TGJa1CP5xEYeLu + name: Send email with Dynamic Template + slug: sendEmail + description: Send email to recipient(s) using a Dynamic Template in Sendgrid + platform: CLOUD + hidden: false + defaultTrigger: null + fields: + - id: 3s9SRyfagPXuGCKiVCjnWw + sortOrder: 0 + fieldKey: domain + label: Validated Domain + type: STRING + description: >- + The domain to use for the email. This field is optional but recommended. + If you do not provide a domain, Sendgrid will attempt to send the email + based on the from address, and may fail if the domain in the from + address is not validated. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: true + allowNull: false + - id: wpNHFDg4tetZAF3oZKMqTk + sortOrder: 1 + fieldKey: from + label: From + type: OBJECT + description: From details. + placeholder: '' + required: true + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 9mz6H6CVoCb7yLMT3DNuuN + sortOrder: 2 + fieldKey: to + label: To + type: OBJECT + description: Recipient details. + placeholder: '' + required: true + multiple: true + choices: null + dynamic: false + allowNull: false + - id: tBber9AUJnBh6XgTxuQ2yG + sortOrder: 3 + fieldKey: cc + label: CC + type: OBJECT + description: CC recipient details + placeholder: '' + required: false + multiple: true + choices: null + dynamic: false + allowNull: false + - id: 8MdoSqdomnzcFywSurFLvo + sortOrder: 4 + fieldKey: bcc + label: BCC + type: OBJECT + description: BCC recipient details + placeholder: '' + required: false + multiple: true + choices: null + dynamic: false + allowNull: false + - id: op5Rvfshi24vvLwETYahbD + sortOrder: 5 + fieldKey: headers + label: Headers + type: OBJECT + description: Headers for the email. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: sTF8sR1wjU7qgkB7fceLrd + sortOrder: 6 + fieldKey: dynamic_template_data + label: Dynamic Template Data + type: OBJECT + description: >- + A collection of property names that will be substituted by their + corresponding property values in the subject, reply-to and content + portions of a SendGrid Dynamic Template. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 9ETWW46krQya8g5Smo4qvo + sortOrder: 7 + fieldKey: template_id + label: Template ID + type: STRING + description: >- + The template ID to use for the email. This must be for a Dynamic + Template and should start with a 'd-' + placeholder: '' + required: true + multiple: false + choices: null + dynamic: true + allowNull: false + - id: fwtebxozXYefHn4PJaV67u + sortOrder: 8 + fieldKey: custom_args + label: Custom Args + type: OBJECT + description: Custom arguments for the email. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: gAcFJ1bFRyotfK7ZiGx8EL + sortOrder: 9 + fieldKey: send_at + label: Send At + type: STRING + description: >- + The time to send the email. ISO 8601 format. E.g. 2024-09-23T12:00:00Z. + A send cannot be scheduled more than 72 hours in advance. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 63ysxWR2FN145SfwwBbGUz + sortOrder: 10 + fieldKey: reply_to + label: Reply To + type: OBJECT + description: Reply to details. + placeholder: '' + defaultValue: + reply_to_equals_from: true + required: true + multiple: false + choices: null + dynamic: false + allowNull: false + - id: tU5WRtT9V7psokYtefXo9p + sortOrder: 11 + fieldKey: subscription_tracking + label: Subscription Tracking + type: OBJECT + description: >- + Allows you to insert a subscription management link at the bottom of the + text and HTML bodies of your email. + placeholder: '' + defaultValue: + enable: false + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 9K2fF49icYNQACryurdDYg + sortOrder: 12 + fieldKey: categories + label: Categories + type: STRING + description: Categories for the email. + placeholder: '' + required: false + multiple: true + choices: null + dynamic: false + allowNull: false + - id: jTcHahvaJoctNj2wb5NSEM + sortOrder: 13 + fieldKey: google_analytics + label: Google Analytics + type: OBJECT + description: Allows you to enable tracking provided by Google Analytics. + placeholder: '' + defaultValue: + enable: true + utm_source: + '@path': $.context.campaign.source + utm_medium: + '@path': $.context.campaign.medium + utm_term: + '@path': $.context.campaign.term + utm_content: + '@path': $.context.campaign.content + utm_campaign: + '@path': $.context.campaign.name + required: false + multiple: false + choices: null + dynamic: false + allowNull: false + - id: 5txhHeEX3A34EJ5vgL16Yt + sortOrder: 14 + fieldKey: ip_pool_name + label: IP Pool + type: STRING + description: Send email with an ip pool. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: true + allowNull: false + - id: 4Wg3giJULyshexbmhw7UQj + sortOrder: 15 + fieldKey: group_id + label: Group ID + type: STRING + description: Specify a Group ID + placeholder: '' + required: false + multiple: false + choices: null + dynamic: true + allowNull: false + - id: rLfteC3hko15cQqio6YbDA + sortOrder: 16 + fieldKey: sandbox_mode + label: Sandbox Mode + type: BOOLEAN + description: >- + Sandbox Mode allows you to send a test email to ensure that your request + body is valid and formatted correctly. + placeholder: '' + required: false + multiple: false + choices: null + dynamic: false + allowNull: false presets: [] partnerOwned: true - id: 54521fda25e721e32a72eef0 diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index 96ad57236c..9b3c3fcf77 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 2024-10-24 +# destination data last updated 2024-10-29 items: - id: 54521fd925e721e32a72eee1 display_name: Pardot diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index cca80b2be4..afd777398f 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 2024-10-24 +# source categories last updated 2024-10-29 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 fb807e6aa6..3c05cfeba2 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 2024-10-24 +# sources last updated 2024-10-29 items: - id: 8HWbgPTt3k display_name: .NET