Campaign SDK
Campaign decisions that fit your site
The dependency-free browser SDK selects published campaign arms, safely updates declared creative slots, measures viewable exposure, and carries signed attribution into your conversion flow.
Integration flow
From release to result
- 01
Register the site
Create an SDK installation and allow each exact customer-site origin. The public td_pub_ key is safe to place in browser code.
- 02
Publish the campaign
Publish a release with a direct channel arm and an inert creative manifest that targets explicit slots on your page.
- 03
Initialize the SDK
Pass the public key, published campaign slug, and consent state. The SDK makes a stable decision and can apply matching slots.
- 04
Measure the outcome
Use browser events for reporting, then send the exact primary conversion from your server when it should guide optimization.
Evidence model
Reporting is not optimization
tday keeps browser observations separate from evidence that can change campaign allocation. This lets you inspect the whole funnel without teaching the optimizer to trust a client-side claim.
Browser events
track(), automatic exposure, hosted visits, CTA clicks, paid redirects, and QR scans are stored as unverified reporting evidence.Server conversions
td_sec_ key is server-verified. Never place that key in a page, tag manager, or browser bundle.Provider conversions
Choose an integration path
Start with the browser SDK
Render your own experience
Instrument reporting events
Add trusted conversions
Continue reading