AWS Lambda

Use this page to connect Ours Privacy to AWS Lambda. Each event invokes your Lambda function in real time, so you can run serverless processing on your events — transformation, enrichment, custom hashing, validation, or routing into other AWS services.

Before you start

• An AWS account with a deployed Lambda function.
• The function's ARN.
• Permission for Ours Privacy to invoke the function. Contact support@oursprivacy.com and we'll share the details for the resource-based policy to attach.

Setup

1. Open the Destinations page and add a new AWS Lambda destination.
2. Enter the Lambda Function ARN of the function to invoke. The ARN includes the region, so no separate region is needed.
3. Save the destination and publish a new version to start sending events.

Functions are invoked asynchronously, so Ours Privacy does not wait on your function's response.

Event format

Each event is delivered as the JSON payload of the invocation, 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 Kinesis destination and AWS SNS destination — other real-time AWS destinations.

Need help?

Reach out to support@oursprivacy.com.