Give your publishers exactly the tags they need — and nothing more

Why this matters

Tags are where the real story of a call lives: the keyword that drove it, the utm, the source data, the dialer info. But not every tag is meant for every set of eyes. Historically that left you with an awkward choice — share everything with a publisher, or share nothing.

This feature removes that trade-off. You decide, tag by tag, which keys a publisher is allowed to see. That granularity lets your publishers track performance and improve their own payouts using real call data, while the rest of the tags on the call — internal notes, margins, buyer details — remain completely invisible to them.

What's new

On a publisher's collaborator page, under Permissions, you'll find a Tags selector: "Below you can select additional tag keys they should have access to." Pick the tag keys you want that publisher to see, save, and the access flows through automatically to every place tags appear.

By default a publisher sees none of your tags. Granting access here is the exception you opt into, per publisher — so you stay in control and nothing leaks by accident.

Note that this feature has been on Retreaver for a long time but not that visible and easy to consume.

Once granted, the publisher sees those tags in four places:

1. On the call detail page

The permitted tags appear inline on the call, alongside the rest of the call's details.

2. On the calls list

The same tags surface in the calls index, so a publisher gets the picture at a glance without opening each call.

3. As a column in exports

Permitted tags become a selectable column in reports, so publishers can group, filter, and export by the tags you've shared with them.

4. In the API

When a publisher pulls their calls through the API using their own API key, the tags on each call are automatically limited to just the keys you granted them. No extra parameters, no risk of over-sharing — the same permission rules apply.

curl -X GET "https://api.retreaver.com/api/v1/calls.json" \
  --data-urlencode "api_key=PUBLISHER_API_KEY" \
  --data-urlencode "created_at_start=2026-06-01T00:00:00Z" \
  --data-urlencode "created_at_end=2026-06-30T23:59:59Z" \
  -G

Each call in the response includes a tags field — and it contains only the tag keys that publisher is permitted to see. Every other tag on the call is omitted entirely.

Permissions

• Granting tag access is done by an admin on the publisher's collaborator page, under Permissions → Tags.
• A publisher only ever sees the tag keys explicitly granted to them. With no tags granted, they see no tags at all — in the UI, in reports, and in the API.
• Access is scoped per publisher, so two publishers can be granted entirely different sets of tags on the same calls.