Adding a new third-party integration (LeadsBridge) to Facebook AI ad product

As part of a major redesign of an AI ad product integration flow, we were also rolling out a new third-party integration with a company called LeadsBridge. The goal was to make it easier for developers to integrate with a new third-party connection. I collaborated with my Facebook product and marketing teams, along with the team at LeadsBridge, to update documentation and even marketing materials.

• When I dove into the documentation, I found there was very little alignment between LeadsBridge documentation and Facebook’s materials. Lots of inconsistencies in how things were explained and different terms used for the same thing.
• Also had to be sensitive with this new relationship to not be too overbearing with LeadsBridge that we were going to come in and “fix everything” for them.
• After getting all the documentation updated, we also had to test the integration to get all the bugs out before launch. This also involved updating documentation with any changes needed.
• I had countless meetings with LeadsBridge to audit their material, review their own glossaries, compare them with what we were using at Meta, and discuss aligning terms.

Final Leadsbridge email I wrote to announce the new integration. Terms matched the in-product user flow as well as Meta’s developer documentation and marketing materials: “connect,” “quality,” “leads who are most likely to convert,” etc.

I collaborated with some amazing partners at Leadsbridge to rewrite this article about the new integration, matching terms with Facebook’s language for a consistent user experience.