Tatari (S3, Legacy)

Use this page to configure the legacy S3-based Tatari destination, which sends conversion events to Tatari for TV advertising attribution and optimization.

Legacy integration. This S3-based Tatari destination is being replaced by the real-time Tatari Events API destination. New Tatari customers should use the Events API. Existing customers on this S3 path can continue using it while everyone migrates over.

Tatari is a TV advertising platform that helps brands measure and optimize their TV ad spend. With this destination, you send conversion events to Tatari for attribution and optimization.

---

Setup

Ours Privacy already has a shared S3 bucket configured with Tatari, so you do not need to set up a new bucket. You only need a dedicated S3 prefix for your account.

1. Contact your Tatari representative and request a new S3 prefix for your account. You can do this directly without going through Ours Privacy.
2. Allow 24 to 48 hours for Tatari to provision the prefix.
3. Once you have your prefix, navigate to Connections > Destinations in your Ours Privacy app.
4. Search for "Tatari" and select it, then click Configure Tatari.
5. Enter your S3 prefix along with the bucket name and region provided by Tatari.
6. Configure your data mappings and enable the destination.

Configuration

Tatari uses a server-to-server integration over S3. When Tatari provisions your prefix, they provide three values you enter in the destination configuration:

• S3 Bucket: the shared S3 bucket name for the server-to-server integration.
• S3 Bucket Region: the AWS region of the S3 bucket.
• S3 Prefix: your unique prefix within the bucket. This is what you request from Tatari and is specific to your account.

Data mapping

Event properties are mapped to Tatari's expected format in the destination configuration UI, where each field is documented with tooltips. The default mapping sends the event name, user agent, IP address, session and user identifiers, page URL, referrer, hashed email, and any custom event properties.

The visitor's email defaults to a normalized SHA-256 hash before it is sent, so raw email addresses do not leave Ours Privacy on the default mapping.

To have purchase-related metrics populate in Tatari, include order_id and order_total in the event's custom properties for the purchase event. For Tatari to populate these metrics, the event Tatari receives must be named purchase. Obfuscated event names will not work.

IPv4 requirement

Tatari and other TV advertising platforms rely on IPv4 addresses for deterministic attribution between TV ad impressions and website visits. If your SDK is collecting IPv6 addresses, Tatari cannot match conversions to TV impressions accurately.

Enable the force_ipv4 option in the Ours Privacy Web SDK when using the Tatari destination. This routes events through the IPv4 ingest endpoint. See the Web SDK documentation for configuration details.

---

Next steps

• Tatari Events API destination: the real-time replacement for this S3 integration.
• Web SDK for JavaScript: install the SDK and enable force_ipv4.

For more information about Tatari's integration capabilities, visit their developer documentation.