Facebook pixel guidelines

The challenge
My team owned the Facebook pixel and I wanted to ensure we were speaking consistently both internally and externally about what the pixel is and what it does.

My role
I led the initiative from gathering input from other content creators to publishing final guidelines.

Results
-
Entered terms and usage guidelines into terminology database.
- Created tickets to fix incorrect usage on live site.
- Shared guidelines with content designers.
- Published to in-house wiki.
- The guidelines format became a template for other product-specific guidelines.

Skills
Nomenclature, Terminology, Standards and Guidelines


The process

  1. Talk with stakeholders from marketing, help content, engineering and policy to understand problematic terms and usage.

  2. Identify terms that need clarification and guidelines.

  3. Search and catalog live strings in database to understand current usage.

  4. Develop usage guidelines

The terms

  • activity vs. action

  • data vs. information

  • hashing vs. anonymizing

  • use data vs. process data

  • see vs. view

  • collect

  • target

  • track


Usage guidelines

For terms that needed guidance, I gave more nuance and definition around why one word might be preferable over another. This example looks at using activity vs. action. The differences might seem minor, but they are helpful for content designers who use certain words repeatedly in the context of their product.


Wiki article

The guidelines covered more than just usage. I included product description, naming history, messaging principles, and considerations around audiences and point of view when writing. I then published the guidelines on the in-house content design wiki.