Skip to content
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

Privacy blog #512

Merged
merged 12 commits into from
Jan 16, 2024
Merged

Privacy blog #512

merged 12 commits into from
Jan 16, 2024

Conversation

LauraDuRy
Copy link
Contributor

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

added text
two images for the privacy blog
Copy link

render bot commented Jan 11, 2024

Copy link

vercel bot commented Jan 11, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
website ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 15, 2024 0:08am

Copy link

render bot commented Jan 11, 2024


- **Tags** are snippets of code added to a website to track your activity and collect data. For example, a tag can be used to track how many people visit a particular page on a website or to collect information about what products you are viewing. The most well-known tool for this is [Google Tag Manager](https://www.semrush.com/blog/beginners-guide-to-google-tag-manager/). It allows you to manage all of your website tags in one place.
- **Pixels** are small, transparent images that are embedded in a website. When you visit a website with a pixel, your browser sends information about your visit to the company that owns the pixel. This information can include the user's IP address, browser type, and the URL of the page you’re visiting. It is a beneficial tool to retarget website visitors with banner or social ads.
- **Cookies,** first-party are set by the website you’ve visited mainly to improve your experience on that website, whereas different websites, such as Google Analytics set third-party cookies. Third-party cookies are the ones that are often used to track you across platforms, mostly meant for advertising purposes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other 2 points sounds like a sentence, but this one reads hard. (beginning)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated!


## The consequences of removing marketing pixels, tags, and cookies

The above mentioned allowed us to analyze user behavior, measure the effectiveness of ad campaigns, retarget ads, and, to some extent, personalize the user experience. There are hardly any growth or marketing teams that don’t rely on them, and as stated in [this article from Osano](https://www.osano.com/articles/marketer-friendly-privacy-software), privacy regulations make it a lot harder for growth and marketing teams to do their work. Go to any privacy footer on any website, and you will read an essay on all the data that is being tracked. But this is precisely what we are challenging: does removing pixels, cookies, and tags make growth’s life harder? Let’s take a look.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this article from Osano to just article from Osano.

Clickable texts should make sense out of context as well. this is giving it context.

If you really want to keep this, we can do it before link. But I don't think its nessessary.


- **Attribution**: It can be challenging to attribute conversions to specific marketing campaigns without the ability to track users across different devices and websites. This can make it challenging to know which campaigns drive the most results and make informed decisions about future campaigns.
- **Segmentation**: Without the ability to track user behavior, preferences, and interests, it is challenging to segment users into different groups based on their interests and preferences. This can make delivering targeted messaging and experiences difficult for different user segments.
- **Reporting**: It can be challenging to generate comprehensive reports on marketing performance without the ability to track users across different devices and websites. This can make it challenging to track progress over time and identify areas for improvement.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

challenging twice in here, let's find synonym.


- **UTM data** helps us track attributions from different campaigns, mediums, sources, and specific content. We can tell whether a visitor is coming from a specific link or not, for which we currently use [dub.co](https://dub.co/), an open-source alternative to Bitly. This helps us determine whether sponsoring a newsletter was effective or if a piece of content brought us traffic. But that is about as far as we will go. As soon as you leave our website, we lose all your information and would like to keep it that way.
- **Open source analytics alternatives.** We use privacy-friendly alternatives like [Plausible](https://plausible.io/about) to help us analyze our website and Console data. It is an open-source analytics platform with one of the highest [privacy standards](https://plausible.io/privacy) I have seen. It helps us get demographic and user behavior data in a privacy-friendly manner.
- **First-party data.** We get a lot from users, like emails and names from authentication. We use it for login purposes, so you don’t have to enter your login details over and over again and add them to our CRM, HubSpot, for email communications. But with this data also comes great responsibility, and with our recent GDPR compliance announcement, we are not only upholding strict data privacy but also certified with the European General Data Protection Regulation (GDPR) standards.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesnt sound like proper beginning of sentence

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but also certified with the European General ...
but are also certified with the ...

I think adding are is grammatically correct. Please check with someone from US/UK, or Grammarly.

Copy link
Contributor

@TorstenDittmann TorstenDittmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

technical part ✅


## Building a privacy-friendly and open-source growth stack

We still have the necessary tools to improve our product, the developer experience, and analyze our website traffic. That said, we will continue to explore the possibilities of moving towards a fully open-source and privacy-friendly growth tech stack. Not only do we feel it is the right thing to do, but it is also rooted in our culture. We want to treat you as we want to be treated by any vendors we use. For now, this has been the most sensible decision we could have made for Appwrite and the community. We are excited to take privacy further and further, so who knows where we will stand a year from now.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want to treat you as we want to be treated by any vendors we use

Powerful sentence, I think it should be used in the beginning of the article. It makes it very clear we understand the pain point, and have been on receiving end too.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we compress this image or get a smaller sized version of it? 3.19MB might be overkill and lead to slower loading times @LauraDuRy

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on it

Copy link
Member

@eldadfux eldadfux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some comments on Discord.

@TorstenDittmann TorstenDittmann merged commit fb82c7e into main Jan 16, 2024
3 checks passed
@TorstenDittmann TorstenDittmann deleted the privacy-blog branch January 16, 2024 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants