CSJ prime_rit Configuration in Taku
1. Feature Overview and Prerequisites
The CSJ backend has added an prime_rit layer. Starting September 6, non-GroMore CSJ code slots must be bound to an prime_rit before they can be submitted. For details, contact your CSJ AM, or view the CSJ backend notice or view the official CSJ notice
To support this platform change, Taku has also upgraded the relevant features. If you use Taku's CSJ auto-creation, Smart Manager, or OpenAPI code slot creation, follow the guide below to use the upgraded features.
This capability requires the CSJ account to have API auto-creation authorization. Once enabled, Taku provides the same prime_rit options as the CSJ backend and supports creating and binding placements.
- Taku's CSJ auto-creation feature provides a CSJ prime_rit (prime_rit) option.
- For CSJ accounts with API auto-creation authorization enabled, historical CSJ ad sources created in Taku support individual or batch prime_rit binding.
- Smart Manager configuration also provides a CSJ prime_rit option, using the same interaction as auto-creation.
- When creating CSJ code slots through Taku OpenAPI, pass the new prime_rit field.
- CSJ code slots under GroMore are not affected by this change and continue to follow the existing process.
Important: Once an prime_rit and code slot are bound in the CSJ backend, this binding cannot be modified. Existing valid bindings in Taku are shown as read-only. Without API auto-creation authorization, configure the relationship in the CSJ backend instead. We recommend enabling CSJ auto-creation for the account.
2. Create New CSJ Code Slots Automatically in Taku
Go to Mediation Management, click "Add Ad Source", select CSJ, and enable auto-creation. After entering the CSJ account and app, select an prime_rit under "CSJ prime_rit" that matches the CSJ backend. If no suitable placement exists, you can create one directly.
After selecting a placement, complete the remaining ad source fields and submit. Taku will submit the selected placement prime_rit to CSJ and create the code slot.
If you create the code slot manually in the CSJ backend, select an prime_rit there according to the CSJ workflow, then enter the code slot ID in Taku. When manually creating a CSJ ad source in Taku, you do not need to fill in a CSJ prime_rit.
3. Bind prime_rits to Historical CSJ Ad Sources
For CSJ accounts with API auto-creation authorization enabled, you can bind an prime_rit to historical CSJ ad sources in Taku.
Note: Once API access is enabled, all historical ad sources, including those created manually or automatically, support ad placement binding.
Individual: Open the ad source edit page, select the corresponding prime_rit, and save.
Batch: Open the batch ad source editing page, select multiple existing ad sources, bind them to the same prime_rit, and submit.
Ad sources selected for batch processing must belong to the same CSJ account and the same CSJ app.
Existing valid bindings are shown as read-only; ad sources with no binding or an invalid binding can be rebound.
When you bind an prime_rit in Taku, the result is synced to the CSJ backend in real time. If the CSJ account linked to the app has auto-creation enabled, Taku also updates the CSJ code slot configuration stored in Taku via API every night. If a historical code slot is bound to an prime_rit in the CSJ backend, Taku will display that binding after the sync; no manual binding in Taku is required.
4. Configure CSJ prime_rits in Smart Manager
If a historical Smart Manager configuration is missing an prime_rit, it will show "Configuration exception". This does not affect existing ad sources, but the configuration must be completed before Smart Manager can automatically create new CSJ code slots. We recommend completing it promptly.
In Smart Manager's "CSJ and Taku Ad Source Configuration", select the corresponding prime_rit under "CSJ prime_rit". This setting is used when Smart Manager automatically creates new CSJ code slots.
If a historical configuration is missing an prime_rit, the page shows "Configuration exception". You can open an individual configuration to complete it, or click "Batch Set CSJ prime_rits" to process multiple configurations at once.
5. Create CSJ Code Slots through Taku OpenAPI
When creating non-GroMore CSJ code slots through Taku OpenAPI, pass the new prime_rit field in the request. The field must contain a valid prime_rit ID under the current CSJ account and app.
API documentation:
Taku Ad Source Auto-Creation API
Official CSJ API Documentation
6. Q&A
1. How should a newly created CSJ code slot be configured?
When using Taku auto-creation, select or create the CSJ prime_rit; Taku submits prime_rit to CSJ. When using Taku OpenAPI, pass prime_rit in the request. If you create the code slot directly in the CSJ backend, select the prime_rit there and then enter the code slot ID in Taku.
2. How should historical CSJ code slots be handled?
Follow the CSJ backend requirements for historical code slots (see the CSJ backend notice in the screenshots below). If you need to bind an prime_rit to a historical code slot, you can do so in Taku as described in Section 3, or in the CSJ backend.
Whether historical code slots need to be rebound and whether this affects ad fill should be confirmed against the official CSJ notice or with your CSJ AM.
3. When will Taku show an prime_rit bound in the CSJ backend?
The CSJ account linked to the app must have auto-creation enabled. Once this condition is met, Taku synchronizes code slot configuration via API every night, and the binding made in the CSJ backend will appear in Taku after the sync.
4. Why can't an existing prime_rit binding be changed?
After an prime_rit and code slot are bound in the CSJ backend, the binding cannot be changed there. Existing valid bindings in Taku are also shown as read-only.
5. What should I do if API auto-creation authorization is not enabled?
If the CSJ account does not have API access, or the account has not authorized auto-creation in Taku, Taku does not provide the relevant prime_rit configuration capability. Configure the prime_rit and code slot relationship in the CSJ backend instead. We recommend enabling CSJ auto-creation for the account.
6. Do CSJ code slots under GroMore need an prime_rit?
No. CSJ code slots under GroMore are not affected by this change and continue to follow the existing process.
7. What should I do if Smart Manager shows "Configuration exception"?
This means the historical Smart Manager configuration is missing a valid prime_rit prime_rit. Complete it in Smart Manager as described in Section 4. This does not affect existing ad sources, but it will affect automatic creation of new CSJ code slots.
8. Will an prime_rit be deleted if I create it in the auto-creation dialog but do not continue creating the code slot?
No. The creation is also applied to the CSJ backend, and canceling the subsequent code slot creation will not delete the prime_rit. A CSJ app can have up to 50 prime_rits, so create them carefully.
9. How many CSJ prime_rits should one Taku prime_rit use?
We recommend binding all CSJ code slots under the same Taku prime_rit to the same CSJ prime_rit for easier management and troubleshooting.