Connect RudderStack

Connect your RudderStack workspace as a destination and Tinct will forward the behavioral events it captures on your campaign landing pages (page views and clicks) straight to your RudderStack data plane.

From there you can route them onward to any of your RudderStack destinations (your warehouse, product analytics, CRM, ads platforms, …).

This is a one-way, outbound integration: Tinct → your RudderStack data plane.
Tinct never reads anything back from RudderStack.

1. What you need before you start

To connect RudderStack you need two values from your RudderStack account:

For security, the write key is stored encrypted and never shown in full once saved, only its last few characters are visible so you can recognize which key is configured.

Getting them in RudderStack

1. In RudderStack, go to Connections → Sources and add a source. An HTTP source (or any server-side source such as Java / Event Stream) works well. Tinct delivers events to RudderStack's standard /v1/batch HTTP API.

2. Copy the source's Write Key.

3. Copy your Data Plane URL from your RudderStack workspace (Settings). It must be an HTTPS URL.

4. In RudderStack, attach the destinations you want these events to flow to (warehouse, analytics, etc.).

Note on new keys: RudderStack takes a few moments to propagate a newly created or rotated write key from its control plane to the data plane. If a brand-new key is rejected on the first try, wait a minute and try again.

2. Connect RudderStack in Tinct

Requirements

• The data plane URL must use HTTPS. Plain http:// and non-HTTPS schemes are rejected.

• The URL must point at a publicly reachable host (internal/private addresses are blocked for security).

Steps (Tinct app)

1. Open Settings → Integrations in your Tinct workspace.

2. Choose RudderStack and select Connect.

3. Enter your Write key and Data plane URL.

4. Select Connect.

When you connect, Tinct immediately verifies the credentials by making a test call to your data plane:

• If the write key is wrong, you'll see "RudderStack rejected the write key."

• If the data plane URL is unreachable (typo, wrong region, not HTTPS), you'll see a "Could not reach the RudderStack data plane" error.

• Otherwise the integration is saved and starts forwarding events.

The test call delivers no events to your destinations. It only checks that the write key and URL are valid.

3. What gets sent to RudderStack

Once connected, Tinct forwards two event types as RudderStack track calls. Other internal signals (scroll depth, session heartbeats) are not forwarded.

Event identity

Each event is sent as an anonymous track call. If RudderStack is already running on your site, Tinct's JS SDK reads the RudderStack anonymous id set by your own RudderStack SDK and forwards it on every event (as both anonymousId and the rudderstack_anonymous_id property). This lets you attribute Tinct's page views and clicks to the same visitor RudderStack already tracks, stitching Tinct activity together with the rest of your RudderStack data.

Event properties

All property names are delivered in snake_case. Properties whose value is empty for a given event are omitted.

Common to both events:

Additional properties on Tinct Item Clicked:

Company fields (company_name, company_domain) appear only once Tinct has identified the visitor's company. Anonymous or not-yet-enriched visits send the event without them.

Example payload (as RudderStack receives it)

// "Tinct Item Clicked"
{
  "type": "track",
  "event": "Tinct Item Clicked",
  "anonymousId": "a1b2c3d4-...",
  "timestamp": "2026-06-15T10:32:11Z",
  "properties": {
    "url": "https://go.yourbrand.com/acme-offer",
    "company_name": "Acme Inc.",
    "company_domain": "acme.com",
    "tinct_campaign_id": "8f1c...",
    "tinct_campaign_name": "Q2 ABM — Manufacturing",
    "rudderstack_anonymous_id": "a1b2c3d4-...",
    "element_type": "button",
    "element_value": "Book a demo",
    "href": "https://go.yourbrand.com/demo",
    "cta_event_name": "primary_cta"
  }
}

// "Tinct Page Viewed"
{
  "type": "track",
  "event": "Tinct Page Viewed",
  "anonymousId": "a1b2c3d4-...",
  "timestamp": "2026-06-15T10:32:11Z",
  "properties": {
    "url": "https://go.yourbrand.com/acme-offer",
    "company_name": "Acme Inc.",
    "company_domain": "acme.com",
    "tinct_campaign_id": "8f1c...",
    "tinct_campaign_name": "Q2 ABM — Manufacturing",
    "rudderstack_anonymous_id": "a1b2c3d4-...",
    "href": "https://go.yourbrand.com/demo"
  }
}

4. Delivery behavior

• Events are delivered asynchronously and in batches, expect a short delay (seconds), not instant delivery.

• Delivery is best-effort with automatic retries. If your data plane is temporarily unreachable, Tinct retries a few times before dropping the event; it does not queue indefinitely.

• Forwarding is fire-and-forget: a delivery failure to RudderStack never affects your landing pages or the visitor experience.

5. Managing the integration

Update the data plane URL or rotate the write key

You can edit the integration's configuration at any time from Settings → Integrations → RudderStack.

• To change only the data plane URL, leave the write key field blank — your existing key is kept.

• To rotate the write key, enter the new key (and the data plane URL). Tinct re-validates before saving.

For security, the stored write key is never shown in full, only its last few characters are visible so you can recognize which key is configured.

Disconnect

Select Disconnect on the integration to stop forwarding. No further events are sent after disconnecting.

6. Troubleshooting