> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/documentation/documentation-nl/integraties-marketingtools/linkedin-ads/waar-je-de-linkedin-partner-id-conversion-ids-en-api-token-vindt.md).

# Waar je de LinkedIn Partner ID, Conversion ID's en API-token vindt

Hoe je de LinkedIn Partner ID ophaalt en nieuwe conversies instelt om de Conversion ID's en API-token te vinden

LinkedIn werkt met drie waarden. De Partner-ID identificeert uw advertentieaccount en wordt gebruikt door de client-side Insight Tag. Een Conversie-ID identificeert één specifieke conversie, dus u hebt er één nodig voor elke conversie die u wilt meten. De API-token autoriseert server-side evenementen via de Conversions API. 

### **Waar u de Partner-ID kunt vinden**

Log in op uw [LinkedIn Campaign Manager](https://www.linkedin.com/campaignmanager).

Ga naar "Analyseren" in het linkermenu en selecteer vervolgens "Insight Tag".

### **Waar u de conversie-ID's kunt vinden**

### **Waar je het API-token vindt**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adpage.io/documentation/documentation-nl/integraties-marketingtools/linkedin-ads/waar-je-de-linkedin-partner-id-conversion-ids-en-api-token-vindt.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.