How to properly track 2-step unsubscribes

Taguchi provides several methods to track when users unsubscribe, with these interactions visible in each subscriber’s profile interaction history.

There are two main methods to set up an unsubscribe page in Taguchi. Both approaches require you to create a web activity:

1. Using the //[client].taguchimail.com/public/subscriber endpoint, where [client] is your organisation’s Taguchi server name.
2. Using an endpoint generated from an integration configured as API: V5 Endpoint (Unauthenticated).

---

Tracking Unsubscribe Clicks

Before diving into the methods, it’s important to ensure that unsubscribe clicks are being tracked properly.
When a subscriber clicks the unsubscribe link in an email, you can track this action by appending the following token to the end of your unsubscribe URL:

{unsubscribe:track}

This will log an unsubscribed event with the label “track” in the subscriber’s interaction history, allowing you to see when and from which campaign the unsubscribe was initiated.

---

Method 1: Using //[client].taguchimail.com/public/subscriber Endpoint

When using this method, you’ll need to include two hidden input values — evt and sevt — in your form, in addition to the unsub_lists field.
The unsub_lists field removes a subscriber from specific lists and logs an unsubscribed event with "track" in their data.

<form ...>
    <input type="hidden" name="evt" value="up" />
    <input type="hidden" name="sevt" value="" />
</form>

Parent Event (sevt)

The sevt input links the logged event to a previously logged parent event, typically the campaign or email from which the subscriber accessed the unsubscribe page.
This linkage allows Taguchi to identify the exact source email tied to the unsubscribe action.

After submitting the unsubscribe form, the subscriber’s interaction history will display both the unsubscribed and update events.

Method 2: How to properly track 2-step unsubscribesMethod 2:

Method 2 uses an integration-based endpoint. It achieves the same output in the interaction history as Method 1 but uses JSON payload data instead of a form.

---

💬 For further assistance, contact Taguchi Support.

---