> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gameball.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Attach Customer Tags

> Add tags to a customer profile for categorization and targeted engagement.

## Attach Customer Tags

Attach one or more tags to the specified customer.

<Info>
  Security: Provide both `apikey` and `secretkey` headers.
</Info>

<Info>
  <strong>Channel Merging Available</strong><br />
  If your system uses different customer IDs across multiple channels (e.g., online and offline), Gameball's channel merging feature helps unify customer profiles. By including the customer's mobile number or email (based on your merging configuration) with each request, Gameball will combine activities into a single profile. For more details, see the <a href="/tutorials/experiences/more/omni-channel">Omni-Channel Handling Guide</a>.
</Info>


## OpenAPI

````yaml POST /api/v4.0/integrations/customers/{customerId}/tags
openapi: 3.1.0
info:
  title: Gameball API
  description: >-
    Gameball REST API v4.0 - Complete API reference for integrating loyalty,
    gamification, and customer engagement features
  version: 4.0.0
servers:
  - url: https://api.gameball.co
security:
  - bearerAuth: []
paths:
  /api/v4.0/integrations/customers/{customerId}/tags:
    post:
      summary: Attach Customer Tags
      description: >-
        This API allows you to add tags to a customer profile in Gameball,
        identified by `customerId`. Attaching tags enables categorization of
        customer profiles, supporting organized management and targeted
        engagement based on specific attributes.
      operationId: attachCustomerTags
      parameters:
        - name: customerId
          in: path
          required: true
          schema:
            type: string
          description: Unique identifier for the customer
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CustomerTagsUpdateRequest'
      responses:
        '200':
          description: Tags attached
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Success'
      security:
        - apiKey: []
          secretKey: []
components:
  schemas:
    CustomerTagsUpdateRequest:
      type: object
      required:
        - tags
      properties:
        tags:
          type: string
          description: >-
            A comma-separated list of tags to apply or remove (e.g., 'gamer,
            highSpender').
    Success:
      type: object
      properties:
        success:
          type: boolean
        message:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
    apiKey:
      type: apiKey
      in: header
      name: apikey
    secretKey:
      type: apiKey
      in: header
      name: secretkey

````