Support

What Relay shares, and what never leaves Tapper

On this page

Relay sends your ad platforms only what they need to count a conversion and match it to an ad. Personal details leave Tapper hashed, and some never leave at all.

What Relay sends

  • The conversion. Its name, its time, its value and currency, and its order ID.
  • The platform's own click ID, when Tapper captured it at the visit. Google Ads gets the Google click ID, Meta gets the Meta click ID, and so on. Each platform only ever gets its own.
  • Meta's browser ID, on Meta only, when Tapper captured it at the visit.
  • Hashed e-mail and phone, where the platform takes them and consent allows. They are sent only as SHA-256 hashes, never in plain text.

What never leaves Tapper

Relay never sends your customer's name, city, postcode, IP address, browser details or device IDs. Every conversion is checked before it is sent, and one that holds any of them is stopped.

  • Hashed e-mail and phone go to a platform only where your visitor's consent allows.
  • A conversion from a visitor who withdrew consent is not sent.
  • When you send events to Relay from your own server, you state the consent with each event.

In Relay > Activity, a conversion held for consent shows its reason: No consent on record, Consent was withdrawn or Recorded before consent.

Your connections stay locked

The tokens that connect Tapper to your ad platforms are stored encrypted. Each conversion goes straight from Tapper to the platform, server to server.

See every send

Relay > Activity lists every conversion Relay sent or held, with its time, source, ad account, value, status and reason. Filter it by status and platform, or search by event name or order ID.

Still need help?

Chat with our team and mention this article.