Tatari Events API Destination

Open Destinations in app

Use this page to connect Ours Privacy to Tatari using the Tatari Events API. Each event you forward is attributed against your Tatari campaigns, so you can measure how your TV and streaming ads drive purchases, sign-ups, and other outcomes — and keep that attribution working when the browser pixel can't fire.

This is the real-time replacement for the older S3-based Tatari destination. New Tatari customers should use this integration.

---

Before you start

• A Tatari account with an active campaign.
• Your Tatari API key and Tatari Client ID, both provided by Tatari during onboarding.
• Agreement with your Tatari CSM on the event names you'll send, so they're configured for reporting on Tatari's side.

Setup

1. Contact your Tatari representative and request an API key and your Tatari Client ID for the Events API.
2. In Ours Privacy, navigate to Connections → Destinations and add the Tatari Events API destination.
3. Paste in your API Key and Tatari Client ID.
4. Configure your event mappings and enable the destination.

Event types

Map each of your events to the event name Tatari expects — for example pageview, purchase, add_to_cart, sign_up, and more. Coordinate the exact names with your Tatari CSM so they're configured for reporting. To have purchase metrics populate in Tatari, send an event named purchase and include order_id and order_total in the event's custom properties.

A note on attribution quality

Tatari relies on IPv4 addresses and hashed email for deterministic matching between ad exposure and website conversions. For the strongest attribution:

• Aim for high IPv4 coverage, especially on conversion events. If your SDK is collecting IPv6, enable the force_ipv4 option — see the Web SDK documentation.
• Include a hashed email on purchase and conversion events where available.

---

Next steps

• Destinations overview
• Set up event mappings

Need help? Contact support@oursprivacy.com.