From 380866c5e06e77d3cccb05cb73a9db3021e94e88 Mon Sep 17 00:00:00 2001 From: Liz Kane <68755692+lizkane222@users.noreply.github.com> Date: Thu, 31 Aug 2023 17:25:20 -0700 Subject: [PATCH 1/2] Update index.md Customer.io troubleshooting filters --- src/connections/destinations/catalog/customer-io/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/connections/destinations/catalog/customer-io/index.md b/src/connections/destinations/catalog/customer-io/index.md index b982376b38..878f060b05 100644 --- a/src/connections/destinations/catalog/customer-io/index.md +++ b/src/connections/destinations/catalog/customer-io/index.md @@ -269,6 +269,7 @@ Customer.io has limits on the data collected by their API. To ensure your events ### No Events in Customer.io from the Browser Remember that before Segment can send events to Customer.io from client-side JavaScript, the current user must identify with their `userId`. The user's email address is only used to identify them if that is the ID on record for them in Customer.io. +Verify that your Customer.io workspace does not have any filters configured, as these filters could prevent campaigns from being triggered. ### Page events not associated with user Page events will associate to a user if the user has been previously identified in Customer.io. If you identify a user after making Page calls, the previous page events won't associate to the user in Customer.io. From d7aae638ab3c448702f4cce0b4c71b84ccf0e5de Mon Sep 17 00:00:00 2001 From: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Date: Fri, 1 Sep 2023 10:17:55 +0900 Subject: [PATCH 2/2] Update src/connections/destinations/catalog/customer-io/index.md --- src/connections/destinations/catalog/customer-io/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/customer-io/index.md b/src/connections/destinations/catalog/customer-io/index.md index 878f060b05..14c633e350 100644 --- a/src/connections/destinations/catalog/customer-io/index.md +++ b/src/connections/destinations/catalog/customer-io/index.md @@ -269,7 +269,7 @@ Customer.io has limits on the data collected by their API. To ensure your events ### No Events in Customer.io from the Browser Remember that before Segment can send events to Customer.io from client-side JavaScript, the current user must identify with their `userId`. The user's email address is only used to identify them if that is the ID on record for them in Customer.io. -Verify that your Customer.io workspace does not have any filters configured, as these filters could prevent campaigns from being triggered. +Verify that your Customer.io workspace doesn't have any filters configured, as these filters could prevent campaigns from triggering. ### Page events not associated with user Page events will associate to a user if the user has been previously identified in Customer.io. If you identify a user after making Page calls, the previous page events won't associate to the user in Customer.io.