Commita6eb20c

and

authored

Update src/connections/destinations/catalog/actions-fullstory-cloud/index.md

Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>

1 parentf5c74fc commita6eb20cCopy full SHA for a6eb20c

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -50,7 +50,7 @@ The FullStory cloud mode destination sends information about your users and rela`
`50`	`50`
`51`	`51`	`###Why am I getting a ‘404 Not Found’ error?`
`52`	`52`
`53`		`-This applies totheorginal 'Identify User' and 'Track Event' actions. The user for which the API request is being made can not be found in the identified set of users within your FullStory organization. If you expect that user to already exist, you can search for that User ID in FullStory to confirm. Also, double check that you are using an API key from the same organization.`
	`53`	`+If you are usingtheoriginal 'Identify User' and 'Track Event' actions and encounter a "404 Not Found" error, the user for which the API request is being made can not be found in the identified set of users within your FullStory organization. If you expect that user to already exist, you can search for that User ID in FullStory to confirm. Also, double check that you are using an API key from the same organization.`
`54`	`54`
`55`	`55`	`Data sent server-side for users must match an already existing userId that was sent from a client-side connection.`
`56`	`56`

Comments

(0)