> ## Documentation Index > Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt > Use this file to discover all available pages before exploring further. # Zeotap SDKs > Client-side libraries for collecting first-party data from your web, mobile, and tag-manager environments. Zeotap provides SDKs for every client environment that needs to send first-party events into the Zeotap CDP. Each SDK exposes the same core tracking model — identities, events, user properties, page properties, and consent — adapted to the conventions of its platform. ## Pick your SDK For websites and single-page apps. Ships as a lightweight async snippet placed in the `` tag. Deploy the Zeotap SDK through your existing GTM container without touching site code. Deploy the Zeotap SDK through Adobe Experience Platform Launch / Tags. Native iOS library for Swift and Objective-C apps. Distributed via Swift Package Manager and CocoaPods. Native Android library for Kotlin and Java apps. Distributed via Maven Central. React Native package wrapping the iOS and Android SDKs for cross-platform apps. ## What every Zeotap SDK gives you * **Identity collection** — send hashed and raw identifiers (`setUserIdentities`) so events stitch to the right profile. * **Event tracking** — track named events with arbitrary properties via `setEventProperties`. * **User properties** — keep a current snapshot of user attributes via `setUserProperties`. * **Page properties** — capture page-level context for web environments. * **Consent management** — integrate with IAB TCF or your own CMP so collection respects user choices. ## Before you implement You'll need a **Source** in the Zeotap CDP to receive the data. The Source provides the `write_key` (or `api_key`) you'll initialize the SDK with. See [Sources](/articles/integrate-customer/sources) for how to create one.