Skip to content

My CDP: Contacts, Segments, and Webhooks

My CDP is the customer data platform / address book on Azmarq. It stores people (phone/email), sources, tags, stages, segments, forms, webhooks, and scoring — then feeds SMS, WhatsApp, and RCS audiences, Team Inbox profiles, and Automations intake.

Portal parent: /contacts/... (default All Contacts). Menu header: My CDP.

What My CDP is

Treat CDP as the system of record for who you message. Channel HTTP is the system of record for the send.

You needUse
Create or merge a person, store attributes, check opt-inMy CDP in the portal
Build an audienceSegments (or a data view turned into a segment)
Send WhatsApp, SMS, or RCSBroadcasts → channel compose, or POST /v1/whatsapp, /v1/sms, /v1/rcs with opted-in destinations
Live chatTeam Inbox — sidebar is this profile
24/7 botAutomations — intake can carry workflowId
Delivery receiptsOmni webhooks
Contact created / stage / score eventsCDP outbound webhooks (portal)

All Contacts lists profiles CDP has accepted. A chat can exist in the inbox before the CDP copy is written — those are two writes, not one. An entry rule never creates the person; it runs only after the profile exists.

Warehouse (/warehouse) is operational imports and attribute permissions — related, but a separate module. Legacy groups, categories, tags, contact list still appear on compose screens.

Portal tools

ScreenWhat you do
MarTech OverviewPlaybooks / journey overview
Lead IntakeCapture a lead (manual, into the pipeline)
Form BuilderBuild/publish public lead forms (/cdp-forms, /cdp-forms/:formId)
All ContactsSearchable profiles (/cdp-contacts, profile /:contactId)
Attributes / custom fieldsDefine fields; optional PII, segmentation, capture channels
Data ViewsSaved filtered tables
SegmentsDynamic or static audiences (/cdp-segments)
Entry RulesTriggers on intake
WebhooksInbound/outbound integrations (/cdp-webhooks)
BroadcastsJump into SMS / WhatsApp / RCS compose with the selected audience
CDP ConfigSources, tags, pipeline stages, statuses, scoring
Legacy address bookGroups, categories, tags, contact list, attributes, data warehousing

Key entities

EntityMeaning
ContactPerson: phone and/or email, name, stage, source, tags, custom fields, opt-ins (optInWa, optInSms, optInEmail, optInVoice)
SourceWhere the lead came from (sourceType required on intake; sourceName)
SegmentAudience: dynamic (filters) or static (member list)
Tag / category / groupLabels still used on compose screens
FormPublic form by slug
Inbound webhookPublic POST by slug into intake
BroadcastNamed send that opens a channel composer

Capture channels on custom fields include: whatsapp, rcs, web_form, api, csv_import, ctwa, wa_direct.

Identity and merge

Match phone first. If there is no phone, match email. A person who arrives again is merged into that profile. Stored values are not deleted. Empty intake does not wipe a field that already has a value.

A contact needs phone or email. sourceType is required on intake.

  • Name
    phone
    Type
    primary key
    Description

    Normalised with country code. Search and merge use this value, so 91… and a local number without the country are not the same person.

  • Name
    email
    Type
    fallback key
    Description

    Used when the event has no phone. Duplicate policy in CDP Config is merge on phone, then email.

  • Name
    first source
    Type
    sticky
    Description

    The path that created the profile stays. Later arrivals are extra sources — that is multi-touch.

  • Name
    last source / last seen
    Type
    updated
    Description

    Each new intake or reply updates last source and last seen. First source does not move.

Default country (India unless you change it in CDP Config) is applied when someone types a number without a country code. Set this before import or Lead Intake.

How people enter

Every path writes the same profile. The source name on the contact tells you which path it was.

SourceWhat happensCDP write
ManualLead Intake: a teammate types phone or emailImmediate create or merge
ImportCSV or Excel. Rows with neither phone nor email are skippedMerge per row after column mapping
Web FormPublished Form Builder pageSubmit creates or merges as Web Form
WebhookOutside system POSTs to the inbound URL from My CDP → WebhooksCreate or merge as Webhook
APIPartner / portal intake with phone or emailNot a public Omni apikey route
WA DirectWhatsApp reply that is not from an adChannel log first, then CDP with WhatsApp opt-in
CTWAReply carries a Click-to-WhatsApp referralSame two-step write as WA Direct, source CTWA
RCSPerson replies on RCSChannel log first, then CDP with RCS opt-in
Facebook / InstagramLead ads and social intake when those sources are onCreate or merge with that source

A disabled source in CDP Config rejects new leads of that type.

Opt-in is the send gate

A segment membership is not permission to message. Broadcasts and journeys only reach a channel that is opted in and has the right address.

  • optInWa, optInSms, optInEmail, optInVoice are stored on the contact.
  • WhatsApp intake (WA Direct, CTWA, and forms/flows that collect consent) turns WhatsApp opt-in on.
  • DND and WhatsApp template policy still apply on the send path. Opt-in in CDP does not bypass WhatsApp template approval or the 24-hour session window.

When you send with the public API, you pass to / number yourself. Only put destinations that are opted in for that channel. CDP will not inject a segment into POST /v1/sms.

Segments and broadcasts

Use a data view when the question is which columns to see. Use a segment when the question is who to message.

  • Dynamic segment — rules, recalculated as profiles change.
  • Static segment — an explicit list of contacts.

Broadcasts do not send. My CDP → Broadcasts opens the channel compose you already use:

  1. Build the audience as a segment (or from All Contacts).
  2. Open WhatsApp, RCS, or SMS Broadcast (cdpAudience).
  3. Compose on that channel. People without that channel’s opt-in are not valid recipients, even if they sit in the segment.

HTTP send is unchanged: SMS, WhatsApp, RCS.

Forms and inbound webhooks

These are the public (no portal JWT, no Omni apikey) ways to add a lead from your site or app.

UseHow
Public formLoad the form by slug; submit values (+ optional countryCode)
Inbound webhookPOST leads to the inbound slug configured in CDP → Webhooks

Intake identity: a contact needs phone or email. sourceType is required.

Copy the inbound URL from the Webhooks card and treat it as a secret. Switch the webhook off to stop accepting calls without deleting the setup. Do not POST this payload to https://api.azmarq.com with apikey. There is no customer POST /v1/cdp and no public contact-list HTTP API.

Intake fields (webhook / form)

Common fields: phone, countryCode, name, email, sourceType (required), sourceName, sourceRefId, lifecycleStage, leadStage, status, ownerName, eventName, optInWa, optInSms, optInEmail, optInVoice, tags[], notes, city, state, country, customFields, UTM fields, optional workflowId / workflowName / stepKey.

Map those names in the webhook card. Use the field mapper in the portal — the public URL is not the Omni send host.

Legacy add-contact (address book): firstName, lastName, countryCode, number, emailId, groupId[], tags[], category[].

Outbound (CDP → your URL)

CDP calls your HTTPS endpoint when a contact is created, updated, the stage changes, or the score changes. Pick the events on the card. A failed outbound call is counted and does not roll back the contact that was just saved. Respond 2xx quickly; treat deliveries as at-least-once.

These are not SMS DLR, WhatsApp message_status, or RCS callbacks. Configure those on Webhooks. Keep Omni DLR and CDP outbound on different URLs.

How CDP connects

ProductHow CDP feeds it
SMS / WhatsApp / RCS composePick segment, source, group, category, or tag (cdpAudience)
Team InboxContact sidebar / attributes on the open chat
AutomationsIntake can carry workflowId / workflowName / stepKey
CTWA / forms / CSV / webhookAll land in the same contact profile

How the four products work together:

  1. My CDP stores people and segments.
  2. RCS / SMS / WhatsApp campaigns send to those audiences.
  3. Replies land in Team Inbox (WhatsApp and RCS).
  4. Automations answer 24/7 on WhatsApp/RCS; agents can take over or assign back to bot.
  5. Inbox shows the CDP profile; new leads from forms, CTWA, and webhooks return to CDP.

Until a contacts list API ships, three honest send patterns:

  1. Portal audience, portal send. Segment → Broadcasts → compose.
  2. Portal audience, HTTP send. Export opted-in numbers, then POST the channel API with apikey.
  3. Your app → inbound webhook → CDP. POST new people to the inbound slug. Let entry rules tag and segment them.
POST
/v1/sms
curl --location --request POST 'https://api.azmarq.com/v1/sms' \
--header 'Content-Type: application/json' \
--header 'apikey: YOUR_API_KEY' \
--data-raw '{
  "sender": "AZMARQ",
  "to": "91XXXXXXXXXX",
  "text": "Hello from a CDP-opted contact",
  "type": "TRANSACTIONAL"
}'

$API_BASE_URL is https://api.azmarq.com. Same apikey header as Authentication. Store messageId and match delivery reports.

Attributes, rules, and journeys

Attributes are fields you define (City, Budget, a form answer). Capture channels decide which intake paths may write the field. PII can mask the value.

Entry rules watch a profile that was just saved, then act (tag, segment, stage, score, field, outbound webhook). They never create the person.

Journeys live on MarTech Overview. Enrollment happens when a rule (or a later action) puts the contact on that journey. The contact still needs matching opt-in and address.

Console setup

CDP Config applies to new intake. Existing profiles keep their values until something updates them.

AreaWhat to set
GeneralDefault country, default lifecycle, default status, merge-on-phone-then-email, score recalculation
SourcesLabel, colour, on/off. Off rejects that intake type
TagsReusable names for profiles and entry rules
LifecycleRelationship: Lead, Prospect, Customer, VIP, Churned
PipelineSales steps: New, Working, Qualified, Won, Lost
ScoringBase plus source, lifecycle, opt-in, tags, completeness

Sensible order

  1. CDP Config — country, sources you actually use, tags, pipeline.
  2. Attributes — fields that forms, imports, and chats will fill; tick those capture channels.
  3. Form Builder or Lead Intake — prove one manual lead and one file import appear on All Contacts.
  4. Send a WhatsApp or RCS reply — confirm source and opt-in.
  5. Entry Rules — one rule, test, then turn it on.
  6. Segments — audience from that tag or from a data view.
  7. Broadcasts — open channel compose for that audience.
  8. MarTech Overview — confirm profiles, rules, and journeys are moving.

Typical errors

SituationWhat it means
Intake without phone and emailMatcher has nothing to key on — row skipped
Missing sourceTypeRequired on intake
Empty segmentFilters match nobody, or opt-in excluded everyone
Inbox thread, no All Contacts rowCDP write failed or source is off
Messaging a segment with no opt-inMembership is not consent
Import without default countryOne person splits into two profiles
Expecting POST /v1/cdpNot published. Use form slug or inbound webhook

Next: send on SMS, WhatsApp, or RCS; staff Team Inbox; publish Automations.

Was this page helpful?