CDPGuidesSupport

AWS Kinesis

Stream your Ours Privacy event data to an Amazon Kinesis data stream in real time for high-throughput, low-latency event processing.

Use this page to connect Ours Privacy to Amazon Kinesis. Each event is written to your Kinesis data stream as it happens, so you can process high-volume event streams with your own consumers.


Before you start

  • A Kinesis data stream, with its name and region.
  • Permission to create an IAM role in the AWS account that owns the stream.

Ours Privacy writes to your stream through an IAM role in your AWS account.

Setup

  1. Open the Destinations page and add an AWS Kinesis destination.

  2. Enter the following, then save:

    • Stream Name: the name of the Kinesis data stream.
    • Region: the AWS region your stream lives in.
    • Role ARN: the role you'll create in the next step, for example arn:aws:iam::123456789012:role/ours-privacy-kinesis-write.
  3. Copy the External ID from the Destination Info panel on the destination's settings page.

  4. Create the role named in step 2. Email support@oursprivacy.com with the External ID for the trust policy to attach.

  5. Attach a permissions policy that lets the role write to the stream:

    {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Effect": "Allow",
          "Action": "kinesis:PutRecord",
          "Resource": "<KINESIS_STREAM_ARN>"
        }
      ]
    }
  6. Publish a new version to start sending events.

Each record's partition key is the visitor ID, so all of a visitor's events land on the same shard.

Event format

Each record is one event with its visitor and user records:

{
  "event": {
    "event": "Order Completed",
    "distinct_id": "evt_789",
    "time": "2026-01-15T18:04:12.000Z",
    "event_properties": {
      "order_id": "12345",
      "total": 99.99
    }
  },
  "visitor": {
    "visitor_id": "visitor_123",
    "first_seen_at": "2026-01-01T00:00:00Z",
    "email": "example@example.com"
  },
  "user": {
    "external_id": "user_456",
    "email": "example@example.com"
  }
}
  • event is the event as Ours Privacy received it, with its name, properties, and distinct_id.
  • visitor is the profile of the visitor who triggered the event.
  • user combines every visitor profile that shares the visitor's external ID.

The records arrive whole, contact details included, so field mappings and hashing don't apply to this destination. To keep an event from reaching it, stop dispatch with a custom mapping or a Global Data Governance rule.

Delivery guarantees

Events are delivered at least once, so a retry can deliver the same event more than once. Deduplicate on event.distinct_id, which stays the same on every delivery of an event. Every event from a visitor shares visitor.visitor_id, so it can't tell two events apart.


Next steps

Need help?

Reach out to support@oursprivacy.com.

How is this guide?

On this page