Skip to content

Commit d7aae63

Browse files
authored
Update src/connections/destinations/catalog/customer-io/index.md
1 parent 380866c commit d7aae63

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/customer-io

1 file changed

+1
-1
lines changed

src/connections/destinations/catalog/customer-io/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -269,7 +269,7 @@ Customer.io has limits on the data collected by their API. To ensure your events
269269

270270
### No Events in Customer.io from the Browser
271271
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.
272-
Verify that your Customer.io workspace does not have any filters configured, as these filters could prevent campaigns from being triggered.
272+
Verify that your Customer.io workspace doesn't have any filters configured, as these filters could prevent campaigns from triggering.
273273

274274
### Page events not associated with user
275275
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.

0 commit comments

Comments
 (0)