What to do when credentials have updated/changed #4018
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daldeano-segment
requested review from
rchinn1
and removed request for
a team
daldeano-segment
deleted the
daldeano-segment-facebook-lead-ads-patch-1-1
branch
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
|
Hi @daldeano-segment, thanks for the PR! In future PRs though, please wait for approval from a Docs team member before you merge. There are a few fixes we need to add here, that our grammar linter caught. I will fix those in a separate PR, but you can see the warnings on the Files Changed tab. |
This was referenced Jan 18, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Updating Getting Started Section with the following Information:
Note: It's important to note that when a connected account changes or updates their credentials, a new Facebook Lead Ads source will have to be created instead of solely reauthorizing the account as this is how FB has decided to operate. Reauthorization implies that a new token gets generated, but the token is not the sole link between Segment and Facebook. A Segment app is installed onto an FB Account and that will be the sprouting point from where tokens are generated.
The reason we can't disconnect and reconnect the CRM on Facebook with reauthorization is because the creation of a new token will mean to invalidate the rest of the tokens attached to the same Facebook account. For example, let's imagine you have a Facebook Account with three accounts: Account A, Account B, and Account C. You connect Segment to all of them and then generate tokens respectively. Later on, you decide for whatever reason to reauthorize the "Account A" page, the other tokens will be invalidated, and the pages will stop working.
Customer
Merge timing
Related issues (optional)