DirectIQ is a US-based email marketing platform serving SMBs and mid-market with drag-and-drop editor, transactional API, and standard automation flows. The unsubscribe mechanism uses the {UNSUBSCRIBE_URL} merge tag auto-injected into every campaign footer, and DirectIQ emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the list level with US CAN-SPAM baseline enforcement. This guide covers the tag, the US SMB baseline, and how to verify the setup end to end.
DirectIQ unsubscribe link
| Tag syntax | {UNSUBSCRIBE_URL} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with US CAN-SPAM baseline |
| Config path | Settings > Sender identity > Footer |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in DirectIQ
Place the merge tag exactly as shown below in the email template. DirectIQ replaces it at send time with a signed URL scoped to the recipient and campaign.
{UNSUBSCRIBE_URL}For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="{UNSUBSCRIBE_URL}">Unsubscribe from this list</a>Auto-embedded in every campaign footer
Yes, automatic for authenticated sending domains The recipient's mailbox provider (Gmail, Yahoo) uses the List-Unsubscribe-Post header to expose the native one-click button on the message. Requires domain authentication with DKIM and DMARC.
DirectIQ US CAN-SPAM baseline provides physical postal address, honest From line, and 10-business-day suppression. Senders targeting EU or Canadian audiences should configure double opt-in and consent documentation matching GDPR or CASL respectively. Transactional API sends bypass marketing consent per transactional exemption. Multi-account team collaboration features support agency use cases.
Testing your DirectIQ unsubscribe link
- Send a test message to a controlled Gmail address you own via the DirectIQ campaign preview action
- Click the footer unsubscribe link and confirm the opt-out on the landing page
- Check the subscriber or contact record: the status should be Unsubscribed within seconds
- Verify the RFC 8058 headers in Gmail: open the message, click three dots, then Show original. Look for
List-UnsubscribeandList-Unsubscribe-Post: List-Unsubscribe=One-Click
Want the full 222-platform reference?
See the pillar guide with the compliance landscape, the RFC 8058 deep dive, and the unsubscribe tag for every ESP: How to add an unsubscribe link: the complete 2026 guide →
How to add the DirectIQ unsubscribe link (step by step)
DirectIQ default templates include the unsubscribe link in the footer, but custom HTML templates require the tag inserted manually.
- Open your campaign or template in the DirectIQ editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
{UNSUBSCRIBE_URL}. DirectIQ replaces it at send time with a signed URL scoped to the subscriber. - Wrap it in an anchor:
<a href="{UNSUBSCRIBE_URL}">Unsubscribe</a>. - Configure the sender identity under Settings > Sender identity > Footer.
- Send a test to a seed address and verify the rendered link routes to the DirectIQ-hosted preference page.
US CAN-SPAM baseline and international audience
DirectIQ US CAN-SPAM baseline provides physical postal address, honest From line, and 10-business-day suppression. Senders targeting EU or Canadian audiences should configure double opt-in and consent documentation matching GDPR or CASL respectively. Transactional API sends bypass marketing consent per transactional exemption. Multi-account team collaboration features support agency use cases with client account isolation.
RFC 8058 one-click headers
DirectIQ added RFC 8058 one-click unsubscribe automatically ahead of the Google and Yahoo February 2024 requirements. The List-Unsubscribe and List-Unsubscribe-Post headers inject on every marketing send from domains authenticated under Settings > Sender identity. SPF and DKIM records must be verified. US data residency is the default.
Transactional API alongside marketing broadcasts
DirectIQ transactional API sends bypass marketing consent per transactional exemption (order confirmations, password resets, receipts). Configure the transactional API distinctly from marketing broadcast infrastructure to keep the classification clear. Some jurisdictions require distinct sending IPs or subdomains for transactional vs marketing to prevent cross-contamination of sender reputation and consent state.
Frequently Asked Questions
What is the DirectIQ unsubscribe tag?
The merge tag is {UNSUBSCRIBE_URL}. DirectIQ replaces it at send time with a signed URL scoped to the subscriber. Use it inside an anchor: <a href="{UNSUBSCRIBE_URL}">Unsubscribe</a>.
Does DirectIQ support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. DirectIQ injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Settings > Sender identity.
Does DirectIQ enforce GDPR double opt-in?
Not by default (US CAN-SPAM baseline). Senders targeting EU audiences should configure double opt-in and consent documentation practices manually to satisfy GDPR expectations.
Does the DirectIQ transactional API respect opt-outs?
Transactional sends (order confirmations, password resets, receipts) bypass marketing opt-out per transactional exemption. Configure the transactional API distinctly from marketing broadcast infrastructure to keep classification clear.
How does DirectIQ compare to Pinpointe or Sender.net?
All three are US-based SMB email platforms with CAN-SPAM baseline. DirectIQ emphasizes agency multi-account features. Pinpointe focuses on B2B ABM. Sender.net targets budget-conscious SMBs. Vendor choice depends on use case.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
