AWS Kinesis

Use this page to connect Ours Privacy to Amazon Kinesis. Each event is written to your Kinesis data stream in real time, so you can process and analyze high-volume event streams with low latency.

Before you start

• An AWS account with a Kinesis data stream to write to.
• The stream's name and region.
• Permission for Ours Privacy to write to the stream. The setup uses a cross-account IAM role — contact support@oursprivacy.com and we'll share the trust policy to attach.

Setup

1. Open the Destinations page and add a new AWS Kinesis destination.
2. Enter the following:
   • Stream Name — the name of the Kinesis data stream.
   • Region — the AWS region your stream lives in.
   • Role ARN — the IAM role that grants Ours Privacy permission to write records.
3. Save the destination and publish a new version to start sending events.

Records are partitioned by visitor, so events for the same visitor land on the same shard.

Event format

Each event is written as a JSON record with the event, visitor, and user records:

{
  "event": {
    "event": "Order Completed",
    "event_properties": {
      "order_id": "12345",
      "total": 99.99
    }
  },
  "visitor": {
    "visitor_id": "visitor_123",
    "first_seen_at": "2024-01-01T00:00:00Z",
    "email": "example@example.com"
  },
  "user": {
    "external_id": "user_456",
    "email": "example@example.com"
  }
}

Delivery guarantees

Events are delivered with at least once semantics — each event may arrive one or more times due to network retries or transient failures. To process events idempotently, deduplicate on visitor.visitor_id and/or event.distinct_id. These identifiers stay consistent across duplicate deliveries of the same event.

Next steps

• Destination overview — how destinations fit into the event pipeline.
• Data mapping — control which events and properties are sent.
• AWS Lambda destination and AWS SNS destination — other real-time AWS destinations.

Need help?

Reach out to support@oursprivacy.com.