Tags Tags are labels that help you organize, segment, and automate interactions with your subscribers. They’re one of the most powerful features in Sequenzy.
Tags are simple string labels attached to subscribers. Each subscriber can have multiple tags, and tags can be added or removed at any time.
{ "email" : "[email protected] " , "tags" : [ "customer" , "pro-plan" , "newsletter" , "webinar-attendee" ] } 1. Segmentation Target specific groups in campaigns:
Send product updates to customer tagged subscribers
Exclude churned subscribers from promotional emails
Target trial users with conversion campaigns
2. Automation Triggers Start sequences when tags are added:
When customer tag is added → Start onboarding sequence
When churned tag is added → Start win-back sequence
When enterprise tag is added → Notify sales team
3. Personalization Customize email content based on tags:
{{#if tags.customer}} < p > Thanks for being a valued customer! </ p > {{else}} < p > Ready to upgrade? Check out our plans. </ p > {{/if}} 4. Analytics Track subscriber segments over time:
How many trial users convert to customer?
What’s the churn rate for pro-plan vs starter-plan?
Sequenzy includes built-in system tags for common use cases:
Tag Description Auto-Applied leadPotential customer Manual customerPaying customer Via sync rules trialIn trial period Via sync rules activeActive subscription Via sync rules cancelledCancelled subscription Via sync rules churnedChurned customer Via sync rules past-duePayment failed Via sync rules refundedReceived refund Via sync rules inactiveNo recent activity Manual
System tags can be automatically applied through sync rules when connected to payment providers like Stripe.
Tag Normalization Tags are automatically normalized when created:
Converted to lowercase
Spaces replaced with hyphens
Special characters removed
"Pro Customer" → "pro-customer" "VIP_User" → "vip-user" "Newsletter!" → "newsletter" Single Tag curl -X POST "https://api.sequenzy.com/api/v1/subscribers/tags" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "email": "[email protected] ", "tag": "customer" }' curl -X POST "https://api.sequenzy.com/api/v1/subscribers/tags/bulk" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "email": "[email protected] ", "tags": ["customer", "pro-plan", "2024-cohort"] }' Auto-Creation When you add a tag, Sequenzy automatically:
Creates the subscriber if they don’t exist
Creates the tag definition if it doesn’t exist
Adds the tag to the subscriber
This makes integration seamless—no pre-configuration required.
Tags can be removed through:
Dashboard - Manual removal in subscriber profileSequences - “Remove Tag” action in automationsSync Rules - Automatic removal when events occur
Trigger: When Tag Added Start a sequence when a subscriber receives a tag:
Trigger: contact_added_tag "customer" │ ▼ ┌─────────────────┐ │ Welcome Email │ └─────────────────┘ │ ▼ ┌─────────────────┐ │ Wait 3 days │ └─────────────────┘ │ ▼ ┌─────────────────┐ │ Onboarding Tips │ └─────────────────┘ Modify tags during sequence execution:
┌─────────────────┐ │ Send Upgrade │ │ Offer Email │ └─────────────────┘ │ ▼ ┌─────────────────┐ │ Wait for Event │ │ "purchase" │ │ Timeout: 7 days │ └─────────────────┘ │ ├── Event received ────────────┐ │ │ ▼ ▼ ┌─────────────────┐ ┌─────────────────┐ │ Add tag: │ │ Add tag: │ │ "converted" │ │ "offer-expired" │ └─────────────────┘ └─────────────────┘ Condition: Has Tag Branch logic based on tags:
┌─────────────────────┐ │ Condition: │ │ has_tag "customer" │ └─────────────────────┘ │ ┌────┴────┐ │ │ Yes No │ │ ▼ ▼ ┌─────────┐ ┌─────────┐ │ Upsell │ │ Convert │ │ Email │ │ Email │ └─────────┘ └─────────┘ When creating a campaign, filter recipients:
Include subscribers with tags: Exclude subscribers with tags: Example: Feature Announcement Target active customers on pro plan:
Recipients: All subscribers Filters: - tags contains "customer" - tags contains "pro-plan" - tags not_contains "churned" Sync Rules Sync rules automatically manage tags based on events. When an event occurs, specified tags are added and removed.
Learn About Sync Rules Configure automatic tagging based on events
Default Sync Rules Event Tags Added Tags Removed saas.purchasecustomerlead, past-due, cancelled, churnedsaas.churnchurnedcustomer, cancelled, past-duesaas.cancelledcancelledcustomersaas.payment_failedpast-due— saas.refundrefunded— saas.trial_startedtrialleadsaas.trial_ended— trial
Best Practices 1. Use Descriptive Names ✓ "webinar-jan-2024-attendee" ✓ "ebook-marketing-guide-downloaded" ✓ "pro-plan-annual" ✗ "tag1" ✗ "promo" ✗ "temp" 2. Create a Tagging Strategy Define your tag taxonomy before implementation:
Lifecycle tags:
lead, trial, customer, churned
Plan tags:
free-plan, starter-plan, pro-plan, enterprise-plan
Behavior tags:
email-opened-30d, highly-engaged, at-risk
Source tags:
source-organic, source-paid, source-referral
3. Avoid Tag Proliferation Too many tags become unmanageable. Consolidate similar tags:
✗ "clicked-email-jan", "clicked-email-feb", "clicked-email-mar" ✓ "email-engaged" (reset monthly) ✗ "purchased-product-a", "purchased-product-b", "purchased-product-c" ✓ "customer" + customAttribute: purchasedProducts 4. Use Events for Temporary States For actions that happen multiple times, use events instead of tags:
✗ Tag: "viewed-pricing-page" (adds up over time) ✓ Event: "page_viewed" with properties: { page: "pricing" } Maintain a reference of what each tag means and how it’s applied:
Tag Description Applied By customerHas paid subscription Sync rule: saas.purchase enterpriseEnterprise plan customer Manual newsletterSubscribed to newsletter Signup form
