Skip to main content

Send from Segment

Prodantix speaks Segment’s HTTP tracking API, so the events you already send through Segment, RudderStack or Jitsu arrive without changing your tracking code. Calls land exactly as the Prodantix SDKs send them: track as the event, page as $pageview, screen as $screen, identify as a person, group as a group and alias as a merged identity.

Through Segment’s Webhooks destination

In Segment, add the Webhooks destination, set its URL to the address below, and add an Authorization header carrying your public project key as a Bearer token.

Bash
URL:           https://eu.api.prodantix.com/segment/v1/webhook
Authorization: Bearer pdx_pub_live_…

From analytics.js

Point analytics.js at Prodantix with its apiHost option and use your public project key as the write key.

TypeScript
import { AnalyticsBrowser } from '@segment/analytics-next';

export const analytics = AnalyticsBrowser.load({
  writeKey: 'pdx_pub_live_…',
  cdnSettings: {
    integrations: {
      'Segment.io': { apiKey: 'pdx_pub_live_…', apiHost: 'eu.api.prodantix.com/segment/v1' },
    },
  },
});

From RudderStack or Jitsu

Both send Segment’s format. Set their destination URL to the address below and the write key to your public project key.

Bash
Endpoint:  https://eu.api.prodantix.com/segment/v1
Write key: pdx_pub_live_…

How calls arrive

The person is the userId, else the anonymousId. Event names are written in Prodantix’s lowercase form, with Segment’s own name kept as $segment_event. A redelivered message lands once, keyed by its messageId. The person’s own address and browser come from context.ip and context.userAgent. Groups take the type segment_group unless their traits name a group_type. Segment’s own limits apply: a call at most 32 KB, a batch at most 500 KB.