DavidWells / DavidWells/analytics

AWS Pinpoint identifier not found - Address

Open
#364 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.7k
Forks
267
PR merge metrics
No merged PRs in 30d

Description

Hi!
Im working on AWS Pinpoint integration and everything looks amazing, but except the identify function seems can't pass the Address into Pinpoint (https://docs.aws.amazon.com/pinpoint/latest/apireference/apps-application-id-endpoints.html) which affect the endpoint can't be used in AWS console, any missing from my side to make this work?

analytics.identify('user-id-xyz-6', {
firstName: 'bill',
lastName: 'murray',
email: 'bill@example.com',
Address: 'bill@example.com'
})

Endpoint {
Attributes {lastSessionDate: ["2023-02-22T05:10:03.909Z"], lastSession: ["641b9679-3fa0-4c5c-bf2b-a059310718d5"],…}
Demographic {AppVersion: "awesome-app-testing-123456@0.0.0", Locale: "zh_tw", Make: "Google", Model: "Chrome",…}
Location {}
Metrics {sessions: 139, pageViews: 56}
RequestId "5a73c0e7-dca8-4071-bcbd-69ec859b06e4"
User {UserId: "user-id-xyz-6",…}
}

Right now all traits is stay under Endpoint.User object, I would like to see any quick around to make Address under Endpoint object.
Thank you!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the AWS Pinpoint integration's analytics.identify entry point and trace how traits are mapped into the endpoint request. Compare the generated endpoint data with the AWS Pinpoint endpoints API; done means Address appears in the endpoint-level location data rather than only under Endpoint.User.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, javascript
Domain
analytics, api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.