Run a re-consent campaign
Ask people you already hold data about to give or refuse consent.
You may hold data about people from before you collected consent: an old customer list, a CRM export, sign-ups from before the DPDP Act. A re-consent campaign asks those people, through a private link to your Trust Center.
Three rules shape it:
- Importing someone records nothing. A campaign's list is not consent. Only the person's own answer goes into the ledger, and no answer means no consent.
- Nothing is pre-ticked. Every purpose starts unticked. Save records what was ticked as granted and everything else as refused.
- The email is a notice, not marketing. It names the purposes, links to your privacy notice and has an unsubscribe link. Replies go to your DPO.
Create a campaign
Consent Management, then Re-consent, then New campaign.
| Field | What to enter |
|---|---|
| Name | For you only, for example "Customers before 2025" |
| What to ask about | Your active data purposes whose lawful basis is consent. Cookie categories belong to the banner, and legitimate-use purposes are not asked |
| A note to include | Optional text shown in the email and on the page |
| Links work for | 14, 30, 60 or 90 days, counted from when each person's link is first exported or emailed |
| Reminder | Pactbase emails only: one reminder after 3, 7 or 14 days to anyone who has not answered, or none |
The campaign is made under your published privacy notice. Without one, it cannot be created.
Add people
Upload a CSV. The email column is required. An id column (customer_id, user_id and so on) and a name column are optional. Columns are found by header, in any order. Large files go up in batches of 2,000. The result says how many were added, already in the list, not an address, and opted out earlier. People who opted out earlier stay in the list but are never emailed and never exported.
Reach them
Either way, or both, the links are the same:
- Export links (CSV) with
email,external_id,name,link,link_expires_atandanswered. Send them from your own tool (Zoho Campaigns, Mailchimp, your CRM, an n8n workflow), from your own domain. - Email them. Pactbase sends the email. There are daily and per-minute sending limits, so large lists go out over several days.
Follow up
The funnel shows People, Reached (emailed or exported), Opened (the link was opened), and Answered, split into agreed to all, some or none, plus opted out of emails and not delivered. Filter the list by each, and search email, id and name.
Close this campaign stops the links and any sending. Answers already given stay in the ledger.
What the person sees
The link opens a page that shows who is asking, the address the request was sent to, and the purposes, all unticked, with a link to your privacy notice. Save records the choice. While the link works they can come back and Change my choices. Don't email me about this again opts them out of your campaign emails and leaves their choices as they are.
What gets recorded
Each Save writes one ledger row per purpose, all sharing one Consent ID, with the person's email, IP address, browser and the live notice version. It fires consent.updated (and consent.withdrawn for a purpose they had granted and now refuse) with campaign: { id, name, external_id }, so your CRM or n8n flow can update the record by your own id. See Webhooks.
An erasure request pseudonymises these rows like any others and removes the person from every campaign. An opt-out is kept only as a hash, so it outlives the erasure without keeping the address.
Not tracked: email opens (pixels are unreliable and out of place in a consent request) and bounces the provider reports later. A send the provider refuses outright shows as Not delivered.