> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/primer-support-legacy/understanding-performance/benchmarking-success.md). # Benchmarking Success #### Ad Audiences We have 2 keys ways to benchmark with the success of a Primer Ad Audience #### **Assessing** Primer audience metrics vs. native targeting in platform The main alternative to a Primer audience is native audience targeting in ad platforms like LinkedIn, Meta, and Google Step 1: Create campaign with native targeting for the audience criteria Step 2: Duplicate the campaign and use the Primer audience instead of the native audience Step 3: Compare the performance metrics of the two campaigns {% embed url="" %} #### Assessing Primer’s impact on last-click form submit While not a lot of B2B buyers last-click form submit from ad campaigns, it's still critical to measure. Step 1: Make sure you have UTM parameter tracking set up Step 2: Create ad campaigns that reference "Primer" in a UTM parameter Step 3: Assess the UTM source of your form submits {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.sayprimer.com/primer/primer-support-legacy/understanding-performance/benchmarking-success.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.