> ## Documentation Index > Fetch the complete documentation index at: https://api.fanvue.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # List clicks on a creator's tracking link > Every click on the link, newest first, with cursor-based pagination. Unlike the tracking-link users endpoint this includes clicks never matched to an account, which have a null `userUuid`, so a partner can reconcile click-level data without one request per fan. Only allowlisted tracking parameters are returned in `metadata`; see the field description for the list. Pass the previous response's `nextCursor` as `cursor` to fetch the next page; it is null on the last page. A cursor is only valid for the link it was issued for. > [!NOTE] > > **Required scopes** > > * `read:tracking_links` — Read tracking links and the users associated with them, including per-user tracking metadata. > * `read:creator` — Access creator profiles, content, and creator-specific information. ## OpenAPI ````yaml /openapi-v1.json get /v1/creators/{creatorUserUuid}/tracking-links/{uuid}/impressions openapi: 3.1.0 info: title: Fanvue API version: '0.1' servers: - url: https://api.fanvue.com security: [] paths: /v1/creators/{creatorUserUuid}/tracking-links/{uuid}/impressions: get: summary: List clicks on a creator's tracking link description: >- Every click on the link, newest first, with cursor-based pagination. Unlike the tracking-link users endpoint this includes clicks never matched to an account, which have a null `userUuid`, so a partner can reconcile click-level data without one request per fan. Only allowlisted tracking parameters are returned in `metadata`; see the field description for the list. Pass the previous response's `nextCursor` as `cursor` to fetch the next page; it is null on the last page. A cursor is only valid for the link it was issued for. operationId: listCreatorTrackingLinkImpressions parameters: - $ref: '#/components/parameters/ApiVersionHeader' - schema: type: string format: uuid required: true name: creatorUserUuid in: path - schema: type: string format: uuid description: Tracking link UUID required: true description: Tracking link UUID name: uuid in: path - schema: type: string description: Opaque pagination cursor from a previous response's `nextCursor` required: false description: Opaque pagination cursor from a previous response's `nextCursor` name: cursor in: query - schema: type: integer minimum: 1 maximum: 50 default: 15 description: 'Number of items to return (1-50, default: 15)' required: false description: 'Number of items to return (1-50, default: 15)' name: size in: query responses: '200': description: Clicks on the tracking link content: application/json: schema: type: object properties: data: type: array items: type: object properties: createdAt: type: string format: date-time description: When the link was clicked userUuid: type: - string - 'null' format: uuid description: >- The user the click was matched to, or null for a click never matched to an account (the visitor did not sign in or sign up afterwards). Anonymous clicks are expected. metadata: type: - object - 'null' additionalProperties: type: string description: >- Tracking parameters captured from this click's landing URL. Only these query parameters are returned; any other parameter on the landing URL is omitted: `utm_campaign`, `utm_content`, `utm_medium`, `utm_source`, `utm_term`, `ref`, `click_id`, `clickid`, `clickId`, `fv_click_id`, `fvc_id` and `client_reference_id`. Null when none of them were present. required: - createdAt - userUuid - metadata description: Clicks on the tracking link, newest first nextCursor: type: - string - 'null' description: >- Opaque cursor for the next page, or null when there are no more results total: type: - number - 'null' description: >- Total number of items, or null when a count is not computed for this list required: - data - nextCursor - total example: data: - createdAt: '2024-01-15T00:00:00.000Z' userUuid: f47ac10b-58cc-4372-a567-0e02b2c3d479 metadata: utm_source: tiktok client_reference_id: lead-xyz123 - createdAt: '2024-01-14T00:00:00.000Z' userUuid: null metadata: utm_campaign: spring_launch nextCursor: eyJjcmVhdGVkQXQiOiIyMDI2LTAxLTAxIn0 total: null '400': description: >- Bad Request - API version not supported OR validation failed OR invalid UUID content: application/json: schema: oneOf: - $ref: '#/components/schemas/UnsupportedVersionError' - $ref: '#/components/schemas/ValidationError' - $ref: '#/components/schemas/InvalidUuidError' '401': $ref: '#/components/responses/UnauthorizedResponse' '403': $ref: '#/components/responses/UnauthorizedResponse' '404': $ref: '#/components/responses/NotFoundResponse' '410': $ref: '#/components/responses/SunsetVersionResponse' '429': $ref: '#/components/responses/RateLimitResponse' security: - BearerAuth: - read:tracking_links - read:creator components: parameters: ApiVersionHeader: name: X-Fanvue-API-Version in: header required: true schema: type: string default: '2025-06-26' example: '2025-06-26' description: API version to use for the request schemas: UnsupportedVersionError: type: object properties: error: type: string message: type: string required: - error - message description: API version not supported ValidationError: type: object properties: errors: type: array items: type: string required: - errors description: Request validation failed InvalidUuidError: type: object properties: message: type: string required: - message description: Invalid UUID format provided responses: UnauthorizedResponse: description: Unauthorized Response content: application/json: schema: type: object properties: error: type: string required: - error NotFoundResponse: description: Not Found Response content: application/json: schema: type: object properties: message: type: string required: - message SunsetVersionResponse: description: API version no longer supported (sunset) content: application/json: schema: type: object properties: error: type: string message: type: string nextVersion: type: string required: - error - message RateLimitResponse: description: Too many requests - rate limit exceeded headers: Retry-After: description: Number of seconds to wait before retrying the request schema: type: integer X-RateLimit-Limit: description: The maximum number of requests allowed in the current window schema: type: integer X-RateLimit-Remaining: description: The number of requests remaining in the current window schema: type: integer X-RateLimit-Reset: description: The Unix timestamp (seconds) when the rate limit window resets schema: type: integer content: application/json: schema: type: object properties: error: type: string required: - error securitySchemes: BearerAuth: type: oauth2 description: >- OAuth 2.0 access token, presented as a JWT bearer token in the `Authorization` header. Obtain a token via the authorization-code flow; the scopes granted to the token determine which operations it may call. flows: authorizationCode: authorizationUrl: https://auth.fanvue.com/oauth2/auth tokenUrl: https://auth.fanvue.com/oauth2/token refreshUrl: https://auth.fanvue.com/oauth2/token scopes: read:self: >- Access your own user profile information, including basic account details and settings. read:chat: >- Read chat conversations, messages, and chat-related data. This includes viewing chat lists and message history. write:chat: >- Create new chats and send messages. This scope is required for any chat-related actions that modify data. read:experience: >- Exchange a fan's experience token for the resolved experience and the fan's identity, so an embedded fan-facing experience can render the right content. write:experience: >- Request that the creator publish or unpublish a fan-facing experience. The app mints a request token; the creator confirms and Fanvue performs the change. read:fan: Access fan-related data and information within the platform. read:post: Read posts, including post details, comments, likes, and tips. write:post: Create, edit, and manage posts and content on behalf of users. read:media: Access media files, images, videos, and other content assets. write:media: >- Upload, modify, and manage media files and content assets. Also required for vault folder management. read:creator: >- Access creator profiles, content, and creator-specific information. write:creator: Modify creator profiles, settings, and creator-specific data. read:insights: >- Access analytics, metrics, and insights data for performance tracking. read:tracking_links: >- Read tracking links and the users associated with them, including per-user tracking metadata. write:tracking_links: Create and delete tracking links. read:agency: Read agency information, including the agency's team members. write:agency: >- Manage agency team members and invites, including inviting new team members and creators. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.