Customer.io web SDK v2
Customer.io has introduced the v2 version of its web device mode in its web SDK. By selecting v2, browser events can now be sent through the Data Pipelines source and in-app messages can be delivered to unidentified visitors. Current destinations will continue to use the v1 version, while new destinations will default to v2. The choice of when to migrate each web device mode connection is up to the user.
The previous integration only included the legacy Journeys snippet, while the newer Data Pipelines JavaScript client requires a Data Pipelines write key and a different event delivery path for anonymous in-app messages. A selector allows users to adopt the Data Pipelines client without altering existing connections. To set up the v2 version, create a Data Pipelines JavaScript source in Customer.io and connect it to the Journeys workspace.
Add the write key and choose v2 in RudderStack. If the Journeys connection is skipped, web events will enter Data Pipelines but not reach Journeys. Keep the Site ID and API key when serving cloud or mobile device mode sources, as their delivery remains unchanged.
Written by urgent.news from Brooks Patterson's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.