Skip to content

Clarify Engage API Subscription Status Update Process [DOC-532] #3081

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Jun 21, 2022
Merged

Clarify Engage API Subscription Status Update Process [DOC-532] #3081

merged 2 commits into from
Jun 21, 2022

Conversation

pwseg
Copy link
Contributor

@pwseg pwseg commented Jun 20, 2022

Proposed changes

  • Added sample payload code so users can properly format their Engage identify calls.
  • Moved up section comparing synchronous and asynchronous calls so that users understand the differences between the two before taking action.

Merge timing

  • ASAP once approved.

@pwseg pwseg added the content-update updates to content that are not new features, includes grammar fixes, added notes label Jun 20, 2022
@pwseg pwseg changed the title Clarify Engage API Subscription Status Update Process [DOC-542] Clarify Engage API Subscription Status Update Process [DOC-532] Jun 20, 2022
@pwseg pwseg merged commit 773722f into develop Jun 21, 2022
@pwseg pwseg deleted the engage-api-update branch June 21, 2022 16:04
@github-actions
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rchinn1 rchinn1 rchinn1 approved these changes

@markzegarelli markzegarelli Awaiting requested review from markzegarelli

Assignees
No one assigned
Labels
content-update updates to content that are not new features, includes grammar fixes, added notes
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@pwseg @rchinn1