> For the complete documentation index, see [llms.txt](https://guide.linkd.kr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.linkd.kr/tip.md).

# 링크디 활용TIP

- [전체 상품 추적과 특정 상품 추적의 차이점을 알고 싶어요.](https://guide.linkd.kr/tip/1.md)
- [판매 데이터 업데이트 주기 알아보기!](https://guide.linkd.kr/tip/2.md)
- [필요없는 캠페인 또는 파트너스 목록에서 숨기기](https://guide.linkd.kr/tip/3.md)
- [파트너스 삭제하기](https://guide.linkd.kr/tip/4.md)
- [파트너스 직접 등록(모집없이 바로 등록하기)](https://guide.linkd.kr/tip/5.md)
- [\[파트너스\] 판매 링크 활용방법](https://guide.linkd.kr/tip/6.md)
- [‘SNS 간편가입’ 또는 ‘이메일ID’로 가입한 회원 쇼핑몰ID 입력 가이드](https://guide.linkd.kr/tip/7.md)


---

# 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://guide.linkd.kr/tip.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.