Recommended launch path
Set up domains and compliance first, import clean audience data, launch a tested campaign, then connect events and automations once the core sending surface is stable.
Launch foundation
Getting Started
Go from account setup to first send with the right guardrails.
NevTan Engage sits between your data sources and your customers. Bring contact, commerce, CRM, or product events into Engage, then use the platform to render, personalize, schedule, deliver, and measure messages across channels.
Authenticate your sending domain
Add the DNS records Engage provides for SPF, DKIM, and DMARC. Verify the domain before production sends to protect trust and inbox placement.
Import contacts cleanly
Upload a UTF-8 CSV, map required fields such as email, choose opt-in status, and preserve existing unsubscribed contacts as suppressed records.
Create, preview, and schedule
Build a campaign from a template or blank layout, test desktop/mobile rendering, send a test email, then send now or schedule.
Product owner checklist
Set default From name and From email.
Add a physical mailing address for compliance.
Configure unsubscribe and double opt-in settings.
Connect Shopify or another data source if applicable.
Audience data
Contacts & Lists
Treat contacts as unified profiles, not just rows in a list.
A contact can hold email, phone, channel tokens, custom fields, engagement history, event history, and suppression flags. Lists are static groups; segments are dynamic audiences that update as profile or behavior data changes.
Contact record
Store standard fields, custom properties, consent data, channel tokens, engagement score, event history, and per-channel suppression status.
Lists vs segments
Use lists for fixed membership, signup groups, events, or loyalty cohorts. Use segments for behavioral, attribute, location, score, and list-membership rules.
Lifecycle and consent
Track Pending, Subscribed, Engaged, At risk, Unsubscribed, Bounced, Complained, and Suppressed states with audit-friendly consent fields.
Contact status guidance
Subscribed
Contact has opted in and can receive marketing.
Send
Unsubscribed
Contact opted out from marketing on a channel.
Do not send
Bounced
Hard bounce or invalid address.
Suppress
Complained
Recipient marked a message as spam.
Suppress
Pending
Double opt-in was sent but not confirmed.
Wait
Product owner checklist
Always import known unsubscribes rather than omitting them.
Use AND logic to narrow and OR logic to broaden segment membership.
Do not manually re-subscribe an opt-out without documented renewed consent.
Broadcast messaging
Campaigns
Build campaigns with audience, sender, content, testing, and reporting discipline.
Campaigns are one-time messages sent to a list or segment. Engage supports email, SMS, WhatsApp, push, A/B tests, and transactional-style use cases, with templates and merge tags to keep content personal.
Campaign workflow
Name the campaign, choose the channel, select list or segment targeting, configure sender details, design content, preview, test, and schedule.
Template editor
Use text, image, button, divider, spacer, product, social, HTML, and unsubscribe-footer blocks with global typography and spacing controls.
A/B testing and send timing
Test subject lines, preview text, content, sender details, or send time. Use fixed scheduling, recipient time-zone sending, or Smart Send.
Product owner checklist
Use fallback values for merge tags such as first_name.
Keep from_email on an authenticated domain.
Review campaign analytics within minutes of launch.
Lifecycle journeys
Automations
Create flows that react to lists, dates, events, segments, and API calls.
Automations are sequences of messages, delays, conditions, splits, tags, and webhook actions. Once activated, a flow runs continuously for each contact that matches the trigger.
Trigger types
Start flows when a contact joins a list, performs an event, reaches a date, enters or exits a segment, or when your app calls an API trigger.
Flow builder
Use the canvas to add email, SMS, wait, condition, split, update contact, webhook, and exit steps. Test with sample contacts before activation.
Transactional messages
Send order confirmations, password resets, billing receipts, and shipping notifications through API-triggered transactional workflows.
Product owner checklist
Use transactional messages for one-to-one operational events.
Honor SMS opt-in before adding SMS steps.
Monitor drop-off and step-level conversion to optimize journeys.
Inbox trust
Deliverability
Authenticate, warm up, and protect sender reputation before scaling.
Deliverability depends on identity, infrastructure, list quality, engagement, and content. Engage provides domain authentication, bounce handling, complaint monitoring, suppression, and warmup guidance.
Authentication standards
SPF authorizes Engage to send for your domain, DKIM signs each message, and DMARC tells mailbox providers how to handle failures.
DNS setup
Add the TXT and CNAME records exactly as shown, verify from Engage, and allow up to 48 hours for global DNS propagation.
Reputation controls
Warm IPs gradually, suppress hard bounces and complaints, segment inactive contacts, and monitor bounce and complaint thresholds.
Product owner checklist
Keep hard bounces below 2%.
Keep spam complaints below 0.1%.
Send re-engagement campaigns before removing inactive contacts.
Measurement
Analytics
Read performance from account health down to contact-level activity.
Engage reporting combines campaign metrics, engagement timelines, device and geography insights, contact scoring, revenue attribution, exports, scheduled digests, and webhook delivery.
Campaign reports
Review sent, delivered, opens, clicks, bounces, unsubscribes, complaints, conversion rate, and attributed revenue.
Engagement scoring
Use score bands from cold to highly engaged based on recency, opens, clicks, purchases, replies, and negative signals.
Revenue attribution
Attribute orders placed after opens or clicks within the configured attribution window, with e-commerce integration data.
Product owner checklist
Export reports manually as CSV when needed.
Schedule weekly or monthly email digests.
Deliver analytics events to a warehouse via webhook.
Connected stack
Integrations
Sync commerce, CMS, CRM, automation, and website behavior into Engage.
Native and platform integrations bring customers, orders, products, forms, and behavioral events into Engage so campaigns and automations can run from current data.
Commerce and CMS
Connect Shopify, WordPress, and WooCommerce to sync customers, products, orders, abandoned carts, and signup forms.
CRM sync
Use HubSpot and Salesforce syncs to keep contacts, lifecycle stage, company, owner, and deal information aligned.
Tracking snippet
Install the JavaScript snippet, identify contacts, and track custom events such as purchase_completed or product_viewed.
Product owner checklist
Use webhooks for real-time event delivery to external systems.
Use Zapier or Make for no-code handoffs.
Retry failed webhook deliveries with exponential backoff.
Build surface
Developer API
Use the REST API for transactional sending, custom events, and external workflows.
The API is designed for product and engineering teams that need programmatic message sends, behavioral tracking, custom integrations, and operational workflows.
Authentication
Create an API key from Settings > Developers > API Keys and send it as Authorization: Bearer YOUR_API_KEY.
Rate limits
Typical accounts are limited to 600 requests per minute. Enterprise accounts can request higher limits.
Consistent response format
Successful responses return status, data, and request_id. Errors return status, code, message, and request_id.
API contract
Base URL
https://api.engage.nevtan.com/v1
Auth header
Authorization: Bearer YOUR_API_KEY
Rate limit
600 requests/minute by default
Success
{ status, data, request_id }
Error
{ status, code, message, request_id }
Send transactional email
curl -X POST https://api.engage.nevtan.com/v1/email/send \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "customer@example.com",
"template_id": "tmpl_order_confirmation",
"data": {
"first_name": "Priya",
"order_id": "ORD-10045"
}
}'Track a custom event
curl -X POST https://api.engage.nevtan.com/v1/events \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"email": "customer@example.com",
"event": "product_viewed",
"properties": {
"product_id": "sku_123",
"category": "Shoes"
}
}'Product owner checklist
Use official SDKs for Node.js, Python, or PHP where possible.
Store API keys server-side only and rotate them regularly.
Use Postman collections to test requests before production rollout.
Governance
Account & Compliance
Keep access, billing, consent, and security controls operationally clear.
Account settings cover team roles, billing, invoices, credits, GDPR, CAN-SPAM, CASL, encryption, access control, API key security, activity logs, and data retention.
Roles and access
Assign Owner, Admin, Marketer, Analyst, Developer, or Billing roles so teams only access the areas they need.
Billing and credits
Manage plan, payment method, invoices, SMS/WhatsApp credits, and overage behavior from account billing settings.
Compliance operations
Maintain consent records, DPA status, unsubscribe handling, data export/delete workflows, and regional regulatory practices.
Product owner checklist
Use SSO on Enterprise plans.
Review API key and activity logs regularly.
Document retention and deletion workflows before launch.