Azmarq · My CDP
One customer truth — from every lead source that matters
My CDP is Azmarq’s customer data platform: contacts, segments, webhooks, entry rules, broadcasts, and channel opt-ins — so journeys and agents never work blind.
Profiles · segments · consent · activate across channels
My CDP
One customer truth for messaging
Ingest
CTWA · forms · chat
Profiles
Identity · attributes
Opt-ins
WA · SMS · email
Segments
Journey-ready
Broadcasts
Audience sends
Activate
Inbox · AI · journeys
Contact sidebar
Riya Sharma
High intent · CTWA
- 01Ingest from ads, forms, and chat
- 02Store consent and channel preference
- 03Segment for journeys and drips
- 04Activate in Inbox, AI, and broadcasts
Multi-source ingest
CTWA · forms · chat · CSV
Consent-ready
WA · SMS · email · voice
Segments that fire
Journeys · drips · email
One activation layer
Inbox · AI · broadcasts
Clarify first
My CDP vs CRM vs spreadsheet lists
CRMs track deals. Spreadsheets scatter leads. My CDP is the audience and consent layer that powers Azmarq channels — so activation never starts from a stale export.
My CDP
Customer truth
Profiles, segments, opt-ins, entry rules, broadcasts, and webhooks — the activation graph for WhatsApp-first GTM on Azmarq.
CRM
Deal & pipeline
Great for opportunities and account ownership. Sync via webhooks when you need CRM stages — don’t force CRM to be your blast list.
Spreadsheet lists
Stale & risky
CSV dumps lose attribution, opt-ins, and real-time events. Import once to clean up — then live in My CDP.
Sources
Ingest every lead source that matters — into one graph
CTWA, FB Lead Ads, WhatsApp Direct, Instagram DM, web forms, CSV, webhooks, and manual entry all land as contacts your journeys and agents can actually use.
- CTWA Ads with campaign attribution
- FB Lead Ads, WhatsApp Direct, and Instagram DM
- Web forms, CSV imports, and manual adds
- Webhooks for events from your own stack
Ingest · Live sources
Identity
Profiles & attributes that stay actionable
One customer truth with the attributes GTM needs — source, score, stage, and channel history — so Inbox and Journeys never work from a blank slate.
- Unified contact profiles across channels
- Custom and lifecycle attributes for scoring
- Source and campaign context preserved
- Activity that agents and automations can read
Riya Sharma
My CDP · High intent
Channels
4
Events
126
Last
2m
Compliance
Opt-ins & consent that keep outreach legal — and effective
WhatsApp, SMS, email, and voice opt-ins live on the profile so campaigns and journeys respect consent instead of blasting from a messy spreadsheet.
- Channel opt-ins: WhatsApp · SMS · email · voice
- Consent hygiene before broadcasts and journeys
- India-aware outreach discipline
- Fewer “wrong channel” compliance surprises
Channel opt-ins
- WhatsAppOpted in
- SMSOpted in
- EmailOpted in
- VoiceNot set
Audiences
Segments your journeys can actually fire on
Build audiences from attributes, sources, and engagement — then activate the same segments in WhatsApp, SMS, email, drips, and Customer Journeys.
- Rule-based and attribute-driven segments
- High-intent CTWA and form audiences
- Shared lists for chat and email channels
- Audiences that update as leads arrive
Segment builder
Output audience
Ready for Journeys
Routing logic
Entry rules that match how leads actually arrive
Define when someone enters a segment or journey — by source, score, opt-in, or event — so automation starts at the right moment, not after a manual CSV upload.
- Source- and attribute-based entry conditions
- Score and stage thresholds for sales-ready views
- Align journey entry with how leads arrive
- Less re-keying between media and nurture tools
Entry rule · Journey
- 01Lead source = CTWA or form
- 02WhatsApp opt-in = true
- 03Score ≥ 70
- 04Enter · High-intent nurture
Reach
Broadcasts when one-to-many is the right move
Send to segments when you need reach — with opt-in awareness — without abandoning the profile graph for a disconnected blast tool.
- One-to-many sends from clean segments
- Opt-in aware audience selection
- Works alongside journeys for deeper nurture
- Same contacts agents see in Inbox
Broadcast · Segment
Active buyers · WhatsApp opted-in
Downstream
Activate across journeys, email, SMS — and chat
My CDP is the audience layer for Customer Journeys, Drip Campaigns, Email Marketing, Messaging SMS, AI Agent Studio, and Unified Inbox — one truth, many activations.
- Customer Journeys for multi-channel orchestration
- Email and SMS from the same segments
- Drips for lighter nurture sequences
- AI Agents and Inbox with full contact context
Activate from My CDP
Integration
Webhooks when your stack needs to talk back
Push or pull events so CRM, product, and billing systems stay aligned with Azmarq profiles — without flattening everything into another spreadsheet export.
- Inbound events to create or update contacts
- Outbound hooks for lead and lifecycle signals
- Keep external systems on the same contact IDs
- Bridge Azmarq CPaaS to the rest of your stack
POST /webhooks/azmarq
{
"event": "ctwa.lead.created",
"contact_id": "c_8f2a",
"channel": "whatsapp",
"segment": ["high_intent", "ctwa_summer"],
"opt_in": { "wa": true, "sms": false }
}Ingest
Leads arrive from everywhere.My CDP makes them one profile.
CTWA, FB Lead Ads, WhatsApp Direct, Instagram DM, web forms, CSV, webhooks, and manual entry — one graph for journeys, email, SMS, Inbox, and AI Agents.
Activate with Customer Journeys, Drip Campaigns, or Email Marketing without rebuilding lists elsewhere.
Where teams use it
One CDP across Indian GTM motions
Same profile graph — different activation mix. Built for teams who can’t afford WhatsApp, email, and ads living in three different lists.
Performance & CTWA teams
Ad chats and FB Lead Ads land as profiles with attribution — ready for journeys and inbox.
D2C & e-commerce
Unify form, WhatsApp, and IG interest so abandoned-browse and win-back share one audience.
BFSI & edtech
Counseling desks see score, source, and opt-in — not anonymous chats or stale CSVs.
Agencies
Client lead sources consolidate under Azmarq segments your journeys and reports can trust.
Product & growth
Webhook events and lifecycle attributes feed the same graph marketing activates on.
Enterprises
Replace spreadsheet stitching with one CDP that powers WhatsApp-first Indian GTM.
How it maps on Azmarq
Capability → what you run → module
My CDP is the audience layer. Use this map to see which module activates the next step.
Paid chat intake
CTWA · Meta attribution
CTWA Ads →Contacts & segments
Profiles · opt-ins · entry rules
My CDP →Multi-channel orchestration
WhatsApp + SMS + email + RCS + voice
Customer Journeys →Light nurture sequences
Tips · reminders · follow-ups
Drip Campaigns →Email campaigns & API
Lists · templates · transactional
Email Marketing →Human conversations
Multi-agent · context · SLA
Unified Inbox →AI qualification
First-touch · FAQ · booking
AI Agent Studio →
From ingest to activation
01
Ingest
Connect CTWA, forms, chat, CSV, webhooks, and manual sources.
02
Enrich
Profiles, attributes, and channel opt-ins on one contact.
03
Segment
Entry rules and audiences ready for journeys and broadcasts.
04
Activate
Journeys, drips, email, SMS, Inbox, and AI — same truth.
FAQs
Questions about My CDP
Straight answers for teams evaluating this module inside Azmarq CPaaS.
Talk to salesMy CDP is built for messaging-led engagement — contacts, segments, and channel activation inside Azmarq. Many teams still sync with their CRM for sales pipeline.
Spreadsheets go stale and don’t carry channel opt-ins or journey context. My CDP keeps one profile truth — sources, attributes, consent, and activation — for WhatsApp-first GTM.
CTWA, FB Lead Ads, WhatsApp Direct, Instagram DM, web forms, CSV, webhooks, and manual entry — so acquisition and chat sources land in one profile store.
Segments and entry rules power Customer Journeys, Drip Campaigns, Email, Messaging, and broadcasts — so activation stays tied to clean audiences.
Yes. WhatsApp, SMS, email, and voice preferences live on the profile so outreach stays compliant and relevant.
Yes. Use webhooks and entry rules so Azmarq stays connected to your CRM, product events, and ops stack without CSV round-trips.
Customer Journeys, Drip Campaigns, Email Marketing, Messaging SMS, broadcasts, Unified Inbox context, and AI Agents — one audience layer for the CPaaS.
Stop stitching leads in spreadsheets
See My CDP ingest CTWA, forms, and chat — then power Journeys and Inbox on one demo.
