What you'll send to Segment
When you connect Candu to Segment, all Candu events are automatically forwarded. This includes:
Content views: when your content renders on the page, after its segment and display rules pass. This does not check whether the content is visible in the viewport.
Call-to-action clicks: button clicks, card clicks, and link interactions
Checklist interactions: individual item completions and full checklist completions
For a complete list of events and their properties, see Candu's eventing schema documentation.
Important: There is currently no event filtering available for the Segment integration on the Candu side. Once enabled, all Candu events are sent to Segment, and you cannot choose which events to send from Candu.
When is a content view counted?
The content viewed event (candu.sdk.content, sent to integrations as "Candu Content Viewed") fires when the content renders on the page, meaning its component mounts and its styles load. This happens after the content's segment and display rules pass.
The event does not check whether the content is visible in the viewport. Content rendered below the fold or inside a hidden element still counts as a view.
For tours, the event can fire when the tour loads, even if a step's target element is not on the page yet. Step-level views are tracked separately. See Product Tour Analytics.
Filtering options and their limitations
The number of events Candu generates depends on:
How many active content pieces you have published
How many users see and interact with that content
What types of content you're using (tours generate more events than banners)
Segment offers filtering at different stages, depending on your pricing plan:
Schema Controls: allows you to block specific event types before they're ingested by Segment. This would prevent them from counting toward your usage limits.
Destination filters: allows you to control where data goes after Segment has ingested it. These do not reduce your usage costs.
Warehouse Selective Sync: allows you to choose which events, properties, and sources sync to your data warehouse. Like destination filters, this happens after ingestion and doesn't reduce Segment costs.
How to set up the integration
For detailed setup instructions, see Segment's Candu source documentation.
Quick overview:
In your Candu workspace, navigate to Settings > Integrations
Find Segment in the list of available integrations
Toggle on and enter your Segment Write Key
Click Save Changes
Once connected, Candu will automatically begin sending events to Segment. You can then route this data to any analytics tools connected to your Segment workspace.
This guide covers sending data from Candu to Segment. To sync data from Segment to Candu, see Pull user data from Segment.com into Candu (Destination).