There can be different reasons for the Teads Click ID not to be forwarded.
Below you can find the main reasons which could be causing this issue.
Please check the following:
Ensure the Teads Click ID is properly implemented by following the How to forward the Teads Click ID guide.
Verify if a 2-step redirection occurs after clicking the creative (e.g. Adserver A → Adserver B → Landing Page). This can result in the &auctid parameter being erased.
Check if there is any automatic refresh on the landing page or after accepting cookies in the CMP, which could wipe URL parameters.
Confirm the CMP allows users to navigate to another page without immediately removing the Click ID from the URL.
Ensure the CMP is configured correctly. In some cases, pixels only fire on subsequent pages rather than the first, causing the Click ID to be lost before the pixel fires.
If the landing page includes an age verification disclaimer, ensure it does not create a redirect that removes the Click ID.
For landing pages requiring country or language selection, confirm the Click ID is retained during the redirection after the selection.
Investigate any automatic URL redirections for geographic targeting. For example, if the URL in the creative is www.website.com/welcome/ but it redirects to www.website.com/en-us/welcome, the Click ID might be removed during the process.
Addressing these scenarios can help ensure proper Teads Click ID forwarding and accurate tracking.