Blog Marketing
Marketing OKRs: examples and how to set them

A marketing OKR pairs an objective that sets a priority with key results that show whether the team made progress. Initiatives are the work the team chooses to try. Keeping those three parts separate makes it harder to mistake a task list for an outcome.
An example with a baseline and a time frame
A marketing and sales team reviews demo requests from the previous 12 weeks. They use the same agreed qualification criteria for each request: an organization they can serve, a problem the product addresses, and a person involved in the decision. Sales accepted 40 of 100 complete requests. Over the same period, 80 of the 100 received a first response within two business days.
In this example, a complete request has all required fields submitted: contact email, organization, and reason for the demo. Duplicates are removed using the same rule in both cycles. Sales qualification is assessed afterward and does not determine which requests enter the denominator. At the end of the cycle, wait until the last requests have had their full two-business-day response window before calculating the response rate.
For the next 12-week cycle, the team proposes this OKR:
Objective: Help sales receive demo requests that are a better fit for the accounts we can serve. KR 1: In the 12-week baseline, sales accepted 40 of 100 complete requests (40%). In the next 12 weeks, achieve an acceptance rate of at least 55% among all complete requests received, using the same qualification criteria. KR 2: In the baseline, 80 of 100 complete requests (80%) received a human first response within two business days. In the next 12 weeks, have at least 95% of all complete requests receive a human first response within that time.
This is a hypothetical example, not a recommended target or a HeyMark result. Before adopting it, the team would need to confirm that its records distinguish complete requests, sales applies the same acceptance criteria, and someone can meet the response time. If the definitions or data source change, the baseline and target are no longer directly comparable.
An initiative might be to review the form and test a new context question. “Publish 20 posts” could also be an initiative if the team explains why it is testing that work. On its own, it does not show that requests became better qualified or that response time improved.
What each part does
The objective describes the change the team wants in clear language. In this example, the priority is to give sales better-fitting requests and respond on time.
Key results turn that change into observable evidence. Each has a measure, starting point, target, time frame, and counting rule. For each period, calculate requests accepted by sales ÷ all complete requests received, and requests answered on time ÷ all complete requests received. Rejected, unreviewed, and late requests stay in the denominator. Future volume does not have to be 100: keep the total request count and accepted count alongside the rate. A higher rate does not show better fit if it came with far fewer requests; agree on a minimum volume before the cycle. If no requests arrive, report that there is no rate to calculate.
Initiatives describe actions the team controls. It can review form questions, agree on criteria with sales, or test an information page. It cannot guarantee that an action caused an improvement. When reviewing the OKR, compare the work completed with the observed results and other changes in the business.
Microsoft Learn describes this separation between objectives, measurable key results, and initiatives. Its guide also recommends keeping the number of objectives and results small at each level. Read the guide to writing OKRs.
OKRs, SMART goals, and KPIs answer different questions
SMART checks that a goal is specific, measurable, achievable, relevant, and time-bound. A KPI is a measure the team monitors, such as the share of requests sales accepts; an OKR connects a priority with key results the team reviews during a cycle. You can use a KPI inside a key result, but the metric alone does not define the change or the work. For social-media examples, see the guides to SMART social media goals and KPIs by goal.
For example, “improve the acceptance rate” names a direction but leaves out the baseline, denominator, and time frame. “Publish 20 posts this quarter” counts activity but may not reflect progress on the objective. A clearer key result states the starting value, target, period, and definition.
Before you close the cycle
Agree with sales on what counts as an accepted request and who records it. Check that past and future data use the same categories. Then set a review date and log any change in criteria. If requests come from several channels, do not credit the change to marketing until you have checked how their source is assigned.
A useful OKR ends in a decision the team can revisit: continue an initiative, change it, or stop it based on the results and the team’s capacity. The framework organizes the work; it does not predict which target the team will reach.
The cover is an AI-generated illustration.
Plan your next post in HeyMark.
Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.