Skip to main content
Stay up to date with the latest changes to Trackly SMS.

​
August 2026

​
Resubscribe policy now applies to every opt-in path

breaking Allow Resubscriptions and the cooling-off window now govern every opt-in path, including double opt-in, except inbound keyword (START / text-to-join), which remains fresh inbound intent; resubscribed contacts enroll in matching journeys; a cooling-off of 0 days disables the wait.

​
Opt-in webhook: consentSource: "white_label" is reserved

breaking POST /api/v2/optins/webhook now also rejects consentSource: "white_label" with a 400, alongside the existing "journey" reservation. The value is reserved for consent captured through platform-generated white-label pages, so a TCPA audit record attributed to one can only be created by the platform itself.
  • Who is affected — any integration currently sending consentSource: "white_label". That request now fails with {"error": "consentSource 'white_label' is reserved"} — note the error body is the shared reserved-source message, so integrations matching the previous "journey"-specific string should match on the 400 status or the word reserved instead.
  • What to do — send a value that describes your own source. consentSource remains a free-form string up to 50 characters and every other value is unchanged.

​
Public opt-in submit: validation failures now use 4xx statuses

breaking POST /optin/submit now returns real HTTP statuses for rejected submissions instead of a universal 200: 400 for a malformed payload or unavailable consent text, 422 when the number is not SMS-capable, 429 when the daily validation budget is exhausted, and 503 for transient failures. The embedded widget and hosted page are unaffected — both read the JSON ok field, not the status. Custom integrations posting to this endpoint directly should branch on ok (or accept 4xx as rejection); an unknown token still returns 200 with ok: false so token validity cannot be probed. feature Offers created or updated through the API can now point at one of your TUNE or Everflow integrations — the same link the offer editor sets. Only a linked offer is picked up by that integration’s conversion sync, so an offer created through the API no longer has to be linked by hand in the app.
  • POST /api/v2/offers — accepts platform_config_id to link the new offer to one of your integrations.
  • PUT /api/v2/offers/{id} — sets the link, or clears it when you send platform_config_id: null. Omit the field and the existing link is left untouched.
  • GET /api/v2/offers and GET /api/v2/offers/{id} — every offer now returns platform_config_id (null when unlinked), and the list endpoint accepts ?platform_config_id= to return only the offers on one integration.
An ID that is not one of your integrations is rejected with platform_config_not_found, and a malformed one with invalid_platform_config.

​
Opt-in webhook: consentSource: "journey" is reserved

breaking POST /api/v2/optins/webhook now rejects consentSource: "journey" with a 400. The value is reserved for consent that originates from a journey’s double opt-in step, so a TCPA audit record attributed to a journey can only be created by the platform itself.
  • Who is affected — any integration currently sending consentSource: "journey". That request now fails with {"error": "consentSource 'journey' is reserved for journey-originated consent"}.
  • What to do — send a value that describes your own source instead (for example the form or platform name). consentSource remains a free-form string up to 50 characters and every other value is unchanged.
Public opt-in tokens are now scoped to the surfaces their type supports: the widget script, impression, submit and hosted-page endpoints resolve only popup, form, form_field_injection and text_to_join tokens; the subscribe short link resolves only text_to_join. A webhook or api token on those endpoints now returns the same not-found response as an unknown token. No embed code or hosted page has ever been issued for those types.

​
March 2026

feature Contacts who previously opted out can now resubscribe through a dedicated API endpoint, keyword replies, or the existing contacts API — with full consent tracking and provider-level sync.
  • POST /v2/contacts/resubscribe — Reactivates opted-out contacts with required consent proof (consent method, language, and optional user agent). Validates cooling-off periods, removes provider-level opt-out blocks, and optionally re-enrolls in a welcome journey.
  • START / UNSTOP keyword auto-resubscribe — When a contact replies START or UNSTOP, the reply handler now automatically reactivates them with consent tracking, rather than requiring manual intervention.
  • Resubscription toggle on sending lists — New allow_resubscriptions and cooling_off_days (default 30 days) settings on each sending list. When enabled, POST /v2/contacts will trigger the resubscribe flow for inactive contacts instead of silently ignoring them.
  • Twilio Consent Management API integration — For Twilio-provisioned lists, resubscription calls the Consent Management API to remove the carrier-level opt-out, ensuring the contact can actually receive messages again.

​
Compliance Engine

feature New paid add-on product that gives your audiences two layers of Do Not Call protection — helping you avoid TCPA litigation and stay off regulatory lists.
  • FTC National DNC Registry sync — Platform-wide nightly download of the full FTC Do Not Call list (~245M numbers). Contacts on the registry are automatically flagged so you can exclude them from sends.
  • Blacklist Alliance analysis — On-demand per-audience scan that identifies TCPA litigators, state-level DNC listings, and risk scores. Results appear as compliance badges on the Contact Lookup page, audience editor sidebar, and a dedicated Compliance Analyzer dashboard.
  • Audience filter dimensions — New is_litigator and state_dnc filter conditions in the audience query builder, so you can create audiences that automatically exclude high-risk contacts.
  • Billed per contact analyzed — charges appear on your account invoices.

​
Contact Card (vCard MMS) in Journeys

feature A new journey step type that sends your branded contact card as an MMS, so recipients can tap to save your business info directly to their phone.
  • Works in both welcome journeys and click trigger flows
  • Full editor with form fields for display name, phone, company, note, and a live preview
  • Supports macro expansion (e.g., {{first_name}}) in all vCard fields
  • Billed as 1 MMS segment via existing usage tracking
feature AI agents can now browse your offer catalog and generate tracked short links during conversations — no manual link management needed.
  • POST /v2/links/shorten — General-purpose link shortener API that works with SMS Offers (TUNE/Everflow tracking preserved) and raw URLs
  • Native agent tools — agents can list your offers and create tracked short links directly in a conversation.

​
AI Agents Subscription Billing

feature AI Agents is now a paid add-on product with its own subscription tier and metered LLM cost passthrough.
  • Product gating with upsell page for unsubscribed accounts
  • LLM cost tracking per conversation turn, charged to the account’s AI Agents balance
  • Provider/model selector in agent settings (Claude, GPT, Gemini)

​
Audience Filters & QoL

improvement Expanded audience targeting with new filter dimensions and more flexible logic.
  • 4 new filter dimensions: line type, phone validity, ad network source, and conversion count
  • Last revenue date (Last Converted) as a time-based filter
  • Per-condition AND/OR join operators — mix logic within a group without needing subgroups
  • Creatives and offers can now be scoped and managed per sending list
  • Contact export from both audience and list views

​
GSM-7 Character Normalization

improvement Messages containing “invisible” non-GSM-7 characters (smart quotes, non-breaking spaces, em dashes from Word or Google Docs) were silently forcing UCS-2 encoding, doubling segment counts. The platform now auto-normalizes these characters to their GSM-7 equivalents before sending. Emoji and intentional Unicode are left untouched.

​
Schedule Log Timezone Fix

improvement Schedule execution logs now show two distinct timestamps — Scheduled and Executed — both displayed in your account’s timezone. Previously, a single “Time” column showed the queueing claim time in the browser’s local timezone.

​
White-Label Resilience

improvement Improved reliability of white-label domain provisioning, including automatic retries.

​
Documentation Redesign

improvement Comprehensive docs overhaul: restructured navigation, standardized API endpoint templates, added API playground, new guides for platform limits, message segments, and production readiness.

​
February 2026

​
Signup Workflow Rework

improvement Redesigned the account signup flow with streamlined onboarding, improved form validation, and clearer step-by-step progression. Reduced signup-to-first-send time by removing unnecessary steps and adding contextual help.

​
Dual-Provider Phone Provisioning

feature Added support for provisioning phone numbers through multiple routes, with automatic failover. When the primary route’s inventory is unavailable for a requested area code, the system automatically attempts provisioning through the next available route.

​
Compliance Fixes

fix Fixed white-label banned term retry logic to prevent false rejections during provisioning. The content filter was incorrectly flagging brand names containing common substrings of banned terms.

​
January 2026

​
Import UX Improvements

improvement Redesigned the CSV import interface with real-time progress tracking, per-row error reporting, and drag-and-drop file upload. Large imports (100K+ contacts) now show estimated time remaining and can be cancelled mid-import.

​
BYOC Webhook Verification

feature Added webhook URL verification for Bring Your Own Carrier (BYOC) lists. Before sending is enabled, the system sends a test message and waits for the webhook callback to confirm the integration is working end-to-end. Verification expires after 15 minutes and can be re-triggered from the list settings page.

​
December 2025

​
OTP / 2FA Product

feature Launched one-time password (OTP) verification as a standalone product. Send verification codes via SMS with configurable expiry (30s-10min), per-number rate limiting, delivery confirmation webhooks, and automatic retry on failure. Available as a separate billing product with its own API key scope.

​
Click Triggers

feature Added the ability to trigger automated actions when a contact clicks a tracked link. Supported actions include journey enrollment, webhook dispatch, and custom field updates. Click triggers can be configured per-link with optional cooldown periods to prevent duplicate triggers from rapid clicks.

​
November 2025

​
Creative Studio with AI

feature Launched AI-powered creative generation using Claude, GPT, and Gemini. Generate, review, and iterate on message templates directly in the dashboard. Supports brand voice customization, A/B variant generation, and compliance pre-screening against carrier content policies.

​
Thompson Sampling for Creatives

feature Implemented multi-armed bandit (Thompson sampling) for automatic creative selection in campaigns. The system learns which creatives perform best across click-through rate, conversion rate, and opt-out rate, then allocates more traffic to winners while continuing to explore new creatives. Stats update every 6 hours with a 7-day rolling window.

​
October 2025

​
API V2 Launch

feature Released the v2 API with full CRUD endpoints for contacts, audiences, creatives, offers, schedules, revenue, and data import. Features include consistent error format with error codes, bulk operations (up to 1,000 contacts per request), cursor-based pagination, and X-Api-Key authentication with trk_ prefixed keys.

​
Tiered Billing V2

improvement Migrated to tiered per-segment billing: 0.0045/segmentforthefirst1Msegmentsina360−daycycle,0.0045/segment for the first 1M segments in a 360-day cycle, 0.003/segment after. Added automatic tier calculation, annual cycle tracking, and real-time usage dashboard. Billing is tracked per-segment (not per-message) to account for multi-segment messages.

​
September 2025

​
Free Tier

feature Introduced a free tier with 500 messages per month for new accounts. No credit card required to start sending. Usage resets monthly, and accounts are automatically paused (not deleted) if the limit is exceeded. Upgrade to paid is available at any time from the billing page. feature Added ToS acceptance flow with version tracking, non-dismissible acceptance modal on login, and public Terms of Service and Privacy Policy pages. ToS version changes trigger re-acceptance for all active users.

​
August 2025

​
CM Provider Integration

feature Added CM.com as an SMS provider option, expanding multi-provider support. CM routes are available for European and APAC destinations where CM offers better deliverability and pricing.

​
July 2025

​
Content Filtering

feature Added automated content filtering to scan outbound messages for banned terms and compliance violations before sending. Configurable per-account with allowlists for brand-specific terms. Messages that fail content filtering are blocked with a clear error code and the specific term flagged.

​
DLR Auto-Removal

improvement Implemented automatic contact removal based on delivery report (DLR) failure patterns. Contacts with 3+ consecutive hard bounces (error codes 30003, 30005, 30006) are automatically deactivated to protect sender reputation. Removed contacts are logged with the failure history and can be manually reactivated.

​
January 2024

​
Platform Launch

feature Initial release of the Trackly SMS platform with core messaging, contact management, list provisioning, scheduled sends, reply handling, and Discord integration for operational alerts.

​
Next Steps

FAQ

Common questions answered

Support

Get help from our team