Skip to content
Recued
Menu
← Back to recipes

Connect Segment source to tracking plan

by recued-core v1

Approval-gated Segment governance workflow. It reads the target source, tracking plan, existing tracking-plan rules, and currently connected sources, then connects exactly one source to the tracking plan through recued-core.segment.tracking_plan.source.add. It does not edit rules, remove sources, delete tracking plans, mutate source settings, change write keys, or call arbitrary Segment routes.

How it works 9 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (9 steps)
source_id trim
Trim whitespace from setting source id
tracking_plan_id trim
Trim whitespace from setting tracking plan id
pagination default
Apply default
source ?
tracking_plan ?
connected_sources ?
rules ?
connected ?
card to_summary
Format results as a summary card
Settings 5 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

reason setting =
segment setting =
page size setting = 25
source id setting =
tracking plan id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Segment connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.sourcedata.trackingplan

About

Tags

segment segmentsourcetracking-planprotocolsgovernanceapprovalpack:segment

Details

9 steps 5 configurable settings recipe_id: connect-segment-source-tracking-plan