Skip to content

Impact of exposing the source write key - AJS #4100

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.

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

Merged
merged 6 commits into from
Feb 7, 2023
Merged

Conversation

vanand17
Copy link
Contributor

Proposed changes

We have had multiple customers ask about the cons of exposing the write key in client side tracking, and we have a canned response in our macro which I believe could be made public.

Merge timing

NA

Related issues (optional)

@vanand17 vanand17 added the KCS label Jan 23, 2023
@vanand17 vanand17 marked this pull request as ready for review February 2, 2023 04:18
@vanand17 vanand17 requested a review from a team as a code owner February 2, 2023 04:18
@vanand17 vanand17 requested review from stayseesong and removed request for a team February 2, 2023 04:18
@stayseesong stayseesong merged commit c978778 into develop Feb 7, 2023
@stayseesong stayseesong deleted the vanand17-patch-6 branch February 7, 2023 18:20
@github-actions
Copy link
Contributor

github-actions bot commented Feb 7, 2023

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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants