Upload respondent unique codes for target group live url
POST/demand/accounts/{account_id}/target-groups/{target_group_id}/respondent-unique-codes/live
Upload respondent unique code(s) for the given target group. They will be inserted into the live URL for each respondent entering the session. This will only be used in the context of the live URL of the target group (as opposed to test codes used with the test URL).
The URL for the given target group will require setup by using [%RESPONDENT_UNIQUE_CODE%]
An example of the live URL setup: https://example_live_url.com?[%RESPONDENT_UNIQUE_CODE%]
Processing Rules:
- Batch Size: A minimum of 1 and a maximum of 20 000 codes can be submitted in a single request.
- Code Format: Codes must consist solely of alphanumeric characters, hyphens (-), and underscores (_). Each code must have a length between 1 and 128 characters, inclusive. All leading and trailing whitespace will be automatically removed upon submission.
- Uniqueness and Handling of Duplicates: Within the context of this target group's respondent unique codes for live urls, only unique submissions are processed. If duplicate codes are present in the uploaded batch, only their first occurrence will be considered for addition. Codes that were previously already uploaded as live (i.e. not as test codes) for the specified target group will be ignored and won't be added again.
This endpoint is only applicable if your account has access to this feature. If your account does not have access, it will result in a 403 forbidden error. For more information, if you need this behaviour, please contact your account manager.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 429
- 500
Contains information on how many respondent unique codes were successfully uploaded. For example, already existing or duplicate codes will not be uploaded.
A request is not valid and can't be processed.
A request is unauthorized.
A requested is forbidden.
A requested resource isn't found.
Rate limiting
Response Headers
The traceparent header primarily carries essential trace context information, including the trace ID and parent span ID as defined by the W3C trace context specification. It's used to pinpoint the position of an incoming request within the trace graph, facilitating the tracking of distributed operations.
The tracestate header complements the traceparent header by providing additional contextual information, thereby allowing for the enrichment of tracing context and offering more fine-grained control.
How long the user agent should wait before making a follow-up request.
A request failed due to an internal error.