Adjust UX writing

Here are some projects I worked on as a Product Content Strategist at Adjust, a mobile marketing analytics platform.

I was the third UX employee at the company. Content and design were previously driven by PM and eng.

 

Social Sharing Preview

In Adjust, users create tracker URLs that can be shared on social media. The “Social Sharing Preview” feature lets users customize the preview image and text that appear when their Adjust Tracker URL is shared via WhatsApp, Facebook, WeChat, and more.

My contributions

  • Researching, naming, and testing the feature. Some apps call this a “Link Preview,” but I found that this was unclear in the context of an Adjust app setting. Adjust users thought of tracker links and deep links, not URLs shared on social platforms. “Social Sharing Preview” tested most positively with users.

  • Writing the UX copy. Header, supporting text, input field labels, information text, button text, error text, and confirmation dialog.

Stakeholders

  • Product design (on the wireframe and prototype)

  • Developers (to learn the feature specs and constraints)

  • Product research (on the user testing)

  • Localization (for translations)

  • Product managers (to share the copy with developers)

Without technical or design constraints, I’d suggest these usability updates:

  • Indicate how many characters the user has overtyped (e.g., “151/150 characters” instead of “Use fewer characters” error)

  • Show a blank preview with placeholder image and text in the blank state (currently, the preview appears when all fields are filled)

  • Require the URL to start with http:// or https://

Hide tracker URLs

As part of a larger content audit, I rewrote the dialog that appears when a user hides a tracker URL from their Adjust dashboard.

BEFORE

AFTER

My changes:

  • Clarify the action. “Archive” implies that the tracker is no longer in use. “Hide” more clearly describes the function: the tracker doesn’t appear in the dashboard but still works normally and appears in the user’s statistics.

  • Clarify the dialog purpose. “Confirmation” is a filler word. “Hide tracker from dashboard?” explains what the user must confirm.

  • Shorten the supporting text. Keep all of the information.

  • Clarify the CTA. “Are You Sure?” is less helpful than “Hide Tracker.” That said, ideally there would be no CTA with X and checkmark buttons—just “Cancel” and “Hide” text buttons.

Adjust Testing Console

I rewrote the supporting text for the Adjust Testing Console.

before

after

My changes:

  • Focus on the user’s goal, not the feature’s ability. It’s about what the user wants to accomplish, not what we’ll “allow” them to do.

  • Avoid repeating information already conveyed through the design. Users can already see that they need to enter an Advertising ID—no need to describe that.

  • Make the text more approachable. Shorter, friendlier, just-as-helpful supporting text.