Connect Segment or RudderStack

If your product already sends its events to Segment or RudderStack, you don't need to write the call in Send your first steps. Add a webhook destination that forwards your events to Outcomify, and your funnels fill from the events you already track.

It is still server to server: the events go from Segment's or RudderStack's servers to Outcomify, so there is no script on your pages and no cookie banner.

1. Create a tracking key

1. Open Funnels in the sidebar.
2. In the setup card at the bottom of the page, press Create a tracking key.
3. Copy the key now. It starts with ock_, and it is shown only once.

The key can report funnel steps and nothing else in your workspace. You can revoke it under Evidence → Connect.

2. Add the destination

The setup card's Using Segment or RudderStack? section shows the address to send to:

https://api.outcomify.com/api/funnels/segment

In Segment

1. Open Connections → Destinations and add the Webhooks (Actions) destination to the source that tracks your product.
2. In its Send action, set the URL to the address above and the method to POST.
3. Under Headers, add Authorization with the value Bearer ock_… (your key).
4. Keep the whole event as the body. Batching can be on or off: a single event and a batch of them both work.
5. Turn the destination on.

In RudderStack

1. Add a Webhook destination to your source.
2. Set the URL to the address above and the method to POST.
3. Add the header Authorization with the value Bearer ock_… (your key).

If only Basic authentication is offered

Use the key as the username and leave the password empty. That works the same as the header.

3. Which events are kept

Segment and RudderStack send everything your product tracks, and most of it is not a funnel step. Storing all of it would use up your workspace's 50 step names and its monthly step records on events no funnel reads. So Outcomify keeps an event only when:

• it is a track event: page, screen, identify, group and alias calls are ignored;
• it has a userId: events with only an anonymousId, from people who have not signed up, are ignored;
• its name is a step in one of your funnels, or a step the workspace already reports.

Every other event is answered with a success, so the destination doesn't retry it, and simply not stored. The answer says what happened, which you can see in the destination's delivery log:

{"received": 3, "kept": 1, "recorded": 1, "ignored": 2, "notTracked": ["product_viewed"]}

The time of a step is the event's timestamp (or originalTimestamp). As with the backend call, each person counts once per step, so a repeat or a retry is never counted twice.

How names are matched

Event names become step names like this:

• letters are put in lower case, and accents are dropped;
• spaces, /, ,, + and & become one _;
• anything else that is not a letter, a digit or _ . : - is dropped;
• names longer than 64 characters are cut.

Sent as	Step name
Order Completed	order_completed
Signed Up!	signed_up
created_project	created_project
Köp genomfört	kop_genomfort

4. Build a funnel from what arrives

Names that arrive but are not steps yet are not stored, but they are noted. The setup card lists them under Seen, not tracked yet, for up to 200 names, each for 30 days after it was last sent.

1. Press New funnel at the top right of the Funnels page.
2. Below the steps you already report, the seen names are offered with a dashed outline, with the name as Segment or RudderStack sent it beside them.
3. Pick the steps in order, and save.

From the next time each of those events arrives, it is kept. Earlier events are not: Outcomify never stored them. To fill a new funnel with the past, send the past steps once with the backend call.

When something doesn't arrive

• 401: the key is missing or wrong. Check the Authorization header, including the word Bearer and the space after it.
• 403: the key lacks the funnel scope (create a tracking key from the Funnels page), or tracking is paused for your workspace.
• 429: too many calls at once, or the month's step records are used up. Segment and RudderStack retry on their own.
• Nothing kept: check the notTracked names in the answer. If the step you expect is there, add it to a funnel.