Amazon Connect Customer Profiles logo

Amazon Connect Customer Profiles

Amazon Connect Customer Profiles

UpOpen Sourcecloudby Amazon Web Services62· JavaScript· MIT

Amazon Connect Customer Profiles API merges contact-center customer info with multi-source CRM data into unified profiles.

Visit site ↗Source ↗Health checked 9h ago
Use it when

Native Amazon Connect integration (auto-match profile on call + screen pop)

Watch for

Heavy Amazon Connect dependency (not a standalone CDP)

First check

Enable Customer Profiles in Amazon Connect, configure data sources (Salesforce, Marketo, etc.), wait for ETL — agent views auto-display customer profiles.

Auth
CORS
No
HTTPS
Yes
Signup
?
Latency
23 ms
Protocol
REST
Pricing
Stars
62

Uptime · 30-day window

Probes: 1Uptime: 100%Avg latency: 23ms

GitHub activity

62JavaScriptMIT17 open issuesLast commit 110d ago
01

About this API

Customer Profiles is the customer data unification layer in Amazon Connect. A contact-center pain point: "agent takes a call without knowing who the customer is, what they bought, recent support tickets" — bad customer experience. Customer Profiles solves this: merge Connect call records, CRM (Salesforce), marketing platforms (Marketo), e-commerce platforms into unified customer profiles, with auto screen-pop on incoming calls. Differentiator: identity resolution — the same person may use different emails/phones across systems; Customer Profiles uses ML to unify. Compared to dedicated CDPs like Segment, heavy Amazon Connect dependency and weaker complex modeling, but easiest for Connect users.

02

What you can build

  • 1Agents see full customer background in contact center (orders, support history, preferences)
  • 2Customer identity resolution (same person across emails/phones)
  • 3Integrate Salesforce/Marketo/Zendesk data
  • 4Auto screen-pop customer profile
03

Strengths & limitations

Strengths

  • Native Amazon Connect integration (auto-match profile on call + screen pop)
  • Built-in connectors for multiple CRM data sources
  • ML-driven identity resolution

Limitations

  • Heavy Amazon Connect dependency (not a standalone CDP)
  • Less powerful data modeling than Segment/RudderStack
04

Example request

Generic template — replace <endpoint> with the real path from the docs.
curl https://github.com/mermade/aws2openapi/<endpoint>
05

Getting started

Enable Customer Profiles in Amazon Connect, configure data sources (Salesforce, Marketo, etc.), wait for ETL — agent views auto-display customer profiles.

06

FAQ

Can it be used standalone as a CDP outside Amazon Connect?+

Not recommended. Designed as Connect companion. For standalone CDP, use Segment/mParticle/RudderStack.

07

Technical details

CORS: NoHTTPS: YesSignup: ?Open source: Yes
Auth type
unknown
Pricing
unknown
Protocols
REST
SDKs
python, javascript, go, java
Response time
23 ms
Last health check
5/12/2026, 7:36:33 AM
08

Tags

09

More from Amazon Web Services